Websites and hosting decision
Render
Keep paying—Render's managed autoscaling, compliance, global infra, and enterprise features are costly to replicate; a small team can cobble together core deploy+host flows but will lose major platform capabilities and face significant ongoing ops burden.
Visit website↗Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Render alternatives, with the arithmetic →
Code Render publishes itself
Not a way out of the subscription - these are the vendor’s own repositories. Worth a look for how they build, and for anything you would have to integrate with.
What a replacement has to do
- Provide git-driven deploys, run containers or language runtimes, and host a managed Postgres-like service.
What it still won’t have
- Autoscaling that handles 100x traffic bursts
- Managed compliance and enterprise controls (SOC2/HIPAA/ISO)
- Full-stack preview environments for pull requests
- Built-in DDoS mitigation and platform-level protections
- Integrated workspace/team controls, audit logs, and support SLAs
What remains hard
- Infrastructure at scale
Intuitive infrastructure to scale any app or agent from your first user to your billionth.
- Brand trust
Trusted by over 6 million builders
- Compliance and regulation
Managed compliance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 2 seats.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal self-hosted PaaS that supports git-driven deploys and a managed Postgres instance using Ubuntu VMs (DigitalOcean), Docker, Nginx, systemd, and PostgreSQL. In scope: webhook receiver to trigger builds, a build step that produces Docker images, registry storage (local or Docker Hub), container runtime orchestration using docker-compose or a single-node Nomad, TLS via Let's Encrypt, basic reverse proxy with health checks and zero-downtime deploy (blue/green), a Postgres service with automated daily backups and restore, a small web UI or CLI to view deploy logs and trigger rollbacks, and monitoring via Prometheus + Grafana. Out of scope: automatic multi-region autoscaling, enterprise SSO/SAML, DDoS mitigation, and a full multi-tenant control plane. Include error handling, retry logic for deploys, CI tests for build/deploy flows, and end-to-end tests for deploy + DB connectivity.
How we checked
How the score was reached
- Pay verdict base20
- An open-source build was found+5
- 5 cited sources+3
- Price verified on pricing page+3
- Hard moats found in the evidence-6
- Evidence score25
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 5
Every page the run actually retrieved.
- official productRender product page
- official pricingRender pricing
- official docsRender docs
- open sourceappwrite/appwrite
- open sourcesandstorm-io/sandstorm
Integrity checks
What held up, and what did not.
