What it does
First-party managed Postgres database, attached to Fly apps via private networking. A top-level docs section. Framed as "Managed" (Fly operates it) vs. the legacy "Fly Postgres" (user-operated on Machines).
Target ICP
Framework-shipping developers who want a real database without operating it. Django, Rails, Phoenix apps all default to Postgres.
Inputs / Outputs
- Input: DB size spec + region + app to attach to.
- Output: Connection string + Postgres instance with automated backups and maintenance.
How it works
Provisioned via flyctl or the dashboard. Connects over Fly's private network so latency is minimal and the DB isn't public-internet-addressable by default.
Pricing / limits
Metered — compute + storage billed separately.
❓
specific $/GB/mo and $/vCPU pricing. Not on the landing page.
UX entry points
fly postgres create(or similar) — not captured precisely.- Docs: top-level "Managed Postgres" section.
Differentiators (claimed)
- Private-network default — DB is reachable from app Machines without public IPs.
- Same platform pricing as Machines — metered per second, no tier step-functions.
Integrations
- First-class with every supported framework (Django, Rails, Phoenix all default to Postgres).
- Tigris (object storage) and Upstash (Redis) frequently used alongside.
Versus the builder category
| Axis | Fly Managed Postgres | Replit DB | Anything.com DB |
|---|---|---|---|
| Surface | Explicit — top-level product | Bundled, hidden | Top-level dashboard nav |
| Pricing | Metered separately | Included in plan | Included in plan |
| Target user | Dev who writes SQL | App the builder generates | App the builder generates |
Takeaway: same technology (Postgres), completely different buyer. Fly sells it to developers; builders hide it behind an ORM or a schema-editor UI.
Sources
- fly.io/docs — Managed Postgres section