Alternativa solo UE a Render.
Render positioned itself as the modern Heroku — same developer experience, more reasonable pricing, faster cold starts. Render Inc. is a US Delaware corporation; the Frankfurt region is EU-located but US-controlled, with the underlying infrastructure ultimately on AWS. The CLOUD Act analysis is identical to Heroku and to direct AWS usage. For EU teams that picked Render specifically for its DX, the sovereign alternative is Coolify or a managed PaaS on Hetzner / OVH — same DX, EU jurisdiction, dramatically cheaper at scale.
"Regione UE" non è sovranità. Quattro domande decidono.
La residenza dei dati indica dove sono i bit. La sovranità indica quale sistema giuridico può imporre l'accesso. La risposta deve reggere su tutte e quattro — altrimenti lo stack non è sovrano.
Dove sono fisicamente archiviati i dati?
Non "nel cloud" — quale datacenter, in quale paese, sotto quale giurisdizione.
Chi altro è nel suo percorso dei dati?
Ogni fornitore che tocca i dati: il CDN, il relay e-mail, il tracker degli errori, la pipeline di analytics.
Quali leggi possono imporre la divulgazione?
Un fornitore con sede negli USA è soggetto al FISA 702 e al CLOUD Act — anche quando i dati sono a Francoforte.
Chi detiene effettivamente le chiavi di cifratura?
Se il provider cloud detiene sia i dati che le chiavi, può leggerli — indipendentemente dal DPA.
Fallisce su giurisdizione e custodia delle chiavi.
Bit nell'UE, casa madre statunitense, sub-responsabili americani nel percorso predefinito, chiavi gestite dal fornitore.
Passa su tutte e quattro.
Ospitato in UE su infrastruttura con sede europea. Zero sub-responsabili statunitensi nel percorso predefinito. Chiavi del cliente o di KMS europeo. Elencati per nome nel suo DPA Articolo 28.
Perché i team se ne vanno Render
Render exits are usually triggered by a customer audit (SaaS/B2B) flagging the AWS-Frankfurt-via-Render data path, or by cost reviews where Render's usage-based pricing crosses into "we should self-host" territory. Render's product is well-engineered, and the migration is mostly mechanical — Render uses standard buildpacks and Docker, which port directly to Coolify or any EU PaaS.
Render servizi e i loro equivalenti solo UE
Una migrazione non è "scambiare una scatola con un'altra". La mappatura sottostante è ciò che eseguiamo per i clienti che lasciano Render per motivi Schrems II — piena giurisdizione UE, nessuna casa madre USA nel percorso dei dati.
| Render servizio | Alternativa solo UE | Nota di ingegneria |
|---|---|---|
| Web Services | Coolify on Hetzner, Scaleway Serverless Containers, Dokku | Coolify is the closest DX equivalent; Scaleway is the most "Render-like" managed option in the EU sovereign space. |
| Background Workers | Coolify worker services, Kubernetes deployments on EU K8s, systemd services on bare VMs | Render workers are essentially long-running containers; the migration is a redeploy. |
| Cron Jobs | Coolify scheduled services, K8s CronJobs, systemd timers | Standard cron scheduling on all EU options. |
| Render Postgres | OVH Managed PostgreSQL, Aiven, self-managed PostgreSQL | Logical replication for zero-downtime cutover. |
| Render Redis | OVH Managed Redis, Aiven Redis, self-managed Redis | Standard Redis migration patterns. |
| Static Sites | Bunny.net + EU object storage, Coolify static apps, GitLab Pages EU | Bunny pull zone in front of EU storage is the cheapest production-grade pattern. |
| Private Services | EU private networks (Hetzner, OVH vRack), Coolify internal networks | Service-to-service communication on a private network is standard. |
| Disks (persistent) | Hetzner Volumes, OVH Block Storage, Scaleway Block Storage | Standard NVMe-backed volumes everywhere. |
| Preview Environments | Coolify preview deployments per PR, GitLab Review Apps | Coolify has built-in PR-based preview environments. |
| Render Blueprints (IaC) | Docker Compose, Kubernetes manifests, Coolify config | Render Blueprints are essentially declarative service configs; equivalent on any EU PaaS. |
Come migriamo da Render
Una tipica migrazione di mid-market si svolge in tre fasi. I numeri qui sotto assumono un team di ingegneria di 6-10 persone e uno stack applicativo moderatamente complesso.
Inventory
List Render services, databases, disks, environment variables and Blueprints. Render setups are typically small and clean — inventory takes less than a day.
Soft swap
Database replicas pre-staged on EU managed PostgreSQL. Object storage / static site files mirrored. CI/CD updated to deploy to both targets in parallel.
Cutover
Coolify (or chosen PaaS) configured with same env vars and build commands. Database cut over via logical replication. DNS shift to new endpoints. Render account decommissioned after verification.
5-year TCO on Render exits: 50–75% cheaper. Render's usage-based pricing scales linearly; self-hosted Coolify on a single Hetzner CCX21 (€10/month) replaces what is typically $200-500/month on Render for small-to-medium workloads.
Domande frequenti
Render has a Frankfurt region — does that solve GDPR?
Residency yes, sovereignty no. Render Inc. is US-headquartered, the underlying compute is AWS Frankfurt (also US-jurisdictional), and the CLOUD Act applies to both layers. For Schrems II–strict workloads, the Frankfurt region is not sufficient.
Can Coolify really replace Render's UX?
For 90% of Render workloads, yes. Coolify supports git-push deploys, automatic SSL, preview environments per PR, environment variable management, secrets, and webhook deploys. The areas where Render is still ahead: integrated metrics dashboards (Coolify's are more basic) and zero-config TLS (parity here).
What about Fly.io as an alternative?
Fly.io is also US-headquartered (Delaware), so it doesn't solve sovereignty — see /alternatives/fly-io for that specific migration. For sovereign PaaS, the EU options are Coolify, Dokku, Caprover, or a managed equivalent.
How long does a Render migration take?
For a typical workload (3–10 services, 1–2 databases, static sites): 1–3 weeks elapsed. With managed-partner support: 1 week. Render's small product surface keeps the migration clean.
Can we run a hybrid during transition?
Yes — common pattern. New deployments go to the EU PaaS; existing services stay on Render until each is verified. Database can be replicated read-only to the EU side during the transition period.
What if we want fully managed (not self-hosted)?
Scaleway Serverless Containers is the closest "managed PaaS" in the EU sovereign space. For teams that want a Render-like experience without operating Coolify, a managed-partner relationship — where someone else operates the PaaS for you — is the third option.
Pianifica la tua uscita da Render.
Chiamata di scoping di 30 minuti. Mappiamo il tuo stack rispetto alle alternative solo UE, stimiamo lo sforzo di migrazione e ti diciamo se è la scelta giusta.