Delay is a hosted cron job service. It calls your endpoints on a schedule or on demand, so you don't have to run a cron server.
Most apps need scheduled tasks: syncing data, sending reports, cleaning up old records, checking that services are up. The usual answer is cron on a server you set up and look after yourself. If that server goes down, the jobs stop and nobody is told.
Delay calls your HTTP endpoints on a cron schedule or on demand, retries them when they fail, alerts you when they keep failing, and keeps a log of every run. You write the code that does the work. Delay makes sure it runs.
You give Delay a URL, an HTTP method, optional headers and payload, and a cron expression. It makes the request on schedule, records the result, and retries on failure according to rules you define. If something keeps failing, you get an alert. When it recovers, you hear about that too. Every run, with its status code, response body and latency, is in the dashboard and the API.
For one-off work, push a job to a named queue with a single API call. That covers webhooks, delayed tasks and event-driven work where a fixed schedule doesn't fit.
Team workspaces have admin and member roles. Everyone on the team sees the same crons, queues and run history, so nobody has to share a login.
Everything in the dashboard is also in the REST API: crons, queues and jobs. If your code can make an HTTP request, it can use Delay.
Read the API reference