Overview

Every integration is an optional package — forze[postgres], forze[redis], and so on — that implements Forze contracts for one backend. They share a common shape: a client and ports in kernel/, concrete adapters/, and execution/ deps + lifecycle modules you wire exactly as shown in Wiring. Your handlers never import them; they resolve ports from the context.

Per-backend pages cover the specifics — configuration, schema expectations, and caveats. The authoritative, always-current set is the [project.optional-dependencies] extras in pyproject.toml; each forze[<name>] maps to the <name> extra.

Available integrations¶

Each row maps to a forze[<extra>] package; their precise contract coverage is on each integration's page. Two key backends need no extra at all: the self-hosted local KMS and the in-memory mock.

The remaining extras are not backend integrations: dst and cli are tooling (deterministic simulation testing and the forze command-line tool), and zstd adds the zstd codec for portable archives.

Install one or several at once — uv add 'forze[fastapi,postgres,redis]'.