Background jobs that finish.
4.1MRuns this week
38msMedian pickup
99.98%Completed first try
30 daysHistory retained
Run history
Every attempt, in the order it happened
Scroll to sweep a batch. Each job records when it was picked up, how long it took, and what it returned. Nothing is summarised away.
6Runs completed
send-receipt-email
0.9s
sync-stripe-invoices
3.2s
rebuild-search-index
5.1s
export-account-csv
2.4s
post-webhook-delivery
retry 2 · 1.6s
nightly-usage-rollup
6.8s
01
Enqueue from anywhere
One HTTP call, or a client library in the language you already use. The job is durable the moment Vault Inc answers.
02
Runs on your workers
Vault Inc calls an endpoint you own. Your code stays in your infrastructure, with your secrets and your database.
03
Fails loudly, retries quietly
Per-job backoff, a cap on attempts, and a dead letter queue you can inspect and drain rather than guess at.
We deleted the cron box, the Redis instance and about four hundred lines of retry code we were quietly frightened of.
Ferrule Northbound Kestrel&Co MARLOW tinbox
Put your slow work somewhere it can be watched.
Free for the first 100,000 runs a month. No card until you pass it.