robots.txt
See which AI crawlers other sites block →# As a condition of accessing this website, you agree to abide by the following
# content signals:
# (a) If a Content-Signal = yes, you may collect content for the corresponding
# use.
# (b) If a Content-Signal = no, you may not collect content for the
# corresponding use.
# (c) If the website operator does not include a Content-Signal for a
# corresponding use, the website operator neither grants nor restricts
# permission via Content-Signal with respect to the corresponding use.
# The content signals and their meanings are:
# search: building a search index and providing search results (e.g., returning
# hyperlinks and short excerpts from your website's contents). Search does not
# include providing AI-generated search summaries.
# ai-input: inputting content into one or more AI models (e.g., retrieval
# augmented generation, grounding, or other real-time taking of content for
# generative AI search answers).
# ai-train: training or fine-tuning AI models.
# use: how AI systems may consume the content (immediate, reference, or full).
# ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS RESERVATIONS OF
# RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN UNION DIRECTIVE 2019/790 ON COPYRIGHT
# AND RELATED RIGHTS IN THE DIGITAL SINGLE MARKET.
# BEGIN Cloudflare Managed content
User-agent: *
Content-Signal: search=yes,ai-train=no,use=reference
Allow: /
# Training crawlers
User-agent: Amazonbot
Disallow: /
User-agent: Applebot-Extended
Disallow: /
User-agent: Bytespider
Disallow: /
User-agent: CCBot
Disallow: /
User-agent: ClaudeBot
Disallow: /
User-agent: Diffbot
Disallow: /
User-agent: Google-Extended
Disallow: /
User-agent: GPTBot
Disallow: /
User-agent: omgili
Disallow: /
User-agent: anthropic-ai
Disallow: /
User-agent: Claude-Web
Disallow: /
User-agent: cohere-ai
Disallow: /
User-agent: MistralAI-Training
Disallow: /
User-agent: meta-externalagent
Disallow: /
User-agent: GoogleOther
Disallow: /
User-agent: Baiduspider
Disallow: /
User-agent: PetalBot
Disallow: /
User-agent: AwarioSmartBot
User-agent: AwarioRssBot
Disallow: /
User-agent: Google-CloudVertexBot
Disallow: /
User-agent: QualifiedBot
Disallow: /
User-agent: Cotoyogi
Disallow: /
User-agent: ICC-Crawler
Disallow: /
User-agent: atlassian-bot
Disallow: /
User-agent: FishBot
Disallow: /
User-agent: BorderxBot
Disallow: /
User-agent: NavuBot
Disallow: /
User-agent: SemrushBot-SWA
Disallow: /
User-agent: WARDBot
Disallow: /
User-agent: magpie-crawler
Disallow: /
User-agent: KimiBot
Disallow: /
User-agent: CitibotSiteCrawler
Disallow: /
# END Cloudflare Managed Content
User-Agent: *
Allow: /
Disallow: /channels
Disallow: /checks
Disallow: /incidents
Disallow: /settings
Disallow: /auth
Disallow: /login
Disallow: /relay
Sitemap: https://capto.run/sitemap.xml
llms.txt
Compare with other sites' llms.txt files →# Capto
> A dead-man's switch for cron jobs, background workers and containers. Capto
> tells you when one goes quiet, and shows the last context it left behind.
A job pings a URL when it finishes. Capto starts expecting that ping and opens
an incident the moment it stops arriving. Checks come in three kinds —
heartbeat for workers and daemons, cron compared against the previous scheduled
fire in a timezone you set, and HTTP polled at its own interval — with Docker
and systemd as recipes on top of heartbeat rather than separate products.
While a job is alive it can post breadcrumbs: short structured lines, ignored
until they matter. When a check goes down the recent ones are snapshotted onto
the incident and travel with the notification, so the alert says what the job
was doing when it stopped rather than only that it stopped. Jobs can also
report that a run started and that one failed, which is what separates a job
that hung from one that never began; a failure can carry the output it died
with.
Detection runs every 30 seconds for everyone, on
every plan. Free watches 20 checks and keeps
3 days of history; Pro watches 100 and keeps
90 days. Alerts, breadcrumb volume and detection speed are never
metered.
## Start here
- [Quickstart](https://capto.run/docs): create a check, ping it from a job, add breadcrumbs, point an alert somewhere
- [Live demo, no account](https://capto.run/demo): a real ping URL valid for an hour — curl it, stop, watch the incident open
- [Pricing](https://capto.run/pricing): two flat plans, no per-monitor or per-seat maths
## Comparisons
- [Capto vs Healthchecks.io](https://capto.run/compare/healthchecks-io): Healthchecks.io is open source and self-hostable, and that is a real advantage. Capto's is context: the breadcrumbs your job left arrive with the alert.
- [A Cronitor alternative for solo developers](https://capto.run/compare/cronitor): Cronitor is built for teams and priced per monitor and per seat. Capto is flat, does not meter, and puts the job's last context on the alert.
- [A Dead Man's Snitch alternative with context on the alert](https://capto.run/compare/dead-mans-snitch): Dead Man's Snitch does one thing and does it plainly. Capto does the same thing, and puts the last few lines your job wrote on the alert.
## Notes
- [A long-running agent is still just a worker](https://capto.run/blog/agent-that-goes-quiet): Long-running agents hang the same way workers do. Heartbeat while they make progress; Capto pages when the pings stop — not an LLM observability suite.
- [Put the agent's last step on the alert](https://capto.run/blog/agent-last-step-on-the-alert): Where to put breadcrumbs in an agent loop so the page names the step it died on, and why a 50-entry ring buffer is the constraint that shapes it.
- [A cron job that never starts is the one you miss](https://capto.run/blog/cron-that-never-starts): Capto cron checks compare the last ping to the previous scheduled fire, so a missed window is the signal — even when the job never started.
- [The alert should include the last thing the worker said](https://capto.run/blog/last-context-when-the-worker-dies): Breadcrumbs are structured events your job posts while alive. When a check goes down, Capto snapshots the recent ones onto the alert.
- [Watch a container without handing over the Docker socket](https://capto.run/blog/docker-without-the-socket): Capto never needs your Docker socket. A host sidecar pings when the container is healthy; silence past interval plus grace is the incident.
- [Your HTTP endpoint can be fine while the job is dead](https://capto.run/blog/http-up-job-down): A green /health check proves the port answers, not that the worker is still working. Use HTTP for reachability; heartbeat or cron for the job.
- [We will not sell you faster detection](https://capto.run/blog/no-faster-detection): Every check is evaluated every 30 seconds on both plans. A faster paid tier would cost free accounts and buy paying ones nothing.
- [Muting an alert should never mute the truth](https://capto.run/blog/muting-vs-truth): Capto keeps detection and notification apart. Mute suppresses the alert; the check still evaluates and still reads as down.
## Optional
- [About](https://capto.run/about): what Capto is for, what it deliberately is not, and what it commits to
- [All notes](https://capto.run/blog): index of the writing above
- [RSS](https://capto.run/blog/rss.xml): the same notes as a feed
- [Terms](https://capto.run/terms): plans, payment, cancelling, and what happens to your history
- [Privacy](https://capto.run/privacy): what is collected, how long it is kept, who else processes it
Support: support@capto.run