Start here · Tech directors and managers

For tech directors and managers

JoobQ runs background jobs and long-running workflows for teams that write services in different languages. This page routes you to the facts behind a decision: what it is, how it is deployed, what needs a paid key, and who can do what. Each linked page states only what the code at this release does.

In short

• Three parts. JoobQ Core (MIT) is Redis-backed queues and jobs. JoobQ Pro (licence key) adds the durable workflow engine, workflow schedules, rate limiting, unique-job release modes, alerting and more. JoobQUI is the operator console and the SDK gateway, self-hosted with a deployment licence. See Understanding JoobQ.
• Your infrastructure. The console, the API, the workers and the data run on your servers, on your PostgreSQL and Redis. The portal at app.joobq.io issues and renews licences and Pro keys; each server checks in every 15 minutes, and no request waits on the portal. See Architecture and deployment.
• Nine languages, one set of rules. Crystal uses the libraries; eight SDKs talk to the gateway, which keeps retries, dead letters, leases and waits in one implementation, tested against a real server in every language.
• When a licence lapses, work keeps running. The console's operations routes answer 402, but the SDK gateway keeps serving, so workers and producers continue. See Licensing: Core and Pro.

Read next

Understanding JoobQThe three parts, how a job runs, how a workflow runs.Architecture at a glanceProcesses, stores, several instances, the deployment model.Core and ProWhat needs a key, what happens without one, when the key changes.Security and governanceRoles, credentials, the audit log, what is masked and sealed.Feature matrixEvery feature, its edition and its languages, built from the code.