Schedule HTTP requests on a managed, monitored, alerted pipeline. No infrastructure. No dropped triggers. No mystery failures.
Managed by Desert Forge IT
Built for teams who got tired of "it worked on my server last week."
Redundant workers with persisted queues. If a worker restarts, running jobs reconcile automatically — no dropped triggers.
GET, POST, PUT, DELETE, PATCH, HEAD. Custom headers, bodies, timeouts up to 5 minutes. Signed webhooks, anything REST-shaped.
Status codes, response bodies (to 10KB), durations, error messages. Searchable for up to 90 days on Business.
Email, webhook, Discord, Slack. Fire on failure, recovery, or both. Per-job notification settings.
Configurable retry count and interval, hard timeouts per job. Never fire-and-forget — every attempt shows up in the log.
Programmatic access to everything. API keys, rate limits, a proper REST interface — script your schedules from code.
From zero to scheduled in under a minute.
Any public HTTP endpoint. GET to ping it, POST to send JSON, anything in between. Custom headers for auth tokens, signed webhooks, whatever.
Standard cron expression with timezone. We show you the next five firing times before you hit save, so there's no guesswork.
Every call is logged with status, duration, and response. Failures and recoveries get sent to your email, Discord, Slack, or a webhook of your choice.
Every action in the dashboard has an API equivalent. Your deploy pipeline is your friend.
Start free. Upgrade when you outgrow it. Cancel anytime.
Workers run with Redis AOF persistence and reconcile with the database on restart, so queued jobs survive crashes. Every execution writes to Postgres before completing. Multi-worker deployments share the queue, so a single box outage does not miss triggers.
The job is marked failed (or timeout after your configured limit), logged with the response code and error message, and — if you enabled failure alerts — your configured channels get notified. Configure retries to have us try again before we alert.
Yes, 5-field cron (minute hour day month weekday) with full timezone support. Intervals can go as fine as 30 seconds on Business, 1 minute on Pro.
Each job has its own timezone. The schedule fires at local time in that zone — we handle DST for you. You can also set a default timezone on your account.
Yes. Pausing removes it from the schedule but keeps its configuration and execution history. Resume any time.
Free forever on the Free tier. Pro and Business are monthly subscriptions billed through Stripe. Downgrade or cancel any time — your jobs stay, but plan limits apply going forward.
Takes 30 seconds to sign up. No credit card needed for the Free tier.
Create your first job