Fly
Day 17 after signup
New from Fly.io
Why it works
- Open with a brief framing sentence so readers understand the updates are a compact roundup.
- Give each update its own section, pairing a plain-language explanation with a link to deeper technical details.
- End with a low-friction invitation to reply, making it clear that questions can reach a person.
How it is built
- Greeting and context
- MCP server announcement
- Sprites storage update
- Further reading links
- Reply invitation and sign-off
Email copy
Hi there, Fly.io got a little love this week! If you build with agents on our platform, these blog posts with the details are probably worth a few minutes of your time. Behind Door #1, you have the new Fly MCP server. It gives your agent one connection to both Sprites and to your Fly.io apps. The idea is: the agent prototypes on a Sprite, and when the project is ready for real users, it can create the Fly Machine, volume and secrets it needs (like, from the same conversation where it built the app). You authorize it with a quick browser login, and your agent can only see the apps you choose to share with it. You can read the full post here and connect your agent here. And behind Door #2, we have the nerdy details of a big change under the hood of Sprites. We replaced the original Sprites filesystem with the Sprites Block Device (SBD), a simpler storage layer that's proving to be even more reliable. Checkpoints now come from a single source of truth, and restoring one takes about as long as a restart. You can read the full story right over here. Thanks for building with us. If you have questions about any/all of this, just reply to this email and a human will get back to you. Best, The Fly.io team unsubscribe