仅欧洲替代方案 Heroku (Salesforce).

Heroku is the original developer-first PaaS, acquired by Salesforce in 2010 and now part of Salesforce.com Inc. Salesforce is a US corporation, Heroku's default region is in the US, and the EU "Common Runtime" lives in AWS Ireland - meaning your Heroku app is on AWS infrastructure with Salesforce as the contractual processor. Both layers are US-jurisdictional. The sovereign alternative is straightforward: a self-hosted PaaS like Coolify or Dokku on EU infrastructure, or a fully-managed equivalent operated by an EU partner.

United States 仅限 EU 的替代技术栈 11 已梳理的服务
预约通话 先扫描您的域
供应商
Heroku (Salesforce)
总部
San Francisco, CA (Salesforce)
司法管辖区
United States
法律制度
CLOUD Act, FISA 702

"欧盟区域"不等于主权。四个问题决定一切。

数据驻留告诉你数据存放在哪里。主权则告诉你哪个法律体系可以强制访问。这四点的答案必须都成立 - 否则该技术栈就不具备主权性。

驻留

数据物理存储在哪里?

不只是笼统的“在云端” - 而是具体在哪个数据中心、哪个国家、受哪种司法管辖。

次级处理者

您的数据路径中还有谁?

每一个接触数据的供应商:CDN、邮件中继、错误追踪、分析管道。

司法管辖区

哪些法律可以强制披露?

总部位于美国的提供商受 FISA 702 和 CLOUD Act 管辖 - 即使数据存放在法兰克福也不例外。

密钥托管

谁实际持有加密密钥?

如果云服务商同时持有数据和密钥，无论签订何种 DPA，数据对其而言都是可读的。

失败 AWS · Azure · GCP · EU 区域

在司法管辖权和密钥托管上失败。

欧盟数据、美国母公司、默认路径中的美国次级处理者、供应商管理的密钥。

通过 Binadit 托管技术栈

四项全部通过。

托管在欧盟、由欧盟总部基础设施提供。默认路径中零美国次级处理者。客户持有或欧盟 KMS 密钥。在您的第 28 条 DPA 中按名称列出。

为什么团队正在退出 Heroku (Salesforce)

Heroku exits we have run come from three triggers: a customer audit (B2B SaaS) flagging the AWS-Ireland-via-Heroku data path as Schrems II-exposed, the discontinuation of free dynos in 2022 forcing a cost reassessment, or a strategic decision to remove the double provider chain (Salesforce → AWS) which complicates DPA management. Heroku's value is the developer experience; open source alternatives like Coolify, Dokku and Caprover reproduce most of that experience on EU infrastructure.

Heroku (Salesforce) 服务及其仅欧盟等效方案

迁移不是"换一个盒子"。下面的映射是我们为离开以下平台的客户运行的 Heroku (Salesforce) 基于 Schrems II 的考量 - 完全适用欧盟司法管辖，数据链路中不涉及美国母公司。

Dynos (web/worker)

我们改用什么
Binadit 托管云平台。在 GitLab CI 中构建 Docker 镜像并部署到 Kubernetes，为每个分支提供审查环境。
工程说明
Coolify 在 EU 基础设施上提供几乎等同于 Heroku 的开发体验（git push 部署、一键应用）。相同算力下账单通常比 Heroku 低 60-80%。

Heroku Postgres

我们改用什么
Binadit 托管云平台。PostgreSQL 或 MySQL 配合 Patroni 实现故障转移，pgBackRest 实现时间点恢复。
工程说明
逻辑复制（logical replication）可实现零停机切换。Heroku Postgres 的备份可以标准 pg_dump 格式下载，并在任意环境中恢复。

Heroku Redis

我们改用什么
Binadit 托管云平台。Redis 或 Valkey，配合 Sentinel 实现故障转移。
工程说明
标准 Redis API；通过 SLAVEOF 或 RDB 传输方式迁移。

Heroku Connect (Salesforce sync)

我们改用什么
Binadit DevOps & Support。集成工作进程运行在您自有的基础设施上，直接与供应商 API 通信。
工程说明
对于保留 Salesforce CRM 的团队，同步层需要重建；对于替换 Salesforce 的团队，这一问题则不复存在。

Add-ons marketplace

我们改用什么
Binadit DevOps & Support。您实际使用的组件，作为您技术栈的一部分进行部署和运维。
工程说明
Heroku 的 add-on 便利性是最大的 DX（开发者体验）损失；直接管理供应商是换取数据主权所需付出的代价。

Pipelines (review apps, CI/CD)

我们改用什么
Binadit DevOps & Support。基于 Kubernetes 为每个分支创建独立的预览环境，由 GitLab CI 负责创建和销毁。
工程说明
Coolify 支持按分支创建预览环境。

Heroku Buildpacks

我们改用什么
Binadit DevOps & Support。使用 Dockerfiles 或 Cloud Native Buildpacks，在 GitLab CI 中构建。
工程说明
大多数 Heroku 应用可通过 Coolify 上的 Cloud Native Buildpacks 原样部署，无需更改。

Logplex / Logging

我们改用什么
Binadit 托管云平台。使用 Loki 进行日志聚合，配合 Grafana 查询，并按数据流设置保留策略。
工程说明
Loki 是标准方案；聚合所有容器的日志。

Heroku CI

我们改用什么
Binadit DevOps & Support。GitLab CI 配合部署在您自有基础设施上的 runners。
工程说明
在自托管的欧盟 runner 上运行 GitLab CI 是达到生产级别的替代方案。

Heroku Private Spaces

我们改用什么
Binadit 私有基础设施。完全隔离的环境、专用硬件、定制化网络架构。
工程说明
所谓的“Private Spaces”概念本质上就是换了个名字的 VPC；标准的欧盟网络架构完全可以胜任。

SSL / domains

我们改用什么
Binadit 托管云平台。cert-manager 配合 Let's Encrypt，自动续期证书。
工程说明
域名转移只是更换注册商；SSL 在所有现代 PaaS 替代方案中都是自动化处理的。

我们如何迁移离开 Heroku (Salesforce)

典型的中端市场迁移分为三个阶段进行。以下数据假设工程团队规模为 6-10 人，应用程序技术栈复杂度中等。

  1. Days 1-3

    PaaS choice + dependency map

    Decide on the EU PaaS (Coolify is our default for Heroku-style DX; Dokku for minimalists; managed offering from Binadit for hands-off teams). Inventory Heroku apps, dynos and add-ons.

  2. Days 4-10

    Database + add-on swap

    Heroku Postgres replicated to EU managed PostgreSQL with logical replication. Each add-on replaced with EU equivalent (one-by-one to control risk). Logging migrated to Loki.

  3. Weeks 2-4

    Application cutover

    Apps redeployed on Coolify with the same buildpacks. DNS cutover with low TTL window. Heroku app archived after a verification period.

5-year TCO on Heroku exits: 60-85% cheaper. Heroku's pricing model (per-dyno, per-add-on, per-database tier) compounds quickly; a self-hosted PaaS on EU infrastructure replaces a typical $500-2000/month Heroku bill for a fraction of that in raw infrastructure, plus our managed fee if you do not want to operate it yourself.

常见问题

查看所有常见问题

Is Heroku's EU region sufficient for GDPR?
Residency only. Heroku's "Common Runtime" EU region runs in AWS Ireland - that is two layers of US-controlled processors (Salesforce as the immediate contracting party, AWS as the underlying infrastructure). The CLOUD Act analysis applies to both. For Schrems II-strict workloads, Heroku EU is not sufficient.
Will we lose the Heroku DX?
Coolify reproduces git-push deploys, one-click app templates, preview environments per PR, automated SSL, environment variables, and per-branch deploys. The DX is genuinely close. The main loss is the add-on marketplace; you swap that for direct vendor relationships, which is more manageable than Heroku marketing suggests.
What about Heroku Connect for Salesforce sync?
If you're keeping Salesforce CRM, Heroku Connect needs to be rebuilt (REST/Bulk API + queue). If you're also moving off Salesforce - which is increasingly common in Schrems II-driven exits - this concern disappears.
Can we use Coolify ourselves or do we need help?
Many teams self-host Coolify successfully on a single VM. For multi-tenant production scenarios - multi-environment, blue-green, secrets management - a managed-partner setup makes sense. We deploy and operate Coolify clusters for clients.
How long does a Heroku exit take?
For a small workload (1-3 apps, 1 Postgres, a few add-ons): 1-2 weeks. For a multi-app enterprise Heroku setup with Private Spaces and Heroku Connect: 6-10 weeks. Heroku's app surface is intentionally simple, which makes the migration mostly a choreography exercise.
What about the newer Heroku-style platforms?
They reproduce the developer experience well, and if that is all you need they are a reasonable landing. Check two things before you commit: which jurisdiction the platform and its database sit under, and what the exit looks like in two years. A platform that builds from your Dockerfile onto infrastructure you could run yourself is a much shorter conversation later than one with a proprietary build and runtime.

规划您的退出 Heroku (Salesforce).

30 分钟范围确定通话。我们将您的技术栈映射到仅欧盟替代方案,估算迁移工作量,并告诉您这是否是正确的选择。

预约通话 对比其他服务商