Computers
for agents
Sandboxes aren't enough.
Give your agent a real computer and get back to building
Machines that Remember
Real hardware-isolated Linux computers for agents, evals, and tools.
The bill goes to zero when nobody's home.
Need more control? Fly Machines lets you tune every lever.
Coding Agents
Every agent gets its own Linux box. A Sprite checkpoints itself while the agent works, so harnesses like Claude and Codex find everything where they left it.
Personal agents
Hermes, Pi, Openclaw… whatever your flavour, an agent with access to your inbox and calendar shouldn't live on your laptop. Give it a Sprite that sleeps until it's needed and wakes up remembering everything.
MCP servers
Run every MCP server in its own Sprite, with persistent disk, and egress policy. Pay only for the tool calls you use.
Untrusted code
Run it in a hardware-isolated VM. A clean baseline per request, so no two users ever share state. Egress-locked and disposable.
Agent-built apps
Every Sprite has an HTTPS URL. The app your agent built stays exactly where it was created and goes live. Nobody migrates anything.
A Real Durable
Filesystem
Everything's still there when you come back.
The
Sprite Block Device
means Sprites can go to sleep without dying.
-
Object-storage backed, so it's infinitely scalable
-
Roll back to any checkpoint in seconds
-
No SDK or object-store gymnastics
Sprites Block Device is currently in private beta. Sign up to receive early access.
Nothing to Manage
The agent does the setup, and you get your afternoon back.
-
No disk sizing
Your disk grows as you write it, up to 100 GB, and you're only billed for the bytes you actually put there.
-
Automatic checkpointing
The Sprite checkpoints itself automatically, so there's always a recent one waiting.
-
Sprites Connectors
Connect a service once for your whole org, and every Sprite can reach it. Nobody pastes a token.
Grow without drama
Scale from side project to production without rewriting your infrastructure
Keep the same primitives at every scale: no rearchitecting when you grow, and no platform migration when you get big. The API you start with is the API you keep.
- 18+
- Regions worldwide
- <1 second
- Machine boot time
- 500ms
- Deploy time, typical
- 99.9%
- Uptime SLA
A Connection to Everything
Sprites are social creatures. Your credentials shouldn't be. Your Sprites reach other services through the API gateway that holds the credential. The token never lands on the Sprite.
-
Configure a connector once
Enable a connection to OpenRouter, Github, Slack, or any HTTP API. Configure once, connect as many Sprites as you like.
-
Granular permissions
Grant access on purpose: by Sprite name, by label, or down to a single endpoint, so a Slack bot can post messages and never touch admin.
-
Auto key rotation
Rotate once and every Sprite has the new credential. Cut off a single Sprite and the rest never notice.
Teams building on Fly.io
-
Airtable
-
Kilocode
-
Builder.io
-
Hatchet
-
Pocketbase
-
Supabase
-
Liveblocks
-
Replicate
-
Trigger.dev
-
Neon
-
Grafbase
Support that knows the stack
Our support team writes code.
When you hit a wall, you talk to someone who's been there.
-
“The Fly support team diagnosed a subtle networking issue in our multi-region setup in under an hour. Real engineers, real answers.”
Platform Engineer
Series B startup
-
“Well, I have to say this is the best support I have ever received from any company. When I sent my initial request I expected to be brushed off as is the norm for non-standard, doesn’t fit the script tech problems. To have what is essentially a step-by-step guide in my inbox first thing in the morning is amazing, I can see why the devs like fly.io.”
Staff Engineer
Fintech
-
“It was useful to be able to speak to fly.io directly. I found [the team] to be very knowledgable and he helped me get clarity around areas I was stuck with, plus he offered me insight in areas I didn’t even know about. Fly.io has been a great experience from the moment I signed up. Keep it up!”
Founder
AI-first product