Plan your migration

A Heroku alternative operated in France

Your application runs on Heroku and you are considering what comes next. SailOps brings together containers, managed PostgreSQL, cache, jobs and operational visibility. Explore the useful service mappings, practical differences and migration steps to decide whether it fits your application.

What has Heroku announced?

On 6 February 2026, Heroku announced a sustaining engineering model focused on stability, security, reliability and support. The platform continues to operate and existing Enterprise subscriptions can renew, while Enterprise Account contracts are no longer offered to new customers. The announcement does not set a shutdown date.

Which services can you map to SailOps?

This table compares uses, without promising identical configurations, options or commitments. Follow the sources to check each mapping before making a migration decision.

On HerokuOn SailOpsWhat to check
Web dynoContainer and gateway

Configure the port, domain and route to your application.

Worker dynoContainer without public exposure

Run your background process without a public route.

One-off dynoOne-time job

Suitable for a script or migration, without implying every interactive console behavior.

Release phaseNo direct equivalent

A job can run the task. You must arrange sequencing and deployment gating.

Heroku SchedulerCron job

Review the cron expression, time zone and concurrent execution policy.

Heroku PostgresManaged PostgreSQL

Check your target version and the extensions your application uses.

Heroku Key-Value StoreRedis-compatible Valkey cache

Test clients and commands. Public Valkey connections do not support TLS on SailOps.

Config varsEnvironment variables

Restart the container to apply changed values.

Custom domains and ACMGateway and automatic certificates

Configure DNS and the HTTPS listener; SailOps handles issuance and renewal.

Logs and logging servicesLogs, metrics and operational alerts

Compare your retention and analysis requirements with the documented features.

PipelinesNo direct equivalent

Your CI can manage deployments through the API.

Review AppsNo direct equivalent

SailOps documentation does not describe automatic creation linked to pull requests.

Add-on marketplaceNo direct equivalent

Evaluate dependencies individually; the SailOps Marketplace catalog has been retired.

What changes when you deploy an image?

On SailOps, you supply an image available in a registry. The documented deployment workflow does not take a git push as its input. Prepare a Dockerfile for your application, then a CI workflow that builds and publishes the image. If you already have a suitable image, you can start with it.

The CI/CD guide includes GitHub Actions and GitLab CI examples: build the image, publish it and update the container through the API. Your team owns that delivery workflow. For schema migrations, explicitly decide when the task runs and how a failure should stop the release.

The service formerly called Heroku Data for Redis has been named Heroku Key-Value Store since 11 October 2024. Do not assume that changing an address is sufficient: check versions, authentication and your client’s connection settings too.

How should you migrate from Heroku?

Rehearse the workflow in a test environment. Agree on acceptance criteria and the conditions for returning to your existing setup before switching production traffic.

  1. Prepare the image

    Collect dependencies, the startup command and listening port. Build and test your image, then deploy your web and worker processes separately.

  2. Transfer PostgreSQL

    Check versions and extensions, then rehearse a logical export with pg_dump and a restore with pg_restore using a compatible archive format. Validate data and permissions before the final transfer.

  3. Prepare the cache

    Separate disposable cached data from sessions and work queues. Decide what needs transferring or resetting. Test private connections and the behavior of your application’s clients.

  4. Recreate configuration

    Copy the required variables, update service addresses and recreate scheduled tasks. Check which values the application actually uses after restarting.

  5. Prepare the domain and cutover

    Configure the gateway, route and domain. Coordinate the final data transfer, application writes and DNS change. Then verify the certificate and essential user journeys.

  6. Validate before retiring the old setup

    Review errors, background processing and metrics. Retire the previous application and its dependencies only after your team has accepted the result and reviewed the rollback plan.

How should you prepare your budget?

Use SailOps pricing and the estimator to size your scenario. Compare the resources you need, then include migration work and the period when both environments run in your budget. This page does not promise savings against your current bill.

Estimate my architecture

When is SailOps the wrong choice?

SailOps currently holds none of the ISO 27001, SOC 2, SecNumCloud or HDS certifications. If your contract requires one of these, SailOps does not meet that condition today.

Heavy reliance on buildpacks, add-ons or Review Apps means reworking your delivery process. Check your cache requirements too: SailOps Valkey offers neither standby replication nor automatic failover, and public connections lack TLS. If these features are essential, Redis compatibility alone is not sufficient grounds to approve a migration.

Questions before you migrate

Do I need to rewrite my application?

Not necessarily, but it depends on how it works and what it relies on. First check that it runs in an image, then test service connections and supporting tasks. That exercise identifies the adaptations your application actually needs.

How long does a migration take?

There is no universal duration. It depends on data volume, dependencies, business acceptance and downtime constraints. A rehearsal helps you build a relevant schedule instead of relying on an arbitrary estimate.

Where is my data hosted?

The documentation places customer compute, databases, backups, volumes and websites in Paris, France, within the European Union. Check this stated scope against your own requirements when evaluating the platform.

Can I migrate without interruption?

This page does not guarantee that. Plan how writes are handled, how clients behave during the DNS change and how you could return to the previous setup. Your architecture and testing determine an acceptable procedure.

Do I have to leave Heroku immediately?

The announcement of 6 February 2026 does not set a shutdown date. You can use this comparison to evaluate an option and prepare decision criteria, without treating the announcement as a requirement for an emergency migration.

The next step is in your project

Evaluate SailOps with your application

Start with an image and a test environment. For a specific dependency or an architecture review, speak with the team before scheduling your production cutover.