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.

Need a dedicated database? AWS RDS on Shuttle: Postgres, MySQL or MariaDB, each its own instance. Default: 2 vCPU, 1 GB memory, 20 GiB storage. Same annotation style: #[shuttle_aws_rds::Postgres] pool: PgPool

Push to GitHub, and Shuttle pulls the latest code, builds it and deploys the updated app. Connect a repository in the console, turn on automatic deployments, pick a branch.

Learning Rust, one concept and one hour at a time ↓

Bring your lambda code as is. Dedicated infrastructure keeps state across requests, has no cold start and can run long-running threads.

Your servers, your cloud, or your garage.

Four starters from the Shuttle site, each with its source code and a post explaining how it works, step by step ↓

Secrets, the Shuttle way: Put them in Secrets.toml (and Secrets*.toml in .gitignore) Add #[shuttle_runtime::Secrets] secrets: SecretStore to main Call secrets.get("MY_API_KEY") Local runs can use Secrets.dev.toml.

The Shuttle MCP server ships with the Shuttle CLI 0.56+. Your AI coding assistant gets Shuttle's docs plus the tooling: deploy services, fetch logs and work with the console, right from the editor. claude mcp add Shuttle --scope user -- shuttle mcp start

Fastest way to build & ship Rust apps. Get resources and deploy your apps with a few lines of code. Simple. Easy. Joyful. github.com/shuttle-hq/shuttl…