A guide for the platform you're on.
Each guide maps your current setup to Komuta step by step. Start reading, or skip ahead and talk to us.
Heroku, Fly.io or your own servers
If it runs in a container, it runs on Komuta. Tell us what you have.
Four steps. Your old platform keeps running until you're sure.
- 01
Talk to an engineer
Tell us what you run today: services, databases, queues, domains. No sales script.
- 02
Get a plan and a price
A written migration plan and your expected monthly bill on Komuta, before anything moves.
- 03
Move with us
We help with the database import, environment variables and DNS cutover. You test on a Komuta address first.
- 04
Run on Komuta
Credits land on your account, and we stay close through your first month.
Easy to come, easy to leave.
A migration program is only fair if leaving is just as simple. Everything you run on Komuta comes out with standard tools.
How we handle your data›docker build .
# your app is a standard container from your own Dockerfile
›pg_dump -Fc $DATABASE_URL
# your database, any time
›komuta.yaml
# your infrastructure as one exported file
›30 days
# to export everything after an account closes
Program terms
Scope and conditions of the Komuta migration program.
- Who it's for
- Teams moving production workloads to Komuta from another hosting platform or their own servers.
- Credit support
- Up to USD 1,000 in Komuta credits. This is a ceiling, not a flat amount: what you get depends on what you move and is agreed on the migration call. Credits are used for Komuta resources.
- Migration help
- Free architecture review, a migration plan with a cost estimate, hands-on help with your data, variables and DNS cutover, and setup support during your first month.
- How to start
- Book a call from this page, or write to [email protected].
- Pricing after that
- Normal Komuta pricing: a free plan for one small service, paid packages from USD 9 a month, and a spending limit on every account.