How much does Fly.io Sprites cost?

Metered at $0.0385 per CPU hour and $0.021875 per GB of memory an hour while a Sprite is awake, plus hot and cold storage, with no per Sprite or bandwidth charge. New users get $30 in trial credits, and plans with included usage range from Hero at $100 a month to Mythic at $2,000.

Does Fly.io Sprites support MCP and tool calling?

Full under the Agentic Index verification standard. Fly.io Sprites publishes public evidence of Model Context Protocol (MCP) support, tool calling, and API or SDK extensibility for connecting agents to external tools. Evidence basis: Sprites are managed through a REST API with a public OpenAPI specification, Python, JavaScript, Go and Elixir SDKs and the sprite command line tool. A hosted MCP server at sprites.dev/mcp, authorized by OAuth, enumerates, creates and destro. Graded from public evidence only against the Agentic Index 14 point capability taxonomy. No vendor pays for placement.

Does Fly.io Sprites have SOC 2, SSO and role based access control?

Full under the Agentic Index verification standard. Fly.io Sprites publishes public evidence of enterprise security and identity controls, covering a compliance posture such as SOC 2 or ISO 27001, single sign on (SSO or SAML), and role based access control (RBAC). Evidence basis: Sprites run in Fly.io organizations, which have admin and member roles and can require single sign on through Google or GitHub. Organization tokens authenticate the command line tool, the API and the SDKs, MCP access is granted by OAuth wit. Graded from public evidence only against the Agentic Index 14 point capability taxonomy. No vendor pays for placement.

Can you bring your own model or route between providers with Fly.io Sprites?

Full under the Agentic Index verification standard. Fly.io Sprites publishes public evidence of bring your own model and bring your own key (BYOK), and of routing tasks between models or providers rather than being locked to one. Evidence basis: The customer chooses the agents and models. Any coding agent or framework can run in a Sprite, and connectors reach OpenAI, Anthropic, OpenRouter, Fireworks, Hugging Face, Ollama Cloud and other model providers with the organization's own k. Graded from public evidence only against the Agentic Index 14 point capability taxonomy. No vendor pays for placement.

Back to vendors

Fly.io Sprites

Q: Who is Fly.io Sprites for?

AI product teams, agent builders, developers

Also known as: Sprites, Sprites by Fly.io, sprites.dev

Visit site

Agent infrastructurefirst party productVerified 2026-11-05

Entry pricePay as you go at $0.0385 per CPU hour and $0.021875 per GB of memory an hour while a Sprite is awake, with $30 in trial credits for new users.Full pricing detail

Fly.io Sprites are persistent Linux microVMs for AI agents that sleep when idle, wake on the next request, checkpoint their filesystem in about a second and reach outside services through connectors that keep credentials out of the machine.

Sprites are Fly.io's Linux computers for AI agents, hardware isolated microVMs that keep their disk, installed packages and files between runs and can be kept for months or thrown away after one task. Each Sprite runs Ubuntu with common languages and AI command line tools preinstalled, has 8 vCPUs, 100 GB of persistent storage and memory the platform scales under pressure, and gets its own HTTPS URL. Fly.io sells Sprites alongside its app hosting platform, with their own API, CLI and price list.

A Sprite pauses about 30 seconds after activity stops, first to a warm state that keeps memory and running processes and wakes in 100 to 500ms, and later to a cold state that wakes in 1 to 2 seconds with only the disk. A request to its URL wakes it and starts its HTTP service, so an agent or app can serve traffic while costing nothing in compute between requests.

Checkpoints copy the filesystem in about a second without stopping the Sprite, also run automatically in the background, and can be restored by a person or by the agent inside. Connectors let a Sprite call GitHub, Slack, OpenAI, Anthropic, Notion, Supabase and dozens of other services through Fly.io's gateway, which holds the credential and denies access until a policy grants it, and a DNS based allowlist set from outside the machine controls other outbound traffic.

Usage is metered at $0.0385 per CPU hour and $0.021875 per GB of memory an hour while a Sprite is awake, with hot and cold storage billed separately and nothing charged per Sprite or for bandwidth. New users get $30 in trial credits, and plans with included usage range from Hero at $100 a month to Mythic at $2,000. Sprites sign in through Fly.io accounts and organizations, which can require Google or GitHub single sign on, and Fly.io offers SOC 2 Type II and a HIPAA package with a BAA signed in advance on its paid plans. Sprites offer no choice of region.

Sprites fit teams that want each agent, user or task to have its own long lived computer that sleeps for free, wakes on a request and keeps its files, and teams that want agents to use outside services without putting keys in the sandbox. They fit less well for buyers who want to pick a data region, a browser their agents can drive, approval steps or traces of an agent's steps, or machines larger than 8 vCPUs and 100 GB of disk.

Vendor details

Canonical URL

https://fly.io/sprites/

Funding status

Sprites is a product of Fly.io, sold alongside Fly.io's app hosting platform.

Company status

first party product

Use cases & customers

Primary use cases

agent sandboxescoding agentsper user agent workspacesuntrusted code executionpersistent dev environments

Target customers

AI product teamsagent buildersdevelopers

Deployment options

SaaSAPI

Integrations

Python, JavaScript, Go and Elixir SDKs, the sprite CLI, a REST API with an OpenAPI specification and a hosted MCP server at sprites.dev/mcp manage Sprites. Plugins connect Claude Code, Codex, Cursor, Antigravity, OpenCode, Droid and other coding agents, framework integrations cover Google ADK, the OpenAI Agents SDK, LlamaIndex, Pydantic AI, Mastra and TanStack AI, and Claude Managed Agents can run its tool environment in a Sprite. The connector catalog reaches more than 40 services, including GitHub, Slack, Notion, OpenAI, Anthropic, OpenRouter, Supabase, Neon, Composio and S3 compatible storage.

In practice

Every user of your app gets their own coding agent workspace, but most sit idle most of the day. Give each user a Sprite that sleeps when idle and wakes on the next request with its files and packages in place, so you pay for compute only while it works.

Your agent needs to open pull requests on GitHub, but you don't want a token sitting in its sandbox. Add a GitHub connector to your organization, allow it for that agent's Sprites, and the agent calls GitHub through Fly.io's gateway, which attaches the credential.

Your agent is about to run a risky migration. Have it create a checkpoint from inside the Sprite first, run the step, and restore the checkpoint if anything breaks.

Sources & related URLs

Related / legacy domains

https://docs.fly.io/sprites https://sprites.dev

Research sources

Agentic Index coverage score

6.5 / 14 capabilities · 46%

Integrations & Tool Calling	Full
Agents call outside services through connectors without holding the credentials. An organization stores a credential once, by OAuth for services such as GitHub or with a key, and the Sprite reaches the service through Fly.io's gateway, which identifies the calling Sprite, checks the connector's access policy and attaches the credential. The catalog holds more than 40 connectors, including GitHub, Slack, Notion, OpenAI, Anthropic, OpenRouter, Supabase, Neon, Composio and S3 compatible storage, a Custom API connector covers any token authenticated HTTP API, and a connector refuses every Sprite until a policy grants access by name, label or endpoint. Sourcedocs.fly.io/sprites/concepts/connectorsread 2026-11-05
Workflow Orchestration	Not documented
There is no workflow logic for an agent's steps. Services keep long running processes up, restart them when they crash and start them in dependency order, and a Tasks API keeps a Sprite awake until work finishes, but sequencing, branching and retrying an agent's work stay in the customer's code or framework. Sourcedocs.fly.io/sprites/concepts/servicesread 2026-11-05
Knowledge Grounding & RAG	Not documented
No retrieval index or knowledge base over the customer's content comes with Sprites. Files an agent reads live on the Sprite's disk, and any retrieval runs in the customer's own code. Sourcedocs.sprites.devread 2026-11-05
Human Oversight & Guardrails	Not documented
Work in a Sprite has no approval step, consent checkpoint or escalation to a person. Connector policies, the outbound allowlist and MCP tokens limited to Sprites with a set name prefix restrict what an agent can reach, and an MCP client may ask before destructive tools run, but nothing on Fly.io's side holds an action for review. Sourcedocs.fly.io/sprites/integrations/remote-mcpread 2026-11-05
Security, Identity & Governance	Full
Sprites run in Fly.io organizations, which have admin and member roles and can require single sign on through Google or GitHub. Organization tokens authenticate the command line tool, the API and the SDKs, MCP access is granted by OAuth with tokens limited by default to Sprites with a set name prefix, Sprite URLs are private to the organization unless made public, and connector credentials are stored encrypted outside the machine. Fly.io offers SOC 2 Type II and a HIPAA package with a BAA signed in advance on its paid plans, without saying whether they extend to Sprites. Sourcedocs.fly.io/security/ssoread 2026-11-05
Observability & Auditability	Partial
The machine is measured and the agent's steps are not. Service logs are kept with timestamps and read through the API, the command line tool and the MCP server, usage endpoints break compute and storage down by organization and by Sprite, managed connectors show usage over 24 hours, 7 days or 30 days, and exec sessions can be reattached after a disconnect. There are no traces or audit trail of what an agent did. Sourceapi.sprites.dev/openapi.jsonread 2026-11-05
Memory & State Persistence	Partial
An agent's working state carries across sessions as machine state. A Sprite's disk keeps files, packages, repositories and databases stored on disk through every sleep, a warm pause keeps memory and running processes, and checkpoints copy the filesystem in about a second, with automatic checkpoints in the background and the last five mounted read only. An agent can checkpoint and restore its own Sprite. This is machine state the developer manages, not a memory layer of stated scope that can be reviewed or deleted as memory. Sourcedocs.fly.io/sprites/concepts/checkpointsread 2026-11-05
Deployment & Data Residency	Not documented
Sprites run on Fly.io's hosted platform with no choice of region and no self hosted option. Creating a Sprite takes a name and URL settings only. Sourceapi.sprites.dev/openapi.jsonread 2026-11-05
Prebuilt Agents / Templates / Packs	Partial
Starting points come as a ready image, plugins and framework integrations. Each Sprite starts from Ubuntu with Node.js, Python, Go, Rust, Java and other languages and AI command line tools preinstalled, plugins connect Claude Code, Codex, Cursor, OpenCode and other coding agents, and integrations cover Google ADK, the OpenAI Agents SDK, Pydantic AI and TanStack AI. These are tools a developer builds with, not prebuilt agents a business adopts. Sourcefly.io/sprites/ecosystemread 2026-11-05
Triggers & Channel Coverage	Full
A request to a Sprite's URL wakes it without the customer's code calling it. If the Sprite's HTTP service is not running when the request arrives, the proxy starts it and forwards the request, so an agent or app served from a Sprite answers traffic while costing nothing in compute between requests. There is no scheduler or webhook. Sourcedocs.fly.io/sprites/concepts/servicesread 2026-11-05
Model Flexibility & Routing	Full
The customer chooses the agents and models. Any coding agent or framework can run in a Sprite, and connectors reach OpenAI, Anthropic, OpenRouter, Fireworks, Hugging Face, Ollama Cloud and other model providers with the organization's own keys, or through a managed option for OpenRouter. Sourcefly.io/sprites/ecosystemread 2026-11-05
APIs / SDKs / MCP Extensibility	Full
Sprites are managed through a REST API with a public OpenAPI specification, Python, JavaScript, Go and Elixir SDKs and the sprite command line tool. A hosted MCP server at sprites.dev/mcp, authorized by OAuth, enumerates, creates and destroys Sprites and runs commands, checkpoints, network policy, services and service logs inside them, and an agent inside a Sprite reaches the same controls through a local management socket. Sourcedocs.fly.io/sprites/integrations/remote-mcpread 2026-11-05
Testing, Debugging & Optimization	Not documented
There are no test cases, scoring or quality gates for an agent's behavior. Sprites can host evaluation and training environments such as Hugging Face OpenEnv through an experimental provider, with the scoring in the customer's own harness. Sourcedocs.fly.io/sprites/integrations/agent-sdksread 2026-11-05
Browser / Computer-use	Not documented
No browser or desktop for an agent to drive comes with Sprites. The Steel Browser Tools connector returns scraped web content, screenshots and PDFs without browser sessions, and an agent that needs to drive a browser installs and runs one itself inside the Sprite. Sourcefly.io/sprites/ecosystemread 2026-11-05

The Agentic Index coverage score grades every vendor Full, Partial or Not documented against the same 14 buyer facing capabilities, from public evidence only. Each capability links to how all vendors in the index score on it. How this evidence is graded

Pricing

Pay as you go at $0.0385 per CPU hour and $0.021875 per GB of memory an hour while a Sprite is awake, with $30 in trial credits for new users.

CPU hours and GB of memory hours while awake, plus hot storage while awake and cold storage until deleted

Trial available

Included quota

Pay as you go includes no usage and allows 10 Sprite creations a minute. Hero at $100 a month includes 1,200 CPU hours, 4,800 GB hours of memory and 150 GB of storage, with 100 running and 100 warm Sprites and email support. Mythic at $2,000 a month includes 28,000 GB hours of memory, 240 creations a minute and premium support.

What is public

Fly.io publishes the Sprites CPU, memory and storage rates, worked cost examples, the Hero and Mythic plan prices and allowances, creation rate limits and its compliance and support add on prices.

Billing mechanics

CPU and memory bill per second while a Sprite is awake and stop when it sleeps after about 30 seconds without activity. Hot storage bills while awake and cold storage until the data is deleted, and plans prepay a monthly allowance of compute and storage.

Cost watchouts

Cold storage bills for as long as a Sprite's data is kept, and checkpoints bill for the changed blocks they retain. Fly.io's HIPAA package costs $99 a month, and paid support runs from $29 to $2,500 or more a month.

Variable cost rationale

Cost follows CPU and memory for every hour a Sprite is awake plus storage for every Sprite and checkpoint kept, so fleets of per user or per task Sprites scale the bill directly, although idle Sprites stop compute charges.

Additional watchouts

Fly.io's own examples put a four hour Claude Code session at about $0.23 and a web app awake 30 hours a month at about $1.05 a month.

Overage / add-ons

Usage beyond a plan's allowance bills at the metered hourly rates.

Sales call required

No, self serve available

Free / trial

$30 in trial credits, one per user and one per organization

Lowest paid plan

Pay as you go metered usage, with Hero at $100 a month the lowest priced plan

Commercial notes

Sprites sign up through a Fly.io account and bill through Fly.io organizations, where compliance packages and paid support are added.

Key ambiguities

Sprites name eight plan tiers but price only Hero and Mythic, and Fly.io's general pricing offers $1 free to start while Sprites offer $30 in trial credits.

Missing data

No prices for the Adventurer, Veteran, Champion, Legend or Epic tiers, and no Sprites specific enterprise terms.

Agentic Index verified 2026-11-05

Official pricing page Docs

Data confidence: medium

Head to head

Fly.io Sprites vs boxdFly.io Sprites vs E2BFly.io Sprites vs exe.devFly.io Sprites vs Freestyle