Compute primitives
- Fly Machines — hardware-virtualized containers. Per-second billing. Global placement. The base compute unit.
- Sprites — hardware-isolated sandboxes. Dedicated CPU, memory, networking per instance. Positioned for AI-generated code + agents. See Flydotio - Sprites.
- Fly GPUs — GPU-backed Machines. For inference and training. See Flydotio - Fly GPUs.
- Fly Kubernetes — K8s on Fly. Targets workloads teams already run on K8s.
Data + storage
- Managed Postgres — first-party managed Postgres (Fly's second-generation offering after the original user-operated stack). See Flydotio - Managed Postgres.
- Tigris Object Storage — S3-compatible, globally distributed. Partner product, first-class in docs.
- Upstash Redis — managed Redis, partner integration.
- Fly Volumes — persistent disks attached to Machines.
Platform services
- Networking — private networks, public anycast, custom domains, TLS termination.
- Monitoring — metrics, logging, error tracking. Built-in.
- Security — SSO, tokens, OIDC, compliance surface.
Developer surface
- flyctl — the primary CLI.
fly launchis the canonical first command in docs. - Machines API — programmatic compute control. The API underneath flyctl.
- Logs API — stream logs programmatically.
- Extensions API — third-party plugin surface.
Supported stacks (named in docs)
Phoenix, Ruby on Rails, Django, Laravel, JavaScript (Node), Rust, Python, Go, static sites, raw Docker. Each has a dedicated quickstart.
What's NOT advertised
- No in-browser IDE — unlike Replit and Anything.com, no browser-based code editor is a headline feature. Phoenix.new has an editor, but it's scoped to its product, not the Fly console.
- No agent-framework integration in core docs — no "use LangChain with Fly" or "deploy an OpenAI Agent" quickstart on the docs index. This is marketing-in-flight but not yet product-in-docs.
- No visible account UX in captured content — dashboard, deploy screens, Sprites console all uncaptured.
❓
whether Sprites has its own dashboard surface or is managed entirely through flyctl + the Machines API.
Stack architecture synthesis
💭
Fly's tech story is a small set of primitives (Machines, volumes, networking) + per-second billing + global placement. Everything else (Postgres, Sprites, GPUs) is a higher-level product built on the primitives. This is a cleaner architecture story than Replit's bundle-of-features, but it requires more customer literacy to consume. The translator between the primitives and the AI-builder buyer is the open question.
Sources
- fly.io homepage
- fly.io/docs