Frequently Asked Questions

We build and deploy every project in its own container. This gives you safe isolation from other users, and also across all the projects that are owned by your account.

Your code is analyzed and built on our servers. The first time you introduce additional resources in your code, like the first time you use a database, we will add that resource to your project and wire it automatically to your deployment.

Of course! When you deploy a project on Shuttle, your API becomes available at a URL of the form ${project_name}.shuttleapp.rs. And since Shuttle is compatible with any of the common frontend hosting solutions (Vercel, Netlify, etc), you just have to make your API calls to the URL of your project, and you’re up.

For details on how to serve static files with shuttle, check out our docs: Shuttle static folder

For a tutorial on how to build & deploy a simple full-stack app using Next.js & Rust, check out this tutorial: Deploying a NextJS frontend with Rust, in one go

You can bring your lambda code to shuttle as is. And we run it on dedicated infrastructure that keeps the state of your services across requests, has no cold-start and can even have long-running threads, all of which is not possible on AWS Lambda.

Absolutely! And it’s quite easy. Check out this section of our docs for the steps to do so: Custom Services

Yes, you can create a SeaORM connection from the sqlx pool Shuttle passes to you when you provision a SQL database. You can take a look at the example here.

Certainly. Just create a Shuttle.toml file in the folder where your Cargo.toml is and add name = "your-project-name.