Migrating to Bahriya

Move an existing application from another platform to Bahriya, step by step.

6 articles

• Migrate from Docker Compose to Bahriya

  A docker-compose.yml describes several services that run together on one host: your app, maybe a worker, a database, a cache, and the wiring between them. Bahriya runs the same services, but each one is deployed and scaled individually across the regions you choose — there is no single compose up that brings the whole stack up at once. This guide maps a compose file onto Bahriya resources and walks the move.

  4 min

• Migrate from Fly.io to Bahriya

  If you are running on Fly.io you are already most of the way to Bahriya: you have a Dockerfile, you deploy an image, and you think in terms of regions. The move is largely a matter of translating your fly.toml into Bahriya container settings, recreating your secrets, and choosing which regions to run in. This guide maps the pieces and walks the cutover.

  3 min

• Migrate from Heroku to Bahriya

  Heroku builds your app from source using a buildpack and a Procfile, runs it on dynos, and bolts on managed add-ons for databases and caches. Bahriya keeps the same building blocks but makes each one explicit: you produce a container image, deploy it across the regions you choose, and wire configuration in as environment variables and secrets. This guide maps each Heroku concept to its Bahriya equivalent and walks the move end to end.

  4 min

• Migrate from Railway to Bahriya

  Railway runs each part of your app as a service, builds from your repository, and stores configuration as variables shared across services. Bahriya uses the same service model but deploys a container image you build, across the regions you choose, with configuration supplied as environment variables and secrets. This guide maps each Railway concept to Bahriya and walks the move.

  3 min

• Migrate from Render to Bahriya

  Render runs your app as a web service, background worker, or cron job, built from your repository and configured through environment groups or a render.yaml. Bahriya uses the same service shapes but deploys a container image you build, spread across the regions you choose, with configuration supplied as environment variables and secrets. This guide maps each Render concept to Bahriya and walks the move.

  3 min

• Migrating to Bahriya

  Moving an application to Bahriya follows the same shape whatever you are coming from. Your app becomes a container, your configuration becomes environment variables and secrets, and your public URL is served automatically over HTTPS with your own domain layered on top. This overview walks the general path; the platform-specific guides linked at the end fill in the details for where you are today.

  4 min