Status page for Russian B2B SaaS buyers
Russian-speaking B2B buyers ask for a status page in procurement packs, bank integrations, and support SLAs. An English-only timeline looks careless when the contract, runbooks, and Tier-1 support are in Russian.
StillOnline gives each project a Russian UI at stillonline.tech/ru/s/{id} and English at /s/{id} — same checks, same incident history. You write incident text; the shell (labels, subscribe button, timestamps) follows the locale. Free covers one product; connect Telegram owner alerts through the StillOnline bot when on-call is one founder with a phone.
Quick answer
For Russian B2B SaaS, share https://stillonline.tech/ru/s/{project-id} in RU contracts and onboarding. StillOnline keeps one project with localized chrome; incident bodies are yours to type in Russian or bilingual. Owner alerts use email, the StillOnline Telegram bot, or Slack (Telegram guide). Put the link in docs and questionnaires — do not hide it in a footer only (B2B trust).
What RU buyers actually check
Procurement rarely reads your marketing site. They open the URL you attached.
| Document | What they expect |
|---|---|
| RU договор / приложение | Link works; labels in Russian |
| Анкета безопасности | Permanent HTTPS URL, uptime history |
| Support macro | Same link support quotes during outages |
| EN security pack (dual HQ) | Often /s/... without /ru |
One broken redirect during diligence costs more than a year of monitoring.
EN vs RU URL on one StillOnline project
You do not fork monitoring per language.
| Surface | English buyers | Russian / СНГ buyers |
|---|---|---|
| Status page | /s/{id} | /ru/s/{id} |
| Dashboard | /app | /ru/app |
| Public JSON API | api.stillonline.tech/v1/public/status/{id} | same payload |
Incident titles and bodies are not auto-translated. For serious outages, add a short second paragraph in the other language or link to a runbook (EN/RU status guide).
Checklist before you send the RU link
- Production
GET /healthreturns 200 (quickstart). - StillOnline check hits that URL from outside your VPC.
- Connect Telegram in settings — test with maintenance mode, not a real outage.
- Paste
/ru/s/...into RU onboarding; keep/s/...in EN pack if you sell both. - Wait 2–3 probe cycles so the timeline is not empty on first open.
Plans that match Russian B2B stage
| Stage | StillOnline fit |
|---|---|
| First RU enterprise pilot | Free — one URL, public page, one owner channel |
| Several products or RU + EN brands | Pro — up to 10 projects, private pages, API |
| Shorter intervals, more history | Ultimate — see pricing |
StillOnline does not host status.вашбренд.ru. You sell transparency on stillonline.tech — same limit as public status guide.
Related guides
- EN and RU status pages for one SaaS
- B2B status page trust
- Public status page for SaaS
- Telegram owner alerts
FAQ
Which StillOnline URL goes in a Russian B2B contract?
Use https://stillonline.tech/ru/s/{project-id} when the contract and support docs are in Russian. Use the non-/ru URL for English-primary security reviews. Both stay valid for the project lifetime (EN/RU guide).
Does StillOnline auto-translate incidents to Russian?
No. UI chrome follows /ru; you type incident text. For bilingual buyers, write both languages in one post or link externally (incident template).
Is a StillOnline status page enough for a Russian bank integration questionnaire?
It covers external uptime proof and incident communication — not full compliance suites. Pair the link with your security docs. Many indie SaaS pass the “status URL” line with a hosted page on Free (B2B trust).
Can Russian buyers subscribe to StillOnline status emails?
Yes on the public page via Google sign-in — separate from owner Telegram/Slack/email alerts. Owner setup: Telegram guide.
Does StillOnline support custom domains for Russian buyers?
No in v1. Share the hosted stillonline.tech/ru/s/... link in RU docs. Custom hostname is not on the roadmap in current prod.