Switching from Fly.io to Deplexo
Fly.io is capable but complex. If you want git-push deploys without a CLI, Deplexo is simpler.
Why switch from Fly.io
Fly.io needs the flyctl CLI for most operations, and its usage-based pricing can make costs hard to predict. The Firecracker microVM model is more than most simple web apps and APIs need. Deplexo deploys from a web dashboard with fixed pricing.
What Deplexo offers
No CLI required
Deploy from the web dashboard: connect a repo, set env vars, and deploy.
Fixed pricing
$0/5/10/custom per month, with no usage metering.
Simpler model
Deplexo runs containers and auto-detects your build, so there's no fly.toml to maintain.
Free tier
128 MB RAM, always on, with no credit card. Fly.io has no free tier.
How to migrate
- Connect your GitHub repo to Deplexo.
- Copy secrets from `fly secrets list` to Deplexo's Env Vars tab.
- Deploy. Deplexo ignores fly.toml and either auto-detects your build or uses your Dockerfile.
- Transfer custom domains.
- Destroy your Fly app with `fly apps destroy`.
FAQ
- Does Deplexo support global edge deployment?
No. Deplexo runs containers in a single region. For global distribution, put a CDN in front of it.
- Can I use flyctl with Deplexo?
No. Deplexo uses a web dashboard and REST API, not a custom CLI.
- Does Deplexo support Fly Machines?
Deplexo containers are always on, similar to a Fly Machine in the started state. They have no suspend/resume mechanism.
- What about Fly's multi-process support?
Each Deplexo app runs one process. Use separate apps for separate services.