11 posts tagged engineering. All posts
2026-11-02
okokumo organizations have three roles, owner, admin and member, and every rule between them is enforced by the API, not the dashboard. This post lists who can do what, the exact error a member gets, why the last owner can't leave, how invitation links are generated and stored, and the one action only an owner can take.
2026-10-26
Archer is okokumo's embeddable status badge, one check rendered in an iframe on your own site. This post walks through what the embed route actually does. Its handler is pinned by a test never to set a frame-blocking header, an unknown token and a disabled badge get the identical 404, a paused check never shows why it is paused, and it renders the check's name and status and nothing else.
2026-10-19
okokumo runs a hosted MCP server at /mcp. Claude, Cursor and other MCP clients can use it to read your checks, pause one, or draft a status-page incident. Each of its 18 tools is a thin call onto an existing /v1 route and runs under your role and your plan limits, so an assistant can do nothing your API key couldn't already do over REST. This post covers what the tools are, what one exchange looks like on the wire, and how browser sign-in replaces pasting a key.
2026-10-12
okokumo has two self-serve JSON exports for GDPR art. 20 portability. One is for admins and covers everything an organization configured. The other is for any user and covers only that person. This post covers what each file contains, what it leaves out and why, and how the document tells you when it was cut short.
2026-10-05
An uptime percentage is a ratio of probe results, not a measurement of time. How okokumo computes the number on badges and status pages, how a UTC day becomes up, partial, down or no data, why a paused check is grey rather than red, and why a 3-minute outage still reads 100.0%.
2026-09-13
A retention number without its error bar is marketing. We publish 90 days for check results and 30 days for the output your job attaches to a failed ping — plus how far past each one a record can actually survive, because we measured it and the first number we published was wrong.
2026-09-04
Disabling a check during planned work stops the probing too, which leaves a hole in the uptime history exactly where the interesting hour was. How okokumo suppresses paging without suppressing measurement — and what has to happen when the window closes and the thing is still down.
2026-08-31
A monitoring product's worst failure is silence, because a broken alerting pipeline looks exactly like a quiet week. Here is the alert of ours that reached nobody, why health checks could not see it, and the endpoint that breaks on purpose every morning so that silence becomes something a pager outside our own infrastructure can see.
2026-08-18
Letting a customer serve their status page from status.theircompany.com is four lines of Caddy config and one endpoint you must not get wrong. How okokumo gates certificate issuance, verifies with a single CNAME, and takes a hostname back when it stops pointing at us.
2026-08-13
A monitoring tool that cries wolf gets muted, and a muted tool is worse than none. How okokumo requires two probe regions to agree before it pages you — and why it deliberately stops requiring that when a probe dies.
2026-07-27
How okokumo schedules thousands of due checks without a global periodic scan, and without double-firing when two scheduler ticks overlap.