Help & Documentation

Okokumo is a family of sovereign, FR/EU-hosted tools. This page covers what each one does, starting with the first: Sentinel, infrastructure monitoring and alerting.

Sentinel — infrastructure monitoring

HTTP(S) checks

Monitor any URL on an interval from 30 seconds to 24 hours. Assert on status code, response latency, body content, or response headers — a check only counts as up when every assertion passes.

Heartbeat / cron monitoring

The reverse of an HTTP check: instead of Sentinel polling you, your scheduled job pings a unique URL after each run. Silence past the configured period plus grace delay is treated as a failure — catches jobs that stop running, not just jobs that fail loudly.

A cron check can take the crontab line itself (0 3 * * 1-5) rather than a flat period, with the timezone your server's crontab runs in. The deadline then becomes the next scheduled run plus the grace delay, so a weekday-only job stays quiet over the weekend instead of paging you every Saturday, and a skipped run is noticed within its own grace window rather than a day later. The form lists the next few runs as you type, so you can see the schedule before relying on it.

SSL/TLS & domain monitoring

Certificate expiry alerts at 30/14/7/1 days out, invalid-chain detection, and SNI support. Domain expiry and DNS resolution failures are monitored the same way, so a lapsed registration or a broken DNS record surfaces before customers notice.

Multi-region confirmation

Checks run from two independent EU probe regions. A failure only triggers an alert once it's confirmed from multiple probes — a single region's network blip won't page you.

Alert channels

Email, Telegram, generic signed webhooks, and Slack and Discord incoming webhooks. A channel only receives real alerts once it's validated: webhook, Slack and Discord validate the moment a test delivery succeeds, email validates once you click the confirmation link sent to that address — this guarantees alerts never go to a destination nobody's confirmed. Channels can be assigned to specific checks, or left as the default that covers every check in your organization.

Dashboard & history

Live status per check, latency and uptime graphs over day/week/month, and a full history of every up/down transition.

Team & roles

Invite teammates by email as owner, admin, or member — manage who can edit checks, billing, and alert channels.

Public API

Every check, its results, and its status are available over a versioned, API-key-authenticated REST API. Full reference: API documentation.

okokumo's own status

A minimal, unauthenticated view of Sentinel's own uptime, independently confirmed by a third-party monitor: Live system status. This is our status, not yours — for your own public page, see Tower below.

Archer — public status badges

Embed a check's status on your own website via a small, self-contained badge — a compact ring with the uptime percentage, or a detailed 30-day history bar — in light or dark, dropped in as an <iframe>. Available on paid plans, from each check's page.

Tower — your public status page

A full status page for your own customers, hosted at status.okokumo.com/your-name. Choose which checks appear as components, name each one for your audience (publish "API", not "prod-api-lb-healthz"), and each shows live status plus 90 days of history. Nothing else about a check is ever exposed — not its URL, not its internal name, not why it's paused. Pick dark or light to match your own branding. Set it up from Status page; available on Pro and Business.

Where Archer is a single badge you embed in your own page, Tower is a whole page we host for you.

Incidents

Components say what's up right now; an incident is the story around it. Write one by hand for anything a check can't see, or let us start it: when a component goes down we draft the incident, name what's affected and open its timeline, then post the recovery note when everything responds again and close it once things have been stable for 15 minutes.

A draft is private. Nothing automation writes is visible to your visitors until you publish it — we never publish one for you, and the words are yours to edit first. Resolved incidents stay on the page for a fortnight; archiving one files it into the history behind your status panel instead, where deleting it would take the story with it.

Incidents also work over the API with an API key, so the job that already knows the deploy failed can declare one and post its own updates. Page setup — slug, components, custom domain — stays here in the dashboard: a key can narrate an outage, not change your public address.

Your own domain on your status page

On Business, the page can be served from your own hostname — status.yourcompany.com instead of ours — with an HTTPS certificate we obtain and renew for you. Two steps, from Status page:

1. Enter the hostname and save it.
2. Create the CNAME record we show you at your DNS provider, then press Verify.

Verification checks that the name actually resolves to us, which is both proof you own it and proof traffic will arrive — so we only ask for one record, not a separate ownership token. DNS changes take a few minutes to spread; if the first check says the name doesn't resolve yet, wait a moment and press Verify again.

Subdomains only. An apex domain (yourcompany.com with nothing in front) can't be a CNAME, so it can't be pointed at us — use status. or similar. Your original status.okokumo.com/your-name address keeps working either way, so links you've already shared don't break. If you leave Business, the custom hostname stops serving and the page falls back to that address.

We re-check the record once a day. If it stops pointing at us we'll email you, and if it stays that way for a week the page goes back to its okokumo address — the domain stays saved, so restoring the record and pressing Verify is all it takes to switch back.

Plans & billing

Free tier covers 5 checks. Paid plans scale up check count and check frequency, billed monthly through Stripe with French-compliant invoicing (VAT handling, sequential numbering, legal mentions).

More help

See also Security & data for hosting and data-protection details. Still stuck? support@okokumo.com.