Places
Every app, website, API, worker, data store, and external dependency, with its environment, its kind, and the person responsible for it.
Kitomer maps every place in your stack, watches whether it is up, and pages whoever is on call. Your AI can trace an incident from that same map.
Free for 30 days. Connects GitHub, Fly, Cloudflare, and Sentry.

Places, coverage, on call, and incidents live on one map. The people who run the stack and the AI clients signed in as them read the same thing.
Every app, website, API, worker, data store, and external dependency, with its environment, its kind, and the person responsible for it.
Kitomer checks each place’s health URL on a schedule, from every minute to every hour: up or down, the HTTP status, and the latency.
One canvas per environment shows how your places connect. Draw links by hand, or generate them from domains and vars.
Four scores show what is still missing: GitHub repos, Fly apps, and Cloudflare resources not linked to a place, and places not on the map.
A repeating week of shifts with a principal and a backup. Cover, swap, or take on-call now. Hours with nobody on call are shaded.
The ladder a page climbs until someone acknowledges: who, after how long, and how many times. SEV1 skips the delays.
A health check crosses an alert policy, an inbound webhook from Sentry, Cloudflare, or Datadog fires, or a person declares one.
The portal, Slack, the iPhone app, an SMS reply, a phone call, or your AI. Acknowledging stops escalation and leaves the incident open.
Findings with their evidence, similar past incidents, a write-up drafted from the timeline, and follow-ups that become GitHub issues.
MTTA, MTTR, how many pages escalated, pages per shift, the noisiest places, and on-call load per person, including out-of-hours pages.
Cursor and Claude read the same places, heartbeats, on-call, and incidents over MCP, with your access level. See the tools.
See what is down, acknowledge, move an incident along, and know who is on call, from the app or your Home Screen. Meet the app.
Email, SMS, voice, browser push, or iPhone. A typical ladder is push now, SMS after two minutes, a call after five. Send yourself a test page.
Scan connected repositories for licenses, checked against your policy: approved, review required, or prohibited.
Planned work on one place or every place, for up to seven days. Checks keep running, and no new incident opens.
A place has a name, an environment, a responsible person, and a probe that says whether it is up. The map shows how those places connect, so a red card shows what sits downstream.
An incident opens from a failed probe, a webhook, or a person. The principal is paged at once, then the backup, then the org admins, until someone acknowledges.
One schedule per team, each with a timezone, an acknowledgement timeout, and an escalation policy. Who is on call is separate from who owns a place.
The Kitomer MCP gives an AI client the same places, heartbeats, on-call, and open incident, signed in as you. Writes follow the same roles as the portal.
> Why is checkout-api down?
get_incident SEV1 · open 21m · nobody has acknowledged
get_place_logs timeout acquiring connection (20/20 in use)
add_incident_finding evidence · fly logs
By schedule, over 7, 30, 90, or 180 days: which places page most, and how heavy on-call is.
The Kitomer iPhone app signs in to the same account and organizations as the portal. See what is down, acknowledge, move an incident along, and know who is on call.




The Kitomer widget shows how many incidents are open and how many nobody has acknowledged, in red, plus the pages sent to you in the last 24 hours across your organizations.
Every organization starts on a 30-day Free trial. Anyone in the organization can see its plan; owners and admins request an upgrade.
$0
30-day trial
$12 a month
Full Kitomer for growing teams
$35 a month
Priority support and room to scale
Create an account, connect GitHub, Fly, or Cloudflare, and turn on monitoring. Heartbeats start within five minutes.