Project setup
A guided first run that sets up monitors, alert channels and a status page for a projectEdit
Project setup takes a new project from empty to watched, then creates everything in one step at the end. You can skip any step. It opens after sign-up and on Create and set up for a new project; reopen it from Project setup in the sidebar, ⌘ K, or Organization → Projects.
Run the setup
Welcome. Pick your focus; it reorders steps, never hides one.
Your app. Enter the URL and optionally choose Scan. It stores only codes, timings, paths and page titles. Private addresses are refused. A test account is saved at once as an encrypted project secret.
Alerts. Add notification channels and send a test alert. Project admins can turn on Repeat until acknowledged (sets the reminder interval and, if the policy has no channels, adds yours) and Also alert on warnings.
Monitors. Pick pages for uptime and SSL; only the homepage starts ticked. Optionally add a heartbeat.
Status page. Publish a status page, keep it as a draft, or choose I don't need a status page.
Requirements and tests (Beta). AI suggests requirements from your scan; each then offers Generate test. Suggest requirements costs 1 AI credit, once per project per day, and the cost shows first. The step is locked on a trial and hidden when no AI provider is configured.
AI SRE. Connect GitHub, Sentry, Datadog, Grafana or Prometheus connectors; each shows Connected or Saved, but the token was rejected. Private-network tools use a private agent from Organization → Private Agents. Needs a project admin; editors see Ask a project admin.
Review and create. A heartbeat's ping URL is shown once, here.
Focus and sidebar
Review and create is always last. Use Change focus in the user menu to switch.
| Focus | Steps start with | Sidebar order (first group open) |
|---|---|---|
| SRE and platform | App, Alerts, Monitors, AI SRE | Respond, Monitor, Communicate, Automate |
| QA engineers | App, Tests | Automate, Communicate, Respond, Monitor |
| Developers | Terminal commands and coding-agent recipe | Automate, Monitor, Respond, Communicate |
| Engineering leaders | Invite your team | Unchanged |
| Everything, or skipped | Default order | Unchanged |
Getting started checklist
Until setup is finished or dismissed, the dashboard shows a Getting started card and the sidebar shows Project setup with a count such as 4/9. Dismiss hides both for that project. Projects that already have monitors, tests, jobs or status pages see them only after you start setup.
Ticks come from what exists: a monitor, notification channel, heartbeat, status page (or "I don't need one"), requirement, test, job, connector or private agent, service, another member or invitation, and a CLI token. Items whose feature is off are hidden.