Keep building your appChoose the right foundation

Building with AI and using Heroku? Check whether its managed runtime fits your project, or whether you want MainPath to connect development, tests and releases on servers you choose.

Versioned build outputs as the foundation for your next project update

Before you moveUnderstand the project

Start with your existing code and the services it depends on.

  1. Check the application

    Your agent first checks whether MainPath supports the stack. A Docker image alone does not make a Heroku app a supported MainPath project.

  2. Map data and services

    List databases, files, workers and add-ons individually. Decide which can stay and which need their own migration.

  3. Prepare the environment

    Map startup behavior and config vars to the new project configuration. Store credentials in managed secrets.

  4. Test in parallel

    Set up a test version and check important workflows. Plan production approval and the domain switch after acceptance.

Two ways to run your appDifferent foundations

Both approaches can run applications. What matters is where the runtime lives and how you want to organize the project.

With Heroku

  • Heroku runs web processes and background workers in managed dynos.
  • Buildpacks prepare application code for its runtime; Docker deployments are available for supported app generations.
  • Databases and other services can be connected through add-ons.
  • A fit when you want to stay in the Heroku model without selecting the underlying servers yourself.
How Heroku works

With MainPath

  • A supported project gets structure, a repository and a prepared test and build workflow.
  • Connect a suitable server and assign it to your project.
  • Web, backend and optional mobile apps can belong to one project, with appropriate separate build steps.
  • A fit when you want server assignment and the path from AI-written code to release organized as a project.
Explore the MainPath project workflow

Your projectOn a connected server

MainPath sets up Docker, a reverse proxy and HTTPS on suitable servers, along with access for deployments. Keep working on code with your AI agent while the pipeline checks and builds your changes.

  • Dev updates after a successful workflow on main.
  • Approve production through the manual release step.
  • Plan servers, databases and additional services around your application.
Connect servers to MainPath

What you want to bringAnd what you set up again

  • Databases and files

    Assess Heroku Postgres and other data services separately. Schema, export, import and application code must fit the target environment.

  • Add-ons and workers

    Map queues, email, file storage and background processes deliberately. An import does not automatically recreate these Heroku connections.

  • Configuration and secrets

    Separate config vars into custom environment values and confidential credentials. Leave generated pipeline and env files in MainPath unchanged.

  • Acceptance and cutover

    Check test data, login, uploads and background workflows. Plan a way back, domain changes and the data cutover before switching production.

Your next project updateWith a foundation that fits

Compare the workflow on a supported project. We can look at your code, services and a useful starting point with MainPath together.

Questions about moving from Heroku

When does staying with Heroku make sense?

If your web processes, workers and add-ons fit Heroku’s managed runtime well, staying can be sensible. A move should address a concrete project need, such as server assignment or a shared workflow for web, backend and mobile apps.

Can I import any Heroku app directly?

No. MainPath imports supported stacks only. Your agent checks the existing code first. A buildpack or Dockerfile does not replace that check; Heroku-specific services and configuration need a separate assessment.

Explore import requirements

What happens to my Heroku Postgres database?

Data migration is a separate task. Check the database type, schema and application code against the target environment, then test export and restoration. MainPath’s prepared backend environment uses MySQL; it does not automatically convert a Postgres database to that format.

Heroku Postgres documentation

Does Heroku support backends, workers and Docker?

Yes. Heroku documents web and worker dynos, as well as Docker deployments for supported app generations. This comparison concerns runtime and project workflow, rather than denying Heroku those capabilities.

Dynos and their roles

Is MainPath always cheaper?

That depends on your projects, resources and the services you need. Compare current plans, server costs and the services in your actual setup. A lower overall operating cost is not a blanket promise.

MainPath plans and pricing

Thank you for your request

We have received your request and will get back to you as soon as possible.

Would you like to talk to us directly?

Choose a time here for an introductory call with Robin.

Open the calendar in a new tab