Compare / RunLater vs Supabase Cron
RunLater vs Supabase Cron
Supabase Cron schedules jobs inside your project's Postgres database. It is the right tool for SQL that runs where the data lives. To call a URL it uses pg_net, which sends the request without waiting for it, gives up after 2 seconds by default and keeps responses for 6 hours. RunLater waits up to 5 minutes for a response, retries failures and keeps every response for 7 to 90 days.
Supabase Cron details are from their own pages (listed under the table), checked November 10, 2026. Prices change; check their page before you decide.
| RunLater | Supabase Cron | |
|---|---|---|
| What it runs | Any public URL, any method, your headers and body | SQL, a database function, or an HTTP request through pg_net |
| HTTP timeout | Configurable per request, 1 to 300 seconds | 2 seconds by default (timeout_milliseconds) |
| Response history | Every run logged with status, timing and response body; kept 7, 30 or 90 days by plan | pg_net keeps responses for 6 hours, in unlogged tables a crash can wipe |
| Retries | Up to 10 retries with exponential backoff, set per request | None built in: a failed request is not resent |
| Jobs at once | Runs are sent by our scheduler, not your database | No more than 8 jobs running at the same time is recommended |
| Minimum interval | 1 minute | 1 second, on Postgres 15 or later |
| Timezone | Timezone per request, daylight saving handled | GMT in the docs examples |
| One-time request at an exact time | Yes: exact date and time, or a cron expression | No: recurring cron or interval schedules only |
| Price | $15/mo (25,000 runs), $39/mo (100,000 runs), $149/mo (500,000 runs); yearly at 10x monthly (two months free) | Part of your Supabase project; jobs use your database's resources |
Sources for the Supabase Cron column, read November 10, 2026:
Pick Supabase Cron if
- The job is SQL or a database function: it runs next to the data with no network hop.
- You need runs more often than once a minute.
- Your app is on Supabase and the HTTP calls are quick ones where a missed run is fine.
Pick RunLater if
- The endpoint takes longer than 2 seconds, or you need to know it succeeded.
- You want failed calls retried and every response kept for more than 6 hours.
- You need a one-time call at an exact date and time, in your own timezone.
- You would rather not run HTTP traffic from your production database.
Errors people hit with Supabase Cron
Try it on your own endpoint
The fastest way to compare is to point both at a real URL. RunLater's trial lasts 14 days and you can cancel from the billing page before it ends.
Other comparisons
See how it works: quick start and your first webhook.