Bindings

Select the provider that runs each job.

A job binding selects the provider that accepts and executes your application’s tasks. The commerce fixture uses the same shape:

jobs: { default: docker(inngest()) },
defaults: {
  bucket: "assets",
  cache: "requests",
  realtime: "default",
  "agent-state": "agents",
  jobs: "default",
},

The binding is part of the compiled deployment plan. It records the provider profile, capability evidence, execution limits, and the worker identity used for publication. A job may use an explicit binding when a service needs a different provider or environment.

An explicit job selects a named service with service: "default"; it does not use a binding field. If no service is specified, the compiler resolves the application’s default jobs binding and records the selected adapter in the manifest.

The compiler rejects a job whose requested execution mode is not provided by its binding. Run relkit jobs capabilities to inspect the selected provider and its actual limits.

Provider guides: Inngest, Trigger.dev, and Effect MQ.