Sprites

HostedPersistent environment

Linux computers for agents

Homepage Docs Pricing

Scanned 12 Oct 2026 · Schema v5 · features v21

From: $100/mo
Usage-metered CPU, actual memory and hot/cold storage; optional subscription allowances described incompletely by FAQ.
Free tier: Yes
Card requirement unconfirmed.
Isolation: Firecracker microVM
shares only the hypervisor
Regions: —
No Sprites-specific placement/region-selection list found. Fly Machines regions are deliberately excluded.
Capabilities: 20 / 61
6 partial · 35 fail · 0 not assessed
Agent readiness: 11/11 · 10/11
read · drive, pre-login surface

Advertised for

AI agent code execution · Untrusted code isolation · Persistent dev environments · Long lived services · CI CD tasks · Agent swarms

Built for

Developers, then technical

· https://fly.io/sprites/ — CLI/code-first quickstart and four SDKs.
· https://fly.io/pricing/ — actual CPU-hour, RAM GB-hour and storage rates.
· https://docs.fly.io/sprites/concepts/connectors — credential policy/gateway and network control vocabulary.

01 Pricing Usage-metered CPU, actual memory and hot/cold storage; optional subscription allowances described incompletely by FAQ.

Tier	EntryPay as you go	Hero (FAQ only; conflicting pricing page)
Price	$0.0385/CPU-hour + $0.021875/RAM GB-hour; hot $0.000683/GB-hour, cold $0.000027/GB-hour	$100/month plus standard-rate overages
Includes	No per-Sprite fee; $30 conditional one-time trial credit; egress not currently metered.	1200 CPU-hours, 4800 RAM GB-hours, 150GB storage; Standard support; 100 running +100 warm, unlimited cold.
Storage	—	150 GB
vCPU hours	—	1200 h
Memory gb hours	—	4800 h
Transfer overage	$0/GB	—
Storage overage	$0.01971/GB	—
vCPU hours overage	$0.0385/h	$0.0385/h
Memory gb hours overage	$0.021875/h	$0.021875/h

CPU-hour + actual RAM GB-hour + storage GB-hour; compute free while warm/cold.·Card required: unconfirmed·fly.io

Overages: CPU $0.0385/hour; actual RAM $0.021875/GB-hour; hot $0.000683/GB-hour while awake; cold $0.000027/GB-hour while data exists. Sprites egress unmetered today; Machines egress separate.

02 Runtime Each fact carries its source; dots show confidence. Open a row for the evidence.

Isolation & lifecycle

Isolation primitive

Firecracker microVMshares only the hypervisor

Persistence

100GB filesystem persists across warm/cold. Warm suspension freezes memory/processes; cold drops them and services restart from disk. TCP connections drop on both.

Snapshots / forks

Yes

Resources & limits

Storage

100GB filesystem per Sprite, billed on used blocks; local hot cache plus durable object storage. S3 Block Device/ext4 backend is early access per org.

Limits & quotas

8 vCPUs and fixed 100GB storage per Sprite; memory platform-managed and autoscaled, no fixed published RAM ceiling. PAYG create10/min; Adventurer60/min to Mythic240/min; Hero100running+100warm, cold unlimited.

GPU

Access

Deploy interface

cliapisdkmcp

SDK languages

GoJavaScriptPythonElixir

Network & secrets

Egress controls

Yes

Secrets

Connectors hold encrypted provider credentials in org database, deny access by default and inject them in gateway requests; Sprite never receives provider token.

Bring your own cloud

Placement & use

Jurisdiction

Fly.io, Inc., US vendor; Sprites workload placement/region selection undisclosed.

Advertised workloads

AI agent code executionUntrusted code isolationPersistent dev environmentsLong lived servicesCI CD tasksAgent swarms

03 Capabilities 20 pass · 6 partial · 35 fail · 61 of 61 assessed

Supported — Documented on the public surface and verified.
Partially supported — Exists with caveats: gated, thin, or enterprise-only.
Not supported — Checked and not offered.
Not assessed — Scanned before this capability was tracked. Not a lack.

Compute & storage 3/11

Persistent diskStorage that survives restart/stop (not ephemeral-only).

Supported

Object storageManaged S3-compatible / blob object store the platform PROVIDES to a user's workloads (buckets, presigned URLs). DISTINCT from persistent-disk (block/volume attached to an instance) and from a self-host dependency (source.self_host.deps[]=["object-storage"] is an infra dep to RUN an OSS tool — the opposite direction). SCOPE varies and matters: native first-class (Railway Buckets, Cloudflare R2) vs a sibling SKU / extension (Fly Tigris, Bunny Storage, DigitalOcean Spaces) — record which in the evidence quote / note. Admitted v15.

Not supported

Snapshots / forkingSnapshot or copy-on-write fork of a running instance (filesystem-only counts). Whether the snapshot also restores memory + running processes is recorded separately by memory-snapshot (v19).

Supported

Live-state (memory) snapshotsA snapshot / checkpoint / pause captures a running instance's MEMORY and PROCESS state and restores it, so running processes continue where they left off instead of a freshly booted instance with the same files. Counts whether user-triggered (snapshot, checkpoint, pause-to-storage) or used to restore pre-initialised state (memory snapshots for fast cold starts). Distinct from snapshots-forks (any snapshot or fork, including filesystem-only; a product passing that key may still fail this one) and from scale-to-zero (an idle-cost property; suspension may or may not keep memory). Actor multiplexing (see scale-to-zero) records its live-state half here — only when the suspended actor's MEMORY/process state is what comes back, not a freshly booted worker with the actor's files.

Partially supported

Scale to zeroIdle instances suspend at no / negligible cost. ACTOR MULTIPLEXING (many suspended stateful actors sharing a small pool of pre-warmed workers, woken on request — Agent Substrate, AX, kagent; Rivet's hibernating actors) has NO key of its own (proposal REJECTED v20) — score the idle-cost half HERE and the live-state half under memory-snapshot; the oversubscription ratio / density is a performance characteristic the registry does not key.

Supported

GPU computeGPU-backed instances available.

Not supported

Multi-regionCompute placeable in more than one geographic region.

Not supported

Sandbox templates / custom imagesBuild reusable sandbox/VM images from an OCI image or Dockerfile (a base you fork instances from).

Not supported

Cloud-init / ignition configCustomise a VM / microVM / instance at boot via cloud-init (or ignition) user-data — the same boot-metadata interface as AWS/Azure/GCP. Inject packages, users, SSH keys, files, and run-commands declaratively at launch. Distinct from sandbox-templates (a PREBUILT image you fork instances from) — this is PER-LAUNCH declarative customisation, not a baked image.

Not supported

Desktop / computer-use sandboxA virtual desktop (GUI) for LLM computer-use — browser + desktop automation, often via noVNC/VNC.

Not supported

Selectable isolation runtimeThe user chooses the isolation runtime per workload / environment / sandbox from more than one option (e.g. microVM vs gVisor vs plain container, native namespaces vs gVisor, gVisor vs VM). Records the CHOICE; the isolation_primitive facet still records the best-evidenced primary. A platform that switches runtime automatically without a user choice (e.g. gVisor forced for GPU) does not pass on that alone.

Not supported

Networking & delivery 4/9

Automatic HTTPSTLS endpoints provisioned automatically per workload.

Supported

Built-in reverse proxyPlatform routes external traffic to workload services.

Supported

Custom domainsBring-your-own domain via CNAME/DNS.

Not supported

Public preview URLsShareable per-deploy / per-branch URLs.

Supported

Direct public IPv6Per-instance stable public IPv6 for raw TCP/UDP (beyond a managed HTTPS proxy) — e.g. mosh / raw sockets.

Not supported

Egress controlsConfigurable OUTBOUND network policy — egress firewall / allowlist / egress proxy on traffic LEAVING a workload. Scoped to OUTBOUND only (v15): private-network REACHABILITY between a user's own services is private-networking, not this. Static-egress-IP belongs here (an outbound concept).

Supported

Private networkingA platform-internal private network between a user's OWN services — service-to-service connectivity, VPC, service mesh, and/or service discovery, not exposed to the public internet. DISTINCT from egress-controls (OUTBOUND firewall/allowlist), reverse-proxy (PUBLIC inbound ingress), and direct-ipv6 (per-instance PUBLIC addressing). Admitted v15.

Not supported

Email send / receiveSend and/or receive email from the workload.

Not supported

Edge KV storeA globally-replicated key-value store read from WITHIN an edge runtime at the PoP (low-latency, eventually-consistent) — Cloudflare Workers KV, Deno KV, Fastly KV Store, Akamai EdgeKV, Vercel Edge Config. Distinct from first-party-db (a managed DATABASE service you provision and connect to) and from http-query-api (HTTP access to an external store) — edge-kv is colocated with the edge compute and read at the edge.

Not supported

Developer access 5/10

Public APIDocumented programmatic API.

Supported

OpenAPI specMachine-readable OpenAPI / Swagger spec published.

Supported

CLIOfficial command-line tool.

Supported

SDKOfficial client library/libraries.

Supported

SSH accessDirect SSH into workloads.

Partially supported

Filesystem APIRemote file operations over the API (list/read/write/watch/copy/upload) without SSH.

Supported

Git deployDeploy from a Git repo / push-to-deploy.

Not supported

Private container registryHosted private image registry.

Not supported

E2B-compatible APIDrop-in compatibility with the E2B sandbox API/SDKs — existing E2B client code runs against this product by changing the endpoint/domain + key, with no business-code changes. E2B itself passes as the reference implementation. Distinct from public-api / sdk (the product has its own API — this key says it also speaks another vendor's) and from self-host-oss (a self-hosted E2B-compatible server is scored on both).

Not supported

HTTP data APIQuery / read / write the stored DATA over plain HTTP/REST (or GraphQL) WITHOUT the native protocol driver (Postgres wire / Redis RESP) — agent- and edge-friendly data access via fetch(). The DATA plane; distinct from public-api (a control-plane / management API). Auto-generated-from-schema REST/GraphQL (PostgREST, pg_graphql) is a flavour of this.

Not supported

AI & agents 5/12

Built-in coding agentShips a first-party AI coding agent in the product.

Not supported

Agent skillsInstallable / declarable agent skills or tools.

Supported

AI app builderPrompt-to-app / vibe-coding generation surface.

Not supported

MCP serverExposes a Model Context Protocol server for agents.

Supported

MCP clientActs as an MCP client / consumes MCP tools.

Not supported

MCP-server hostingRun/host MCP servers as a workload on the platform (distinct from exposing a first-party MCP control server — that is mcp-server).

Partially supported

LLM gatewayRoutes LLM API calls through the platform (multi-provider).

Partially supported

BYOK for LLMsBring-your-own LLM provider keys.

Supported

Model inference API (first-party)A FIRST-PARTY hosted LLM/model inference API — the provider serves its OWN catalogue of (usually open-weight) models behind a (typically OpenAI-compatible) endpoint, billed per token. Distinct from llm-gateway (a multi-PROVIDER proxy/router for YOUR calls to external providers like OpenAI/Anthropic) and from byok-llm (bring your own provider keys) — here the platform IS the inference provider, serving its own models.

Not supported

Autonomous QA agentA first-party AUTONOMOUS AI agent that QA-TESTS a running app / implementation — exercising it like a real user (clicking through flows, checking behaviour) and reporting bugs/defects (often back to a coding agent, or before a human review). Distinct from built-in-agent (a code-AUTHORING agent — this one VERIFIES the result, it does not write the feature; a product can ship both), from ai-guided-code-review (organises a diff for a HUMAN to review — not an autonomous tester), and from observability (runtime metrics/logs, not active testing).

Not supported

Credential-injection proxyThe platform holds real secrets OUTSIDE the workload and injects them on the wire (an egress / broker proxy swaps a placeholder or phantom token for the real credential on matching outbound requests), so code running in the sandbox — e.g. an untrusted agent — never sees or can exfiltrate the real key. Distinct from secrets-management (storage + injection INTO the workload as env vars/files — the workload holds the secret) and from egress-controls (outbound allow/deny POLICY; a product can have an allowlist without injecting credentials, and vice versa).

Supported

Preinstalled coding agentThe platform installs and launches a THIRD-PARTY coding agent (a harnesses.yml entry — Claude Code, Codex, OpenCode, Pi ...) inside a workspace/sandbox it provisions, with the agent's auth wired in (your own account or API key), so you start an agent session rather than an empty box. Distinct from built-in-agent (a FIRST-PARTY agent the vendor ships) and from harnesses[] (which records that a harness CAN target the product, not that the product runs it for you).

Supported

Data 0/4

First-party databasePlatform-provided managed database.

Not supported

Database branchingCopy-on-write branch of a DATABASE (schema + data) as a dev-lifecycle primitive — branch your data like code, usually instant via a metadata operation. Distinct from snapshots-forks (forks a running compute INSTANCE / VM state) and from preview-environments (a full per-PR environment that may USE a DB branch). For a data product a CoW branch maps HERE, not to snapshots-forks.

Not supported

Vector searchFirst-class storage, indexing, and similarity search of vector embeddings — a native vector type/index or a managed vector DB. The data-layer primitive for RAG / semantic retrieval.

Not supported

Ephemeral instant DB (no-signup)Provision a working, usable instance via a single command / HTTP call with NO account, signup, or card — typically time-boxed (expires unless claimed). A zero-onboarding path an agent can hit directly.

Not supported

Platform & operations 1/6

Scheduled tasksCron / scheduled job primitive.

Not supported

Durable workflowsDurable execution / long-running workflow primitive.

Not supported

Preview environmentsA full EPHEMERAL environment spun up per PR / branch — compute + addons + (often) a DB branch — torn down on merge. More than preview-urls (which is just a shareable URL for one deploy).

Not supported

Built-in observabilityFirst-party metrics / logs / tracing / APM / profiling included in the platform (no third-party stack required to see what a workload is doing).

Supported

Managed CI/CD runnersPlatform-hosted, drop-in CI/CD runner VMs (GitHub Actions / GitLab), typically faster and cheaper than the CI vendor's own hosted runners, billed per runner-minute; isolated + ephemeral per job. Distinct from git-deploy (push-to-deploy of an APP) and scheduled-tasks (cron) — this is managed CI COMPUTE you point your existing pipelines at.

Not supported

Project template marketplaceA marketplace / gallery of prebuilt PROJECT STARTER templates (apps or websites) a user clones or launches a new project from and then customises — the "start from a template" surface of a builder / PaaS. Distinct from sandbox-templates (a COMPUTE base IMAGE you fork runtime INSTANCES from — Dockerfile / OCI), from app-builder (the prompt-to-app GENERATION surface — a product can have both), and from one-click OSS-app catalogues / helm-addon-marketplace (deploy a FINISHED app as-is, not a starter you build on).

Not supported

Organisation & security 2/9

Built-in authPlatform-provided authentication / IAM for workloads.

Partially supported

SSO / SAMLEnterprise single sign-on.

Not supported

Secrets managementFirst-class secrets storage / injection.

Not supported

TeamsMulti-user team accounts.

Supported

SharingShare a running workload/resource via link (optionally gated).

Supported

BYOCRuns inside the customer's own cloud account.

Not supported

Deploy into customers' VPCsA SaaS vendor uses the platform to deploy and operate ITS software inside ITS CUSTOMERS' cloud accounts / VPCs (nested or "customer BYOC"), managed from the vendor's control plane. Distinct from byoc (your own workloads in your own cloud account).

Not supported

Workload identityThe platform gives each workload its own verifiable identity (OIDC token, SPIFFE SVID, cloud IAM federation) that it exchanges for short-lived credentials, so no long-lived static secret is stored or injected. Distinct from secrets-management (stores / injects static secrets) and credential-injection-proxy (swaps real secrets in on the wire).

Partially supported

Self-host / OSS coreOpen-source core that can be self-hosted.

Not supported

04 Agent readiness Pre-login surface · counts, not a grade

Can an agent read it?

parse-ability · docs, metadata, machine-readable surfaces

11/11

9 full · 2 partial · 100% of applicable checks

llms.txt
Supported
“https://fly.io/llms.txt plus substantive https://docs.fly.io/llms.txt; docs include Sprites.”
llms-full.txt
Supported
“https://docs.fly.io/llms-full.txt HTTP200, 2,858,737 bytes full docs including Sprites; retained pointer.”
robots.txt AI policy
Partially supported
“https://fly.io/robots.txt silent on AI UAs, default-allow; disallows /speedrun only.”
JSON-LD
Partially supported
“Homepage has Organization/WebSite + Sprites Service with name/description; SoftwareApplication is Fly platform, not Sprites with offers.”
Sitemap
Supported
“https://fly.io/sitemap.xml index links landing sitemap with >5 URLs and Sprites paths.”
Meta tags
Supported
“Homepage title Sprites | Linux computers for agents; substantive description + OG image/title/description.”
Markdown negotiation
Supported
“Accept:text/markdown returns clean Sprites Markdown HTTP200 (12,698 bytes); docs also offer .md.”
Content efficiency
Supported
“Readable text/HTML bytes = 6.49% on canonical Sprites homepage; server-rendered public content.”
Docs discoverable
Supported
“Sprites Docs linked in header, reachable unauthenticated, redirects to docs.fly.io/sprites.”
Machine-readable pricing
Supported
“Structured HTML and Markdown tables agree on usage rates; subscription ladder conflicting, recorded scan_issue.”
No anti-bot wall
Supported
“Public content accessible HTTP200; no fetch-blocking bot challenge. Consent banner does not prevent body fetch.”

Can an agent drive it?

act-ability · APIs, SDKs, MCP, credentials, webhooks

10/11

7 full · 3 partial · 91% of applicable checks

Public API
Supported
“https://sprites.dev/api redirects to public Sprites reference; documented bearer API.”
OpenAPI spec
Supported
“https://api.sprites.dev/openapi.json HTTP200 valid OpenAPI3.1.”
MCP server
Supported
“Hosted https://sprites.dev/mcp documented by ecosystem and https://fly.io/.well-known/mcp/server-card.json.”
SDK packages
Supported
“Official Go, JS/TS (@fly/sprites), Python (sprites-py), Elixir clients in ecosystem and fetched GitHub readmes.”
Auth documented
Supported
“Sprites-specific bearer tokens/CI setup in CLI auth guide; OAuth PKCE flow in fly.io/auth.md. Linked discovery currently404 noted.”
Self-serve credentials
Partially supported
“Token creation at account/dashboard; sprite login browser requires human approval. Fly Machines programmatic tokens not transferred.”
Webhooks
Not supported
“No signed Sprites lifecycle webhook delivery documented; hosting incoming webhooks is different.”
CLI tool
Supported
“Official sprite CLI for create/exec/checkpoint/proxy/auth.”
Error model
Partially supported
“Auth guide gives Sprites API JSON error example; OpenAPI lists HTTP401/404 descriptions and stream error schemas, no comprehensive common error contract.”
Rate limits documented
Partially supported
“Homepage FAQ creation rates10/min PAYG through240/min Mythic and org concurrency; no comprehensive API rate response-header contract.”
Agent config files
Supported
“Read-only /.sprite/llm.txt in checkpoint docs, gateway skills preinstalled, portable plugin package and agent-ready Markdown.”

05 Coding harnesses Which agents and IDEs are documented to run here

Advertised integrations 8

Claude Code Anthropic
Supported
“Explicit Claude Code setup instructions with dedicated Sprites integration.”
Source fly.io
Codex CLI OpenAI
Supported
“Explicit Codex setup instructions with dedicated Sprites integration.”
Source fly.io
Cursor Anysphere
Supported
“Explicit Cursor setup instructions with dedicated Sprites integration.”
Source fly.io
Antigravity Google
Supported
“Explicit Antigravity setup instructions with dedicated Sprites integration.”
Source fly.io
OpenCode opencode
Supported
“Explicit OpenCode setup instructions with dedicated Sprites integration.”
Source fly.io
Pi earendil-works
Supported
“Explicit Pi setup instructions with dedicated Sprites integration.”
Source fly.io
Hermes Agent Nous Research
Supported
“Explicit Hermes Agent setup instructions with dedicated Sprites integration.”
Source fly.io
Gemini CLI Google
Supported
“Gemini CLI preinstalled in base image; own authentication required.”
Source docs.fly.io

Plausible compatibility 0

Derived, not stored: the product passes SSH access, so any CLI coding agent is installable inside it. This is plausible compatibility, not a supported integration.

No general shell access documented, so nothing is derived. Absence is not unsupported.

06 Compliance & regions Standards held, with ordinal rigor; never a score

Certifications held 0

No attestations found on the public surface. Empty means nothing is advertised, after checking, not that nothing was checked.

Regions —

Regions are not disclosed on the public surface.

No Sprites-specific placement/region-selection list found. Fly Machines regions are deliberately excluded.

Legal

Privacy notice Terms of service

07 Company & presence Facts only, not scored

Company

Headquarters: San Francisco, CA, USA; legal/contact address 2261 Market Street #4990
Founded: Parent Fly.io: 2017; Sprites publicly launched January 2026.
Team size: unknown
Hiring: Parent hiring: strategic accounts, fullstack engineering, infrastructure operations, networking.

Notable people

Kurt Mackey (Fly.io team)
Thomas Ptacek (design article author)
Daniel Botha (Sprites blog author)

Activity

Last release: Latest public release-note date: 2026-04-30 (Sprites API); SDK repository pushes are separate. fly.io
Last blog post: 2026-04-01 — Run Paperclip on a Sprite; first listing item, article date confirmed. fly.io

Presence 5

Links found on the public surface scanned; not an exhaustive search.

08 Sources & method How this entry was produced

Public surface only

Everything here was read from sprites.dev's unauthenticated pages, docs, pricing and repository on 12 Oct 2026. Nothing behind a login was used.

Statuses, not scores

Capabilities are pass, partial or fail against a written rubric (features v21). “Not assessed” means the scan predates the key.

Confidence is separate

Each fact carries its own confidence. Low-confidence facts are shown, never hidden, so you can weigh them.

Schema: scan v5
Features registry: v21
Keys tracked today: 61
Assessed on this entry: 61

Something wrong on this page?

Nearby in the atlas

All Persistent environment products →