Shuttle

Exciting news! We just shipped Neptune, an open source app deployment platform built for AI agents that gives your agents real DevOps abilities. It reads your code, infers the infra it needs, and generates a simple IaC spec you can inspect, approve, and apply. Think: coding agents that can actually ship safely to AWS. Think of it as: 💻 Take any of your existing apps 🫡 Install Neptune mcp & login 🤖 Tell your agent to deploy Watch it do everything else for you and (super important) it keeps you in the loop at every step, asking for your approval and guidance. We’ve spent most of our time implementing guardrails to make this as safe as if you were doing it yourself. We’re in beta, which means the rough edges are still there and your feedback matters a lot! You can find our templates to deploy in the comments below 👇 Right now we have support for the most basic Amazon Web Services (AWS) products (ECS, S3, SecretManager ), and we support postgres (thanks to Neon) and we are adding more resources as we speak. For now, your apps are all deployed to our a shared tenancy AWS account, and “bring your own cloud” account is coming soon too. If you are also excited about a future where coding agents can help you reliably ship stuff into production, try it and share what you think.

Scaling complex workloads shouldn't be a guessing game. 📉➡️📈 For MasterAI, building an infinite, AI-generated RPG meant managing complex state data - characters, adventures, and real-time chat history. They needed infrastructure that could handle the load without requiring a dedicated DevOps team. By leveraging Shuttle, they secured a backend capable of serious growth: 1️⃣ Horizontal Scaling: Successfully handling 10,000+ daily interactions between users and the AI. 2️⃣ Dedicated Database Management: Shuttle manages their primary database and data persistence automatically, ensuring zero data loss for players. 3️⃣ Production Readiness: They moved from a concept to a live app handling thousands of concurrent sessions without infrastructure bottlenecks. The result? A team that focuses 100% on their Rust application code, not on keeping the servers alive. If your team is managing complex production needs, it might be time to upgrade your infrastructure to a dedicated Growth environment.

If you're not using Claude Skills, you're missing out on your software development workflow. We built a custom Shuttle deployment skill and put it to work. Here's what makes Skills different from MCP servers and slash commands 👇

Unpopular opinion: Infrastructure as Code (IaC) is becoming technical debt. 🚩 We convinced ourselves that writing 500 lines of YAML to spin up a simple microservice was "modern." We convinced ourselves that debugging a state file drift at 4 PM on a Friday was "part of the job." It isn't. It’s a distraction. We are spending 20% of our week babysitting config files instead of building products. We created a wall between writing code and deploying code, and now we are paying the price in lost velocity. There is a new philosophy emerging: Infrastructure FROM Code. Don't write a separate script to build a database. Just annotate your function, and let the compiler build the database for you. We broke down exactly why the IaC era might be ending (and what comes next). Read the full breakdown in the comments. 👇

What’s your favorite feature of the Rust ecosystem that you can’t live without? Let’s share our top picks! 🚀 🦀

Wishing you and yours a wonderful Thanksgiving filled with gratitude and good company. Happy Thanksgiving from all of us at Shuttle 🚀 !

We built a full stack Rust web application from scratch & deployed to Shuttle with Claude Opus 4.5 and the results were mindblowing 🤯 All that with just one prompt, link below 👇

One thing about Opus 4.5 is that it uses all the latest Rust crates 👀

Did Anthropic just kill Gemini 3?