Deno Cron
Declare scheduled JavaScript or TypeScript tasks directly with Deno.cron and run them on Deno Deploy.
- Card required
- No
Deno Cron scores 6.3/10 for free value in Schedulers. The main constraint: Deno Deploy plan and runtime limits apply; verify current Deploy pricing and cron availability.
Free value score
6.3 / 10Show the math
Key metrics
What you get
Cron definitions in code
Zero-config Deno Deploy scheduling
No overlapping cron executions
Gotchas
- Deno Deploy Classic shuts down July 20, 2026
Deno Deploy Classic, which hosts Deno.cron, is being permanently shut down on July 20, 2026; all cron jobs will cease to function unless migrated to the new Deno Deploy platform.
- 1M requests/month free
Cron invocations are billed at the same rate as inbound HTTP requests and count against the 1 million requests/month free-tier cap; overages are not allowed on the free plan.
- 15h CPU time/month
Free plan includes 15 hours of total CPU time per month across all deployments; note this does not apply to Classic (only new Deploy platform).
- 20GB egress/month
Free tier is capped at 20 GB of outbound bandwidth per month across all deployments.
- 350 GB-h memory-time/month
Free plan allows 350 GB-hours of memory-time per month; applicable only to new Deno Deploy platform, not Classic.
- Max 20 active apps
Free tier allows at most 20 simultaneously active deployments across the organization, limiting how many separate cron-bearing projects can coexist.
- Production deployments only
Deno.cron only executes on production deployments, not preview/branch deployments, limiting testing and staging workflows.
- No SLA or email support
Free plan has no reliability SLA and no email support; only community Discord is available, making it unsuitable for critical scheduled tasks.
- 1-day log retention
Free tier retains logs for only 1 day, making debugging and auditing of cron execution history very limited.
- No wildcard subdomains
Free plan does not include wildcard subdomain routing, restricting multi-tenant cron application patterns.
- Cron timing variance up to 1 minute
Deno Deploy does not guarantee precise cron firing times; invocation may occur up to 1 minute late from the scheduled time.
- Deno runtime lock-in
Deno.cron is available only within the Deno runtime and Deno Deploy; there is no equivalent for Node.js, Python, or other runtimes.
- Static cron definitions only
Cron tasks must be defined at module top-level scope at deploy time; dynamic scheduling at runtime requires a separate Deno Queues API.
- 60 deployments/hour
Free plan allows a maximum of 60 deployments per hour, which can constrain rapid iteration on cron definitions.
Sources
-
"Requests/month Allowed inbound HTTP requests to your deployments per month | 1M"
https://deno.com/deploy/pricing/ -
"Deno.cron invocations are charged at the same rate as inbound HTTP requests to your deployments."
https://docs.deno.com/deploy/classic/cron/ -
"Sunsetting on July 20, 2026 Deno Deploy Classic will be shut down on July 20, 2026. We recommend migrating to the new Deno Deploy platform."
https://docs.deno.com/deploy/classic/cron/ -
"The Deno.cron() API works the same way on the new Deploy. Your existing cron job code should work without modification."
https://docs.deno.com/deploy/migration_guide/
