Skip to content
Comparison

HostStack vs Fly.io

A flat-priced EU PaaS for teams that want managed databases that are actually managed — not a Postgres cluster you operate yourself.

Why developers choose HostStack

Fully-managed PostgreSQL with daily backups, point-in-time recovery, and version upgrades handled for you. Fly's "Postgres" is an unmanaged cluster you operate via flyctl
Real EU data residency in Nuremberg or Helsinki with a DPA at signup. Fly has EU regions but is US-incorporated (Schrems II territory)
Flat €5/mo Starter, €15/mo Pro, €39/mo Team — predictable invoice. Fly bills per-machine + per-second usage, with separate line items for shared CPU, dedicated CPU, RAM, storage, and bandwidth
Managed MySQL, MariaDB, MongoDB, and Redis included. Fly only ships unmanaged Postgres, Upstash Redis (third party), and Tigris object storage (third party)
TypeScript SDK and Terraform provider — first-party, not community-maintained
Cron jobs, background workers, and queues bundled. Fly Machines can run them but you wire the scheduling yourself

Feature comparison

FeatureHostStackFly.io
Web services
Background workers
DIY on Fly Machines
Cron jobs
DIY scheduler
Static sites
Fully-managed PostgreSQL
Unmanaged cluster
Managed MySQL / MariaDB / MongoDB
Managed Redis
Upstash (3rd party)
Object storage
Tigris (3rd party)
Custom domains + SSL
GitHub auto-deploy
GitHub Actions setup required
Docker runtime
CLI tool
TypeScript SDK
Multi-region apps
EU data residency
DE, FI
Region-pinned, US-incorporated
DPA included
Enterprise only
Flat pricing
Per-machine + per-second

Pricing comparison

TierHostStackFly.io
Free / Hobby€0/mo — 1 service foreverFree $5 credit/mo (used quickly)
Starter€5/mo flat — 3 services + DB + queue + search~$5-15/mo (machines + Postgres cluster)
Pro€15/mo — 10 services + 3 DBs + 5 buckets$25/mo per shared-1x machine + $20/mo per Postgres node
Team€39/mo — 30 services + 6 DBs + unlimited seatsCustom; per-org billing add-on
EgressFree$0.02/GB above plan in NA/EU

When NOT to choose HostStack

Fly.io is the better fit in some cases. Here's when we'd tell you so.

You actually need a multi-region app with low-latency reads everywhere. Fly's anycast routing across 30+ regions is purpose-built for that; we run single-region per project.
You want bare Fly Machines to script your own runtime / orchestrator on top. We're an opinionated PaaS; if you're looking for "raw VMs with TLS" Fly is closer.
You're happy operating your own Postgres cluster (HA failover, version upgrades, backup verification). That hands-on workflow is fine — it just isn't what a "managed" PaaS gives you, and our pricing assumes you don't want to do it.
You depend on Fly's GPU machines. We don't offer GPU instances yet.

Migrate from Fly.io

1

Open a HostStack account

Sign up with an email at hoststack.dev — no card during migration. Create a project in Nuremberg or Helsinki.

2

Connect your repo

Install the HostStack app on the GitHub, GitLab, or Bitbucket repo you deploy from Fly. Framework auto-detection fills in build and start commands; your fly.toml structure carries over conceptually.

3

Import your services and env vars

Export Fly secrets (fly secrets list -a APP) and push them with hoststack env bulk svc_… KEY=VAL KEY=VAL …. The [services] block in fly.toml maps to a single HostStack service.

4

Move your Postgres

Provision a fully-managed PostgreSQL on HostStack and stream a pg_dump from your Fly Postgres cluster directly into it. Compare Postgres options in our managed PostgreSQL Europe 2026 buyer's guide.

5

Cut over DNS

Point your A/AAAA records (or CNAME) at HostStack and wait for the Let's Encrypt cert to provision. Rotate any Fly-issued credentials and decommission the Fly app.

Ready to switch?

Start for free. No credit card required. Migrate in minutes.