Three concentric rings
Ring 1 — Framework-shipping developers (the base)
Fly.io's founding audience: developers who write code in Phoenix, Rails, Django, Laravel, JavaScript, Rust, Python, Go, and want to deploy it globally without AWS/GCP overhead. Evidenced by:
- Content marketing cadence — branded publications per stack: Phoenix Files, Laravel Bytes, Ruby Dispatch, Django Beats, JavaScript Journal.
- Docs top-level nav — "Languages & Frameworks" section treated as peer to "Fly Machines."
- CLI-first onboarding —
flyctl+fly launchis the documented first step. No drag-and-drop. No AI chat.
Ring 2 — AI / agent builders (the new surface)
New with Sprites. The pitch: hardware isolation for running AI-generated code safely, and per-instance dedicated resources so "agents run better on Sprites." Evidenced by:
- Hero line: "Run AI-generated code in complete safety."
- Sprites landing-page framing: "agents that scale to millions of users", "scalable agents", "persistent or ephemeral execution."
- No AI/agent-specific product in the docs index yet — this audience is being sold via marketing, not yet solidified in structured docs. Indicates a go-to-market in-flight, not a mature product line.
Fly is pre-positioning against the OpenAI Agents SDK default-provider list (Blaxel, Cloudflare, Daytona, E2B, Modal, Runloop, Vercel). Sprites is the vehicle. If CreateOS wants that same slot, they are the competition for that listing, not for the Replit dashboard.
Ring 3 — Enterprise / compliance buyers
Lighter than Replit's enterprise surface but present:
- Compliance package — $99/mo add-on for HIPAA-compliant workloads.
- Support plans — $29/mo starter, custom enterprise pricing with SLAs and emergency support.
- Security surface in docs — SSO, OIDC, tokens, compliance — a top-level docs section.
- Contact:
[email protected]for custom enterprise deals.
Compared to Replit's "Google, Microsoft, Stripe, PayPal" logo wall, Fly.io's enterprise surface is colder — no named customer logos, no public case studies in the captured content.
What Fly.io is NOT targeting
- Non-coders / indie makers / solopreneurs — no prompt-to-app hero, no templates-for-non-developers, no monetization stack. Everyone lands on "Install flyctl."
- Design-led builders — no Figma import, no visual canvas, no named design systems. The opposite of Anything.com.
- Beginners / learners — docs assume Unix comfort. There is no "learn to code" pathway.
Contested vs. Replit / Anything.com
| Segment | Fly.io | Replit | Anything.com |
|---|---|---|---|
| Indie makers / solopreneurs | ❌ Not targeted | 🟡 Ring 1 | ✅ Sole ICP |
| Individual developers | ✅ Core | ✅ Ring 2 | 🟡 Quietly (not marketed) |
| Agent / AI builders | ✅ New via Sprites | 🟡 Implicit (agent runtime is their own) | 🟡 Implicit |
| Enterprise devs | 🟡 Compliance + support | ✅ SBOM, SSO, logos | ❌ Absent |
See Enterprise Developers, Indie Makers and Solopreneurs.
Sources
- fly.io homepage
- fly.io/docs
- fly.io/pricing
- phoenix.new