Supabase Cron
Schedule recurring SQL, database functions, HTTP requests, or Edge Functions from inside Supabase Postgres.
- Card required
- No
Supabase Cron scores 3.5/10 for free value in Schedulers. The main constraint: Available in Supabase projects subject to current project, database, and function limits.
Free value score
3.5 / 10Show the math
Key metrics
What you get
Cron syntax inside Postgres
Can call SQL, HTTP, or Edge Functions
Run monitoring in Supabase
Gotchas
- Max 2 active free projects
The free plan allows at most 2 active Supabase projects, limiting how many separate cron environments you can run simultaneously.
- Project pauses after 1 week of inactivity
Free projects are automatically paused after 7 days of inactivity and require a manual resume, making them unsuitable for low-frequency but always-on cron schedules.
- Shared CPU, no dedicated compute
Free tier runs on shared CPU with 500 MB RAM; dedicated compute is not included, so cron job execution may be slower and less consistent under load.
- No automatic database backups
Automatic backups are not included on the free plan, meaning if a cron job corrupts data there is no point-in-time recovery.
- 1-day log retention only
Cron job run history logs are subject to the free plan's 1-day API and database log retention, severely limiting post-hoc debugging.
- 500 MB database size cap
The free plan includes only 500 MB of database storage; the cron.job_run_details table accumulates run history and counts toward this limit.
- Recommended max 8 concurrent jobs
Supabase recommends running no more than 8 cron jobs concurrently and keeping each job under 10 minutes for best performance on shared infrastructure.
- No backups, branching, or advanced disk
Free tier omits database branching, advanced disk configuration, and point-in-time recovery, limiting safe use in production cron workflows.
- 5 GB egress cap
HTTP-based cron jobs that trigger external requests or Edge Functions are subject to the 5 GB monthly egress limit on the free plan.
- 500K Edge Function invocations/month
Cron jobs that trigger Supabase Edge Functions share the free plan's 500,000 monthly invocation quota.
Sources
-
"For best performance, we recommend no more than 8 Jobs run concurrently. Each Job should run no more than 10 minutes."
https://supabase.com/docs/guides/cron -
"Free projects are paused after 1 week of inactivity. Limit of 2 active projects."
https://supabase.com/pricing -
"Get started with: Unlimited API requests, 50,000 monthly active users, 500 MB database size, Shared CPU • 500 MB RAM, 5 GB egress, 5 GB cached egress, 1 GB file storage"
https://supabase.com/pricing -
"Supabase, the open source database of choice for the vibe-coding world, has raised a $500 million Series F at a $10 billion pre-money valuation"
https://techcrunch.com/2026/06/05/supabase-doubles-valuation-to-10b-in-8-months/
