Product
How JobOrc runs your work.
Your application enqueues jobs. JobOrc owns the queue, execution, retries, and the console you use to observe them.
Architecture
From enqueue to completion.
- 01
Application
SDK or HTTP call from your service.
- 02
JobOrc API
Authenticated enqueue on /v1.
- 03
Queue
Durable storage with concurrency limits.
- 04
Workers
Claim, heartbeat, complete or fail.
- 05
Execution
Your handler runs with a lease.
- 06
Observe
Timeline, retries, DLQ, webhooks.
Capabilities
What you get out of the box.
jobs
Background jobs
Enqueue typed work with a payload. Jobs survive process crashes.
queues
Queues
Isolate workloads with concurrency and rate limits per queue.
workers
Workers
Claim leases, heartbeat while running, complete or fail from your process.
retries
Retries
Server-owned retry policy with backoff. Failures do not disappear.
delayed
Delayed jobs
Run later without building a delay queue yourself.
schedules
Scheduled jobs
Cron-style schedules that enqueue into your queues.
dlq
Dead-letter handling
Inspect exhausted jobs and replay when ready.
observability
Observability
Job timelines, attempts, workers, and console metrics.
webhooks
Webhooks
HMAC-signed callbacks when job state changes.
realtime
Realtime console
Live job state in the dashboard as work progresses.
workflows
Workflows
Multi-step orchestration where your plan includes it.
alerts
Alerts
Notify when failure rates or queues need attention.