Internal status page for small teams
A three-person SaaS team still needs a shared picture when production flickers — but not every check belongs on a public page competitors can bookmark. Staging, admin APIs, and migration windows should stay inside Slack, not Google search.
StillOnline private status pages (Pro / Ultimate) return 404 to anonymous visitors while owner alerts (email, StillOnline Telegram bot, Slack) ping whoever is on laptop duty. Your public customer page stays on the same account when you are ready.
Quick answer
Use a private StillOnline status page at stillonline.tech/.../s/... for internal or staging URLs your small team shares in Slack — Pro or Ultimate required. Anonymous users cannot open the link; teammates with it see the same timeline as a public page. Owner alerts still fire via the StillOnline bot on Telegram (guide). Keep customer-facing checks on a public project (public vs private).
Public vs private on one small team
| Page | Who sees it | Typical checks |
|---|---|---|
| Public | Customers, prospects | Production /health, API gateway |
| Private (Pro+) | Founders, contractors with link | Staging, internal tools, pre-release |
Free only supports public visibility. If you need hidden URLs, budget Pro — see pricing.
Setup pattern for 2–5 people
- Project A (public) — production health URL (quickstart).
- Project B (private) — staging or admin host; visibility → Private in settings.
- One Telegram connect per account — alerts include project name so you know which stack failed (Telegram).
- Pin both links in an internal Slack channel — do not hide them in a footer only.
On Free, use a single public project for production only; keep staging checks in CI or logs until you upgrade.
When internal page beats a spreadsheet
Shared doc rows go stale. A status timeline shows probe time, last green, and incident posts in one URL.
- Contractor in another timezone opens the link before DMing you.
- You run scheduled maintenance on staging without scary public red.
- Postmortems link to the same timeline support already saw.
Do not over-build
Small teams rarely need PagerDuty rotations on day one. Pair private StillOnline with solo on-call without PagerDuty until sleep debt forces escalation policy.
Related guides
- Public vs private status page
- Side project production checklist
- Telegram owner alerts
- Which StillOnline plan
FAQ
Does StillOnline Free include private status pages?
No. Private visibility is Pro and Ultimate (public vs private).
Can contractors open our private StillOnline page?
Anyone with the secret URL can open it; anonymous visitors without the link get 404. Rotate the project id if the link leaks — treat it like an unlisted Google Doc.
Do Telegram alerts work on private StillOnline projects?
Yes. Owner alerts are account-wide; messages name the project that failed (Telegram guide).
Should staging and production share one StillOnline project?
Usually no — split projects so staging red does not frighten customers. Pro allows up to 10 projects.
Is an internal page a replacement for logging and APM?
No. It answers is the endpoint up from outside? — not why inside the JVM. See status without full observability.