Public vs private status page on StillOnline
Public pages are for customers and partners — anyone with the link sees uptime and incidents. Private pages are for your team when you do not want the internet to watch a staging stack or internal tool.
StillOnline defaults to public on all plans. Private visibility is Pro and Ultimate. Either way, owner alerts (email, StillOnline bot on Telegram, or Slack) tell you when checks fail before most visitors refresh the page.
Quick answer
A public StillOnline status page is for customers — anyone with stillonline.tech/.../s/... sees uptime and incidents. Private (Pro/Ultimate) returns 404 to anonymous visitors for internal or staging stacks. Owner alerts work either way via email, the StillOnline bot, or Slack in settings.
Comparison
Visibility changes who can read the timeline; it does not turn off monitoring.
| Public | Private | |
|---|---|---|
Who can open /s/... | Anyone with link | Anonymous visitors get 404 |
| Typical use | B2B SaaS, API docs for integrators | Internal admin, pre-launch |
| Plan | All | Pro, Ultimate |
| Subscriber emails (Google) | Yes on public page | N/A for anonymous visitors |
You still get owner alerts on either visibility — Telegram guide.
When to stay public
Most revenue-stage SaaS products should default here until you have a concrete reason to hide.
- Paying customers need a trust link without logging in.
- You promised a public status page in sales or security questionnaires.
- Incidents should reduce “is it down?” support tickets.
Start here: public status page guide.
When to switch to private (Pro)
Private is for URLs you never want indexed or guessed — not for shame about downtime.
- Monitoring internal APIs not meant for customers.
- Competitors should not see your uptime history.
- You share the URL only inside Slack with a small team.
Toggle in project settings → visibility → Private. If you downgrade from paid, visibility returns to public — plan before sharing widely.
Hybrid pattern on a budget
Free forces a choice; Pro lets you separate prod and internal.
Free: one URL — usually production API health public. Do not put staging on the same project if you need privacy; wait for Pro or skip external monitoring for staging.
Pro: second project or more checks — public prod page plus private internal page.
Setup checklist
Walk through once per environment so links do not leak to the wrong audience.
- Health URL live — health check quickstart.
- Create project → choose visibility.
- Copy
/s/...link only to the intended audience (docs, onboarding, or internal Slack). - Connect Telegram or other owner channel so you know before visitors refresh the page.
Related guides
- Public status page for SaaS, API, or bot
- Status page at first revenue
- Telegram owner alerts
- StillOnline vs Instatus / Statuspage
FAQ
Does a private StillOnline status page hide from search engines?
Anonymous visitors get 404 on a private page — they cannot load uptime or history. Do not publish the /s/... URL in open docs; share it only inside your team. Customer-facing links: public status page guide.
Can Google subscribers get email on a private StillOnline page?
No. Subscribe with Google targets public pages. Private projects rely on owner alerts and manual link sharing — configure Telegram or email in settings.
Do StillOnline HTTP probes still run on private projects?
Yes. Visibility only changes who can view results; checks run the same. You still get owner alerts when a probe fails.
Is private visibility available on StillOnline Free?
No — the private toggle requires Pro or Ultimate. On Free, use one public production health URL — Pricing · status page at first revenue.
Can I switch a StillOnline project from public to private after customers have the link?
Yes on Pro / Ultimate. Old links may still circulate — treat the public URL as shared forever and communicate if you rotate. New private URLs should go only to the intended team.
Do StillOnline owner Telegram alerts work the same on private pages?
Yes — the StillOnline bot alerts the owner regardless of visibility. Customers need a public page (or manual updates) for self-serve status — Telegram guide.