Rust hosting cargo build, then live.
Push to GitHub. We read Cargo.toml, build your program in release mode and start it. Every deploy waits for the new version to answer before visitors see it.
- Rust1.98
- Builds withcargo build --release
- Port8080, in PORT
- Priced byWhat it uses
We read your code, so you don't write a build script.
Every build shows what we found and each command we ran, line by line. Anything we found, you can change in the app's settings.
| File | What we do with it |
|---|---|
Cargo.toml | Rust, and the program to start: the first [[bin]] it names, or the package's own name. |
Cargo.lock | Your crates' exact versions, so the build uses exactly what you tested. |
tanzahost.json | Optional: system packages, like the ones a crate needs to link, and the build and start commands. |
Small, fast, and started in a moment.
We start ./target/release/ and your program's name. Your app listens on the port in PORT, which is 8080.
Release builds
Every deploy is built with --release, the way you'd ship it.
Low memory
A Rust API often holds a few dozen MB, and you pay for what it really holds, not a plan's size.
Any framework
Axum, Actix Web, Rocket, Poem or plain Hyper: anything that listens on a port works.
Deploys that never take you down.
The new version starts beside the old one. Visitors switch only once it answers its health address, “/” unless you choose another.
If it fails, nothing changes
A build or a “before going live” command that fails stops the deploy, and the version before it keeps serving your visitors.
Watched for five minutes
If the new version stops by itself within five minutes, visitors go back to the previous one, and we tell you.
Roll back in one click
The version before, deployed again without downtime.
Workers, tasks and a database next door.
Add what a real app needs beside its web process, each with the app's code and variables.
- Up to 5 workers for queues and background jobs, and up to 10 scheduled tasks, as often as every minute, in UTC.
- PostgreSQL with connection pooling, MySQL or Valkey in the same project: attaching one adds DATABASE_URL or REDIS_URL to your variables.
- Logs live, a terminal in your browser, and the numbers for memory, processor and requests.
A Rust app, priced in the open.
Say a Rust API holds 0.03 GB of memory and uses 1% of a processor, awake all month. You pay for that use, hour by hour, from your wallet. The limits you set cost nothing by themselves.
reading today's prices