Multiple status pages for agencies and client projects
Web studios and product agencies ship several client SaaS products. Each client deserves a dedicated StillOnline status URL — not your agency homepage — so incidents stay scoped and PMs know which product is red.
StillOnline uses one login, separate projects per client, and one account-wide Telegram StillOnline bot link for owner alerts. Free fits a single client pilot; Pro scales to a small portfolio without building custom status software.
Quick answer
StillOnline creates a separate project (and public status page) per client product. Each project has its own HTTP checks and /s/{project-id} URL. Free: 1 project (one client on free tier). Pro ($9/mo): up to 10 projects and 10 URLs per project — suited to small agency portfolios. Owner alerts use one account-wide Telegram StillOnline bot link (Telegram guide).
Recommended agency structure
One project per client keeps incident history, naming, and handoff clean. Mixing client URLs in a single project blurs who is down and makes offboarding painful.
| Client | StillOnline | Monitor |
|---|---|---|
| Client A SaaS | Project “Acme App” | https://api.acme.com/health |
| Client B API | Project “Beta API” | https://api.beta.io/health |
| Internal tools | Project “Agency Admin” (optional private on Pro) | Internal health URL |
Do not mix client URLs in one project — incidents and branding blur.
Workflow for delivery teams
Treat status setup as part of launch, not a post-mortem after the first outage.
- On launch: add health route on client stack — health quickstart.
- StillOnline: new project per client; hand off status URL to client PM.
- Alerts: agency on-call uses Telegram or Slack — your settings, one bot link.
- Incidents: you or client writes updates — incident template.
- Offboarding: export history screenshots; disable checks or hand the project to the client’s own StillOnline login when the retainer ends.
Billing and positioning
| Plan | Agency use |
|---|---|
| Free | Single client pilot or internal demo |
| Pro | Several paying client retainers |
| Ultimate | Large portfolio, faster intervals |
Bill $9–29/mo as a “monitoring & status” line item — cheaper than building custom status (vs Uptime Kuma).
White-label honesty
StillOnline pages live on stillonline.tech. Sell transparency, not white-label hostname. Mention the status URL in client onboarding or contracts — docs and welcome email work better than hiding the link in a footer.
Related guides
FAQ
Does one StillOnline Telegram bot cover all agency client alerts?
Yes. Link the official StillOnline bot once in settings; downtime messages include the project name. Free: one owner channel total; Pro / Ultimate: email, Telegram, and Slack together — Telegram guide.
Can each client post incidents on their own StillOnline status page?
The account owner manages incidents in the dashboard today. Options: invite the client to sign in with their Google account on a dedicated StillOnline login, or your agency posts using the incident template.
Which StillOnline hosting guides apply per client stack?
Match the client’s host: Vercel, Render, Netlify. Each gets its own project and /s/{id} URL — public status page guide.
Can agency ops automate StillOnline checks with AI agents?
On Pro, StillOnline MCP lists projects after client infra changes. External HTTP checks still need a public health URL per client — health quickstart.