The catalog documents eighteen Apache 2.0 packages, all published at 0.0.50. Start with quadkit-cli and its api project starter; package availability is shown in the catalog below.
Package dependencies vary by family. Shared interfaces belong in quadkit-contracts; consult Compatibility for published dependencies and the configured package-boundary rules.
Foundation quadkit → Application, container, providers, modules, Result, YAML config quadkit-contracts → Shared protocols, types, exceptions (`typing-extensions` dependency)Web quadkit-web → ASGI, controllers, routing, middleware, OpenAPI quadkit-http → Outbound HTTP client: typed Result errors, retries, timeoutsAI & Agents quadkit-ai-llm → Async LLM providers, streaming, structured output, embeddings quadkit-ai-agents → Typed agent loops, @tool functions, handoffs, HITL checkpoints quadkit-ai-mcp → Model Context Protocol servers & clients (stdio + HTTP/SSE)Data quadkit-sql → Async SQL: repositories, migrations, pooling quadkit-cache → Cache protocol, in-memory and Redis, single-flight helpers quadkit-storage → BlobStore protocol, local and S3, content-addressed keysEvents & Notifications quadkit-events → Event bus, outbox, durable subscriptions, replay quadkit-notification → Email, SMS, push, Slack, and webhook notifications + digestsInfra & Workflows quadkit-tasks → Queues, worker pools, schedules, task console quadkit-workflow → Durable DAG workflows, state machines, approval gates, sagas quadkit-monitor → Counters, histograms, health probes, metrics endpointSecurity quadkit-auth → API keys, MFA, RBAC, sessions, login flowsTooling quadkit-cli → Scaffolding, generators, dev server quadkit-testing → Test harnesses, fakes, fixturesStart from the CLI’s api starter, which includes the web layer; add other installed packages as needed.
uv add "quadkit-cli>=0.0.46,<0.1"quadkit new project my-app --template apiquadkit runThis catalog is the same list as The Ecosystem and the sidebar. Canonical URLs live under /packages/{group}/…. Ungrouped /packages/quadkit-* paths redirect here.
Foundation
The container, the lifecycle, and the contracts everything else builds on.
| Package | Availability | What it does |
|---|---|---|
quadkit | Published | Async-first core: the DI container, application lifecycle, providers, modules, typed config, and the Result model. |
quadkit-contracts | Published | Protocols, shared types, and the exception hierarchy — zero runtime dependencies beyond typing-extensions. |
Web & HTTP
ASGI, routing, middleware, and the Result-to-HTTP bridge.
| Package | Availability | What it does |
|---|---|---|
quadkit-web | Published | The async web layer: controllers with signature-based binding, middleware pipelines, a Result-to-HTTP bridge, and OpenAPI. |
quadkit-http | Published | HTTP client with typed Result errors, retries, timeouts, and a pluggable transport for calling other services. |
AI & Agents
Model providers, agent loops, tool registries, and Model Context Protocol servers & clients.
| Package | Availability | What it does |
|---|---|---|
quadkit-ai-llm | Published | Unified async LLM layer: streaming completions, structured outputs, embeddings, cost attribution, and multi-provider adapters. |
quadkit-ai-agents | Published | Typed agent loops, `@tool` functions, handoffs, human-in-the-loop checkpoints, and structured execution traces. |
quadkit-ai-mcp | Published | Model Context Protocol servers and clients: stdio and HTTP/SSE transports, tool/resource/prompt bridges, and DI wiring. |
Data
Relational and document storage behind repositories.
| Package | Availability | What it does |
|---|---|---|
quadkit-sql | Published | Async SQL repositories: typed rows, migrations, connection pooling, and a repository base over SQLAlchemy and asyncpg. |
quadkit-cache | Published | Cache primitives: a Cache protocol, in-memory and Redis backends, stampede-safe single-flight helpers, and TTL invalidation. |
quadkit-storage | Published | Artifact storage: a BlobStore protocol, local and S3 backends, content-addressed keys, and signed URL helpers. |
Events & Notifications
Publish, subscribe, replay, and deliver multi-channel notifications.
| Package | Availability | What it does |
|---|---|---|
quadkit-events | Published | Event bus, outbox publishing, durable subscriptions, and a timeline/replay API for auditing what happened. |
quadkit-notification | Published | Multi-channel notifications: email, SMS, push, Slack, and webhook delivery with templates, user preferences, and digest batching. |
Infra & Workflows
Background work, durable DAG workflows, and operational visibility.
| Package | Availability | What it does |
|---|---|---|
quadkit-tasks | Published | Background tasks: a queue, worker pools, retries with backoff, schedules, and an HTTP console for observing runs. |
quadkit-workflow | Published | Durable workflows, DAG pipelines, state machines, human approval gates, and compensating sagas with checkpoint/resume. |
quadkit-monitor | Published | Observability: counters, histograms, structured logs, health/readiness probes, and a metrics endpoint. |
Security
Identity, sessions, and access control.
| Package | Availability | What it does |
|---|---|---|
quadkit-auth | Published | Authentication and authorization: API keys, MFA, RBAC, session stores, and login flows wired through the DI container. |
Tooling
Scaffold, run, and test a project: the CLI and the testing harness.
| Package | Availability | What it does |
|---|---|---|
quadkit-cli | Published | The quadkit command line: project scaffolding, generators, a smart runner, and admin commands. |
quadkit-testing | Published | Test harnesses, fakes, and fixtures that boot the real application in-process. |
Next Steps
Section titled “Next Steps”- The Ecosystem — grouped by purpose, with install examples
- Adoption Paths — scaffold → test → ship
- Architecture — the package-boundary rules and their configured exceptions
- Installation — pin
0.0.xand scaffold