Powered by the community.

Running Shuttle locally, in detail ↓

Shuttle Heroes recognises developers who made exceptional contributions. What it asks: help others on Discord and GitHub, spread the word, create tutorials, posts and videos, and keep contributing to push Shuttle forward.

Get a database by just asking for one in your Rust code.

Inside the shuttle repo. cargo-shuttle is the CLI, runtime runs your service, codegen generates the proc macros, ifc parses Infrastructure from Code, builder holds the Docker build recipes, and mcp is the Shuttle MCP server.

Everything your app writes to stdout and stderr, plus the build logs: shuttle logs shuttle logs --latest shuttle logs --raw shuttle deployment list Add tracing to Cargo.toml and info!() just works, no subscriber setup needed.

Need more power? Scale vertically from the code itself: #[shuttle_runtime::main(instance_size = "m")] Sizes run from xs (0.25 vCPU, 0.5 GB) up to xxl (8 vCPU, 16 GB).

Custom build steps, still experimental: three optional scripts at the project root. shuttle_prebuild.sh runs before cargo build shuttle_postbuild.sh runs after it shuttle_setup_container.sh prepares the runtime image A nightly toolchain is two lines.

Shuttle inside a cargo workspace ↓

Your own domain in three steps: 1. Buy a domain 2. Point a DNS record at Shuttle 3. shuttle certificate add <domain> HTTPS on your own domain, right next to the default project address.