Deplexo vs Fly.io
Fly.io runs apps on Firecracker microVMs distributed globally with usage-based pricing. Deplexo uses containers with fixed resource limits and has a free tier that needs no credit card.
Feature comparison
| Feature | Deplexo | Fly.io |
|---|---|---|
| Runtime isolation | Secure container | Firecracker microVM |
| Free tier | 128 MB RAM, 1 app, no card required | Requires credit card; free allowance on small VMs |
| Pricing model | Fixed plans: $0 / $5 / $10 | Usage-based (per vCPU-second, per GB-month) |
| Predictable monthly cost | Yes | No, it varies by usage and region |
| Global multi-region | No | Yes, 30+ regions |
| Container security defaults | Locked-down security defaults | microVM kernel boundary (hardware-level isolation) |
| Build method | Dockerfile (default) or auto-detect via deplexo.yaml | Via flyctl scanner (limited detection) |
| Config file required | No (deplexo.yaml optional) | fly.toml required |
| Custom Dockerfile | Yes | Yes |
| Git providers (OAuth deploy) | GitHub, GitLab, Bitbucket, Codeberg | GitHub (via flyctl or GitHub Actions) |
Isolation model
Fly.io runs each app instance inside a Firecracker microVM, a lightweight VM with its own kernel, which gives strong hardware-level isolation between tenants. Deplexo uses secure containers with a locked-down security profile applied by default. Both isolate tenants, using different mechanisms.
Pricing model
Fly.io uses usage-based billing: you pay per vCPU-second of compute and per GB-month of memory. Costs scale with usage and vary by region. A credit card is required even to access the free allowance.
Deplexo uses fixed-tier pricing. The free tier needs no credit card, and paid plans cost the same each month however heavily you use the allocated resources.
Global deployment
Fly.io's main feature is deploying your app to 30+ regions with anycast routing to the nearest instance. Deplexo does not provide multi-region deployment. Apps run in the EU (Germany). If you need global distribution, Fly.io is the better choice.
FAQ
- Can I migrate from Fly.io to Deplexo?
- Yes. Connect your GitHub repo to Deplexo. If the repo has a Dockerfile, Deplexo uses it. Copy your environment variables from
fly secrets listto Deplexo's env vars panel. Thefly.tomlfile is ignored. - Do I need a fly.toml?
- No. Deplexo builds from your Dockerfile by default. An optional
deplexo.yamlconfigures auto-detect builds. Thefly.tomlfrom your repo is not read. - Does Deplexo support Fly Machines (always-on microVMs)?
- Deplexo containers are always-on within their resource limits, similar to Fly Machines in "started" state. Deplexo has no suspend/wake mechanism, so the process keeps running.
- Does Deplexo require flyctl or a CLI?
- No. Deployment is configured entirely in the web dashboard. You connect a repo, set environment variables, and deploy without a CLI. A
deplexo.yamlin the repo can override build settings if needed.
Ready to deploy? Sign up free. No credit card required.