Please meet shuttle! We are a distributed YC-backed team working on an open source, Rust-native platform for deploying apps with zero infra hassle.
In order to deploy your app, all it takes is one annotation on your main function and you're good to go!
The fun doesn't end here, however. Modern web applications are complex beasts - you need a front-end, back-end, infrastructure to run your code, databases, queues etc. Today, all of this can be quite overwhelming and daunting, especially at the beginning; going through consoles, choosing and provisioning the right services, wiring them up, setting up deployments..
With shuttle, your infrastructure is defined implicitly in your application code, meaning you don't have to leave your IDE (or project folder) to get your infra up and running. At compile time, we automatically provision the resources you need, granting you compile time assurance that you'll get the right infrastructure setup right out of the box.
If you are building an MVP, pitching Rust inside your company or for your side-project, you can get started with shuttle in no time. It takes less than 2 minutes to create, setup & deploy an example hello-world app using axum (web application framework from tokio). So take it for a spin!
Love the idea!
Seems like it might save me quite a lot of time and money starting new rust projects - especially to avoid the pains of AWS.
Tho makes me wonder, can the provisioned infra be accessed somehow?
i.e. when provisioning a Postgre DB, is it possible to get the access data so it is accessible via other tools and backends?
thanks, glad you liked it - feel free to join our discord community https://discord.gg/shuttle and we'd be happy to show you around!
> Tho makes me wonder, can the provisioned infra be accessed somehow? i.e. when provisioning a Postgre DB, is it possible to get the access data so it is accessible via other tools and backends?
After deploy, we give you the connection string for public connections. For most DBs, however, communications from services happen on the internal network
3 comments
[ 4.5 ms ] story [ 15.3 ms ] threadPlease meet shuttle! We are a distributed YC-backed team working on an open source, Rust-native platform for deploying apps with zero infra hassle.
In order to deploy your app, all it takes is one annotation on your main function and you're good to go!
The fun doesn't end here, however. Modern web applications are complex beasts - you need a front-end, back-end, infrastructure to run your code, databases, queues etc. Today, all of this can be quite overwhelming and daunting, especially at the beginning; going through consoles, choosing and provisioning the right services, wiring them up, setting up deployments..
With shuttle, your infrastructure is defined implicitly in your application code, meaning you don't have to leave your IDE (or project folder) to get your infra up and running. At compile time, we automatically provision the resources you need, granting you compile time assurance that you'll get the right infrastructure setup right out of the box.
If you are building an MVP, pitching Rust inside your company or for your side-project, you can get started with shuttle in no time. It takes less than 2 minutes to create, setup & deploy an example hello-world app using axum (web application framework from tokio). So take it for a spin!
It takes less than 2 minutes to create, setup & deploy an example [hello-world](https://github.com/shuttle-hq/shuttle/tree/main/examples/axu...) app using axum (web application framework from tokio). So take it for a spin!
We are in alpha so constructive criticism and feedback are extra welcome!
Tho makes me wonder, can the provisioned infra be accessed somehow? i.e. when provisioning a Postgre DB, is it possible to get the access data so it is accessible via other tools and backends?
> Tho makes me wonder, can the provisioned infra be accessed somehow? i.e. when provisioning a Postgre DB, is it possible to get the access data so it is accessible via other tools and backends?
After deploy, we give you the connection string for public connections. For most DBs, however, communications from services happen on the internal network