OSS-first docs

These docs teach the open system first: contracts, generated surfaces, runtimes, governance, and incremental adoption. Studio shows up as the operating layer on top, not as the source of truth.

AI index

Integrations

Integrations stay explicit: spec what a provider offers, then bind it per tenant and per app.

The integration model keeps provider behavior out of ad hoc glue code. Define the capability contract first, configure the provider connection explicitly, then bind the integration into app workflows and runtime surfaces with clear ownership.

Binding modelIntegration spec → tenant connection → app binding

That separation is what makes reuse, tenant isolation, and provider swaps practical without rewriting every surface.

Start with the model, then pick a provider

Integration spec model

Define what the provider offers, what configuration it needs, and how the runtime should treat it.

Integration binding

Understand how tenant connections get mapped into concrete app surfaces and workflows.

Models and voice

OpenAIMistralElevenLabs

Messaging and product operations

GitHubSlackTwilioPostmark

Data, storage, and retrieval

QdrantS3 storageGmailGoogle DriveGoogle Calendar

Payments and external workflows

StripePowensCircuit breakersHealth routing
OSS docsintegrationsStart with OSS. Adopt Studio when you want the operating layer.
Previous

Distributed tracing

Trace contract execution across integrations, workflows, and generated surfaces.

Next

Set up integrations

Use reusable integration packages across BYOK, managed, and hybrid modes without leaking provider glue into apps.

Why ContractSpec

Keep educational and comparison content reachable without letting it define the primary OSS learning path.

ManifestoContract-first APISpec-driven development