---
title: "Fly.io: computers for agents"
description: "Sandboxes aren't enough. Give your agent a real computer and get back to building."
---

# Fly.io: computers for agents

Fly.io is a public cloud that runs code on hardware-isolated Linux virtual
machines, close to users, in 18+ regions. It has two compute products and
a database:

- **Sprites** — full Linux computers for agents. Persistent or disposable,
  checkpointed automatically, asleep and free when idle. https://fly.io/sprites.md
- **Fly Machines** — fast-booting VMs for running what the agent builds:
  web apps, APIs, background jobs, untrusted code. https://fly.io/machines.md
- **Managed Postgres** — production PostgreSQL with backups, failover and
  connection pooling. https://fly.io/mpg.md

Prices for all three: https://fly.io/pricing.md. Sign up: https://fly.io/app/sign-up

## Sprites: machines that remember

Real hardware-isolated Linux computers for agents, evals, and tools. The
bill goes to zero when nobody's home. What people run on them:

- **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 in private beta —
request access at https://fly.io/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 per
  Sprite, 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.

## Sprites: where your agent runs. Machines: where you run what it builds.

- **Sprites** sleep when the agent stops, and wake up with the
  filesystem, the running services and the installed dependencies right
  where they were. Checkpoint before a risky change, roll back in
  seconds. https://fly.io/sprites.md
- **Machines** are hardware-isolated VMs that boot in under a second, run
  close to your users, and scale out to tens of thousands when the
  traffic arrives. The app your agent finished needs somewhere to live.
  https://fly.io/machines.md

## 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.

| | |
| --- | --- |
| Regions worldwide | 18+ |
| Machine boot time | <1 second |
| Deploy time, typical | 500ms |
| Uptime SLA | 99.9% |

## Connectors: 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.

Set one up at https://fly.io/dashboard/personal/sprites/connectors

## Customers

Teams building on Fly.io include Kilocode, Builder.io, Hatchet, Phonic, Supabase, Firecrawl, Plastic Labs, Replicate, Steel, Delos and Lemonade.

## Support that knows the stack

Our support team writes code. When you hit a wall, you talk to someone
who's been there. https://fly.io/support/

> “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

## Get started

Give an agent a computer:

```
curl https://sprites.dev/install.sh | bash
sprite login
sprite create my-sprite
sprite exec -s my-sprite -- ls -la
```

Deploy an app:

```
curl -L https://fly.io/install.sh | sh
fly launch
```

New Sprites organizations get $30 in trial credit. Sign up at
https://fly.io/app/sign-up; the launch guide is at
https://fly.io/docs/getting-started/launch/

## More

- Sprites: https://fly.io/sprites.md · docs https://docs.sprites.dev/ · API https://sprites.dev/api
- Machines: https://fly.io/machines.md · docs https://fly.io/docs/machines/ · API https://fly.io/docs/machines/api/
- Managed Postgres: https://fly.io/mpg.md · docs https://fly.io/docs/mpg/
- Pricing, every region and plan: https://fly.io/pricing.md
- Setting up an agent-ready environment on a Sprite: https://fly.io/sprites/agent-ready.md
- Authenticating — flyctl, access tokens, the MCP servers: https://fly.io/auth.md
- Documentation index: https://fly.io/llms.txt
- Status https://status.flyio.net/ · Community https://community.fly.io/ · Support https://fly.io/docs/about/support/