Operate
Go-live check
Before real users arrive, one checklist for each app shows what's in place and fixes what isn't.
Before sending real visitors to an app, the go-live check lists what should be in place: a domain, backups, alerts, a health check, a spending limit and more. Each item is ticked, or has a button that sets it up.
How to use it: open an app and go to its Go-live tab. Work down the list until everything that matters is ticked.
Before you send real traffic to an app, check that it's actually ready. The go-live check looks at one app and lists what should be in place, with each item ticked or paired with a button that fixes it.
What it checks
| Item | Level | Passes when |
|---|---|---|
| A version is live | Needed | A deploy has gone healthy |
| Your own domain with HTTPS | Recommended | A custom domain is verified and serving HTTPS |
| A health check path | Recommended | CLI checks a path, not just the port (functions always pass) |
| Databases are backed up | Needed | Every database the app references has scheduled backups |
| Someone hears about problems | Needed | The project has at least one alert channel |
| Its main page is checked in a browser | Recommended | A browser check covers the app |
| Protected from floods and scrapers | Recommended | Edge rules are on |
| No leaked secrets | Needed | No open secret-scanning findings in the project |
| A spending ceiling | Recommended | The project has a monthly budget |
The app is ready when every item marked "Needed" passes. "Recommended" items make it safer, and don't block anything.
Use it
In the dashboard: open the app and choose the Go-live tab. Press an item's button to fix it: some apply straight away (deploy, standard edge protection, a browser check for the home page), others take you to the right settings.
Ask your agent:
"Is web ready to launch? Fix what's missing."
Agents use the cli_go_live tool. Each item that isn't in place carries fix.request (a call that fixes it) or fix.dashboardPath (where a person fixes it).
With the API:
GET /v1/services/:id/go-live{
"ready": false,
"passed": 6,
"total": 9,
"items": [
{ "id": "alerts", "label": "Someone hears about problems", "ok": false, "level": "required",
"detail": "No alert channel: outages only show in the dashboard.",
"fix": { "label": "Add an alert channel", "dashboardPath": "/projects/prj_…?view=settings" } }
]
}The project doctor (/docs/project-doctor) covers the whole project all the time; the go-live check is one app, once, before launch.