Recurring schedules and one-off jobs
Create them from the API, the CLI or the dashboard. Chronos calls your endpoint, or your worker pulls the job.
At most one job per occurrence
curl -X POST https://api.chronos.sh/v1/schedules \
-H "Content-Type: application/json" \
-H "Authorization: Bearer chrns_xxx" \
-d '{
"name": "Sync tenants",
"handler": "sync-tenant",
"cron": "0 * * * *",
"payload": { "tenant_id": "t_123" }
}' Tenant syncs, billing, reports, cleanup. For a one-off job, POST to /v1/jobs with a delay.
Timeouts and server errors retry with backoff
Chronos records every attempt's status and duration.
| failed | cleanup-sessions | attempt 1 | 30.0s (timeout) |
| failed | cleanup-sessions | attempt 2 | 30.0s (timeout) |
| completed | cleanup-sessions | attempt 3 | 2.1s |
Did the job actually run?
Add a ping to a job on cron, GitHub Actions or any other scheduler. If it fails or stops pinging, Chronos alerts you by email, Slack or webhook.
| Status | Monitor | Last ping | Next due |
|---|---|---|---|
| up | nightly-backup | 3 hours ago | in 21 hours |
| late | sync-invoices | 1 hour ago | 4 min ago |
| down | prune-sessions | 26 hours ago | 2 hours ago |
Guides: cron, GitHub Actions, Vercel, Supabase, n8n, systemd
Your coding agent can set up Chronos
Give it one prompt and an API key. It adds a worker and confirms that a job ran. Point it at a job scheduled elsewhere, and it adds a monitor and checks the first ping.
Agent setup →Predictable pricing
| Tier | Price | Schedules | Monitors | Executions/mo | Retention | Seats |
|---|---|---|---|---|---|---|
| Free | $0 | 3 | 10 | 2,500 | 7+ days | 1 |
| Solo | $9.99/mo | 25 | 50 | 25,000 | 30+ days | 1 |
| Team | $29.99/mo | 100 | 250 | 250,000 | 90+ days | Unlimited |
| Business | $79.99/mo | 500 | 1,000 | 1,000,000 | 180+ days | Unlimited |
Every tier includes unlimited one-off jobs and every alert channel. Limits are hard caps, so you never get a surprise bill.
Stop wondering if the job ran.
Free tier is permanent. No credit card required.