From model to application

Choose the HTTP, SQL or binary integration for your next boundary.

Keep the model at the center of your application. Add an HTTP adapter, a database driver or a native wire format as you need it. Each integration builds on the same validation rules.

Rust model→Validated data→HTTP · SQL · Cap’n Proto

Choose a boundary

Serve a typed HTTP API

Validate request bodies and response models with Axum and Tokio.

Persist your model

Use SQLx-backed CRUD with SQLite, PostgreSQL or MySQL.

Evolve your database

Plan table changes from model definitions and review the migration.

Generate a native protocol

Derive Cap’n Proto schemas, Rust bindings and validated codecs.

Start with a complete example

The HTTP + database guide connects a validated Axum endpoint to the same SQL model. Start with SQLite locally, then choose an independent PostgreSQL or MySQL driver.

cargo run -p rydantic --example database_api --features axum,sqlite -- --smoke

Add only the features you need

Application boundary	Cargo feature	Continue with
HTTP requests and responses	axum	Axum and Tokio
Local database	sqlite	Database models
Server database	postgres or mysql	PostgreSQL and MySQL
Native binary messages	capnp	Generated bindings
Existing binary schema	capnp	External schema bindings

See Cargo features for combinations and release notes for version details. For typed agents, structured output or model routing, start with the separate RydanticAI crate.