cron-job.org
- Free allowance
- Entirely free of charge, with no limit on the number of cronjobs per account (fair usage expected); each job runs up to 60 times an hour, i.e. every minute
- Verdict
- ★ qualifiesusable as stated; the read path was probed
- Cost
- free tier
- Identity
- emailno card, no phone
- Binding limit
- request-rateeach job runs up to 60 times an hour (every minute); API: 100 requests per day by default, 5,000 per day for sustaining members; API per-method limits such as 5 requests per second, or 1 request per second and 5 requests per minute
- Evidence
- documented26 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-12-01checked 2026-10-31 (live); stale on 2026-12-01
| Free tier | Entirely free of charge, with no limit on the number of cronjobs per account (fair usage expected); each job runs up to 60 times an hour, i.e. every minute unit unlimited; metered on none; Financed by voluntary donations. Sustaining members get a higher API limit of 5,000 requests a day; scheduling has no paid tier. Status pages, status badges and failure notifications by email or webhook are part of the free service. |
|---|---|
| Price | none stated |
| Limits |
An execution times out after 30 seconds. A job that fails more than 25 times in a row is disabled automatically. |
| Binding | request-rate The one-minute minimum interval and the 30-second timeout bound what a job can drive; the 100-a-day API limit binds only on programmatic job management. |
| Identity | email The console sign-up form asks for first name, last name, email address and a password; there is no payment step because the service is free. |
| Egress | not applicable: an outbound HTTP caller; at most 64 KB of each response is read |
| Per-object cap | up to 64 KB of each response is read; a larger response aborts the execution |
| Retention | response headers and bodies stored for 2 days; the last 50 executions of each job are viewable (2 days) |
| Interface | rest a REST API with JSON payloads, authenticated by an API key in an Authorization bearer header; keys are generated in the console and can be restricted to listed IP addresses endpoint: https://api.cron-job.org/ |
| Tooling | any HTTP client against the REST API, or the web console. As a last resort the scheduler source (chronos, GPL) is on GitHub: the user installs and runs the server software on a rented or free machine. |
| Composes with | Calls a free HTTP endpoint (a serverless function or a CI trigger URL) as often as once a minute, so it supplies the schedule that a free compute host without cron lacks, as long as each call finishes within 30 seconds. |
| Reliability | Slight delays at peak hours with no punctuality guarantee; jobs that failed often or ran long may be delayed on purpose, and a job is disabled after more than 25 consecutive failures. |
| Evidence note | documented Free tier, limits and sign-up fields are read on first-party pages. The API answered HTTP 401 to a request without a key and the public executor-node list answered HTTP 200 with JSON, so the endpoint is live; a job execution is not measured. |
| Parsed numbers |
|
Evidence 26
| date | source | what it proved |
|---|---|---|
| 2026-10-30 | cron-job.org/en/ | the service is free and financed by donations |
| 2026-10-30 | cron-job.org/en/faq/ | the FAQ states the service costs nothing |
| 2026-10-30 | cron-job.org/en/faq/ | no cap on the number of jobs per account, with fair usage expected |
| 2026-10-30 | cron-job.org/en/faq/ | the minimum interval is one minute |
| 2026-10-30 | cron-job.org/en/faq/ | part of the text of Limits, above |
| 2026-10-30 | cron-job.org/en/faq/ | at most 64 KB of each response is read |
| 2026-10-30 | cron-job.org/en/faq/ | response headers and bodies are kept for 2 days |
| 2026-10-30 | cron-job.org/en/faq/ | the last 50 executions per job are viewable |
| 2026-10-30 | cron-job.org/en/faq/ | part of the text of Reliability, above |
| 2026-10-30 | cron-job.org/en/faq/ | no punctuality guarantee; delays at peak hours |
| 2026-10-30 | docs.cron-job.org/rest-api.html | the API allows 100 requests per day by default |
| 2026-10-30 | docs.cron-job.org/rest-api.html | sustaining members get 5,000 API requests per day |
| 2026-10-30 | docs.cron-job.org/rest-api.html | some API methods are limited to 1 request per second and 5 per minute |
| 2026-10-30 | docs.cron-job.org/rest-api.html | most API methods are limited to 5 requests per second |
| 2026-10-30 | docs.cron-job.org/rest-api.html | the REST API authenticates with an API key in a bearer header |
| 2026-10-30 | docs.cron-job.org/rest-api.html | API keys can be restricted to listed IP addresses |
| 2026-10-30 | cron-job.org/en/ | cronjobs are managed programmatically through a REST API |
| 2026-10-30 | cron-job.org/en/ | status monitor jobs and status pages are part of the service |
| 2026-10-30 | cron-job.org/en/ | status badges are part of the service |
| 2026-10-30 | cron-job.org/en/ | failure notifications are part of the service |
| 2026-10-30 | cron-job.org/en/ | notifications can go to a webhook |
| 2026-10-30 | console.cron-job.org/signup | the sign-up is free |
| 2026-10-30 | console.cron-job.org/signup | the sign-up form asks for an email address, alongside first name, last name and password fields |
| 2026-10-31 | probe: https://api.cron-job.org/jobs | the REST API at api.cron-job.org answered HTTP 401 to a request without an API key |
| 2026-10-31 | probe: https://api.cron-job.org/executor-nodes.json | the public executor-node list at api.cron-job.org answered HTTP 200 with JSON |
| 2026-10-30 | github.com/pschlan/cron-job.org | the scheduler daemon source is published on GitHub |