Get started with Status

Set up an installation, join an organization, and create a monitor.

Status monitors services, routes alerts, manages incidents and maintenance, and publishes service health. Self-hosted installations start with a setup wizard. Invited users join an organization through an invitation link. The console displays one organization at a time.

If an administrator has already invited you, skip to Join and sign in. The installation section is for the person deploying Status.

Set up a new installationCopy link

1. Start Status and its PostgreSQL database as described in Self-hosting.
2. Open /setup on the instance. Enter the setup token printed by the web container or stored in $STATUS_STATE_DIR/setup-token.
3. Connect PostgreSQL if it is not already configured, then apply migrations. Set the instance name and public URL.
4. Choose how people sign in: email and password, SSO, or both. Provider discovery is checked before setup completes.
5. Create the first organization and, for password sign-in, its first owner.
6. Copy the worker token when it is revealed. It cannot be retrieved later, although an admin can generate a new one from Settings → Instance.

After completion, the token file is removed and the setup routes return 404. The setup wizard cannot be used to reconfigure a running instance; owners use Settings → Instance instead. Configuration precedence and write-only secret fields are covered in Configuration.

Join and sign inCopy link

An owner or admin invites additional people from Team. The link is bound to the invited email address and expires after seven days. A new local user chooses a password at registration; an existing user signs in and accepts the membership. SSO users authenticate with the configured provider. If both methods are enabled, an SSO account can add a local password later in Settings → Profile.

Password reset links are one-time and expire after one hour. Repeated login, registration, and reset requests are rate-limited. See Roles, members, and teams for workspace access and User profiles for account settings.

Learn the consoleCopy link

The sidebar is grouped by workflow:

• Monitoring: Overview, Monitors, Incidents, and Maintenance.
• Response: Alerts, On-call, Escalation, Objectives, Deployments, and the Operations toolkit.
• Visibility: Analytics and Status pages.
• Management: Agents, Setup health, Team, Audit log, and Settings.

The organization switcher changes the workspace used by every page. The environment selector filters monitors and related information—for example, showing production without staging. It does not move or duplicate records. The top bar contains search, the notification inbox, guided tours, theme controls, and your account. Tours can be replayed for supported pages.

Open the command palette with the search control or Command/Ctrl+K. It can navigate to every console page, find the first 40 indexed monitors, create a monitor/incident/maintenance window/status page, open account settings, change language or theme, sign out, and start page, deep-feature, or multi-page tours. The help menu offers tours relevant to the current page, the welcome tour, a reset for completed tours, and the same palette entry point.

The clock uses the timezone in your profile. The health and environment control shows the selected environment's overall state and can switch environments or open public status pages. Status refreshes live information automatically. When you change organization or environment, the console loads data for that selection.

The Overview is a personal, organization-specific board. Use its editor to add, remove, resize, and rearrange widgets or to create multiple boards. A new board starts from the shipped layout. Learn the available cards in Custom dashboards.

Recommended first workflowCopy link

1. Open Agents and confirm at least one worker is healthy. For internal targets, register a private agent.
2. Create a monitor and use the workbench to test it.
3. Configure an alert channel and send a test notification.
4. Create a status page and map the monitor to a component.
5. Review Setup health for missing production safeguards.

Related documentationCopy link

• Common tasks gives short instructions for the actions most people perform first.
• Status console explains the navigation, top bar, search, notifications, help, settings, and shared interaction patterns in detail.
• Glossary explains product terms in plain language.
• Monitoring explains monitor types, scheduling, state, and diagnostics.
• Incidents covers the responder workflow.
• Maintenance covers planned work.
• Operations toolkit shows where reusable resources and recovery tools live.