Databases & notifications
Connect existing services and follow deployment results.
Database connectors and query console
Master can configure MongoDB, PostgreSQL, MySQL and Redis connections, check TCP reachability and use the query console when the provider driver is installed (mongodb, pg, mysql2 or redis). Portal does not provision the database server. The console caps returned rows at 200 and applies a 10-second query timeout. Read/write classification is a guardrail; use database-enforced least-privilege credentials. The allow-write option can modify real data.
Project diagnostics tokens
Monitor Logs Tokens expose scoped deployment diagnostics. Creating them requires webhooks.manage and logs.read. Copy and store tokens securely; rotate them if disclosed. They are not general management API keys.
Outbound deployment notifications
Configure Discord, Google Chat, Slack or generic HTTPS notification endpoints per project. These notify deployment outcomes; inbound GitHub/Actions triggers are configured separately. Do not infer retry guarantees or delivery SLAs from a saved endpoint.
Where to manage Monitor tokens
Masters create, list and revoke Monitor tokens under Settings → External integrations (/settings/monitor). Account and update settings now have separate pages. During v1.0.0 host maintenance, Monitor requests that record token usage can return HTTP 503; retry after maintenance and do not interpret this response alone as application downtime.