StillOnline?

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/demo and English at /s/demo — 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/demo 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.

DocumentWhat they expect
RU договор / приложениеLink works; labels in Russian
Анкета безопасностиPermanent HTTPS URL, uptime history
Support macroSame 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.

SurfaceEnglish buyersRussian / СНГ buyers
Status page/s/demo/ru/s/demo
Dashboard/app/ru/app
Public JSON APIapi.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

  1. Production GET /health returns 200 (quickstart).
  2. StillOnline check hits that URL from outside your VPC.
  3. Connect Telegram in settings — test with maintenance mode, not a real outage.
  4. Paste /ru/s/... into RU onboarding; keep /s/... in EN pack if you sell both.
  5. Wait 2–3 probe cycles so the timeline is not empty on first open.

Plans that match Russian B2B stage

StageStillOnline fit
First RU enterprise pilotFree — one URL, public page, one owner channel
Several products or RU + EN brandsPro — up to 10 projects, private pages, API
Shorter intervals, more historyUltimate — see pricing

StillOnline does not host status.вашбренд.ru. You sell transparency on stillonline.tech — same limit as public status guide.

FAQ

Which StillOnline URL goes in a Russian B2B contract?

Use https://stillonline.tech/ru/s/demo 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.

Further reading