specific deploy; your projects and environments appear automatically after the first deployment.
What you can do
- Service overview - architecture visualization, per-service status, logs, metrics, and scaling.
- Deployments - view and track deployments across environments.
- Database - browse tables, run queries, and manage your Postgres databases.
- Storage - browse bucket contents and generate external S3 credentials.
- Secrets and config - update values in place; they take effect on the next deployment.
- Crons - inspect scheduled jobs and their runs, or trigger one with Run now.
- Workflows - the Temporal Web UI for your Temporal engines: monitor workflow executions, task queues, and workflow state.
- Analytics - traffic analytics for your services.
- Jobs - run one-off commands against a deployed service.
- Custom domains - add, list, and remove domains.
- GitHub integration - deploy automatically on every push and get preview environments per pull request.
The local dashboard
Local development has the same dashboard:specific dev launches a local mirror of it, usually at http://localhost:3000 (the exact URL is printed at startup, and each instance run with --key gets its own). It drops the features that don’t apply locally, like deployments, domains, and scaling, and keeps everything you need while building: the architecture view, database browser, storage browser, crons, and workflows.