Websites and hosting decision
DigitalOcean App Platform
A small, opinionated PaaS for personal projects or low-scale apps is feasible to build and maintain by a developer, but reproducing DigitalOcean App Platform's scale, owned infrastructure optimizations, and production polish is not practical.
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.
Code DigitalOcean App Platform 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.
- digitalocean/nginxconfig.io★28,281 GitHub starsMIT⚙️ NGINX config generator on steroids 💉↗
- digitalocean/doctl★3,447 GitHub starsApache-2.0The official command line interface for the DigitalOcean API.↗
- digitalocean/godo★1,539 GitHub starslicence unclearDigitalOcean Go API client↗
- digitalocean/go-libvirt★1,098 GitHub starsApache-2.0Package libvirt provides a pure Go interface for interacting with Libvirt. Apache 2.0 Licensed.↗
What a replacement has to do
- Accept Git push → build image (or use Dockerfile) → run container on VM/Kubernetes → provide TLS + domain + load balancing → collect logs/metrics and scale instances.
What it still won’t have
- Managed autoscaling and production-ready scaling policies
- Integrated team/billing/GUI and one-bill experience
- Deep infrastructure optimizations (GPU/AI stack, owned silicon)
- Enterprise support, managed backups, and built-in integrations
What remains hard
- Infrastructure at scale
We own the silicon. Your unit economics improve as you scale.
- Execution quality
One CLI. One API. One bill. Migrate in one line of code, and leave on the same terms.
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 3 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 App Platform PaaS using: Docker, a single Ubuntu Droplet (or small VM), Nginx (reverse proxy), Docker Registry (or Docker Hub), systemd (or docker-compose) for process management, Certbot for TLS, and a small Node/Express dashboard. Features in scope: Git webhook endpoint that triggers a build, build+push container image, pull and run container on the VM, route domains with automatic Let's Encrypt TLS, basic health checks and restart on crash, and collection of container logs to files. Out of scope: multi-node scheduling, advanced autoscaling, integrated billing, managed databases, and GPU/AI inference. Include error handling, retries for builds/pulls, and unit/integration tests for the webhook, build, and deploy steps.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 5 cited sources+3
- 3/3 assessment runs agreed+4
- Hard moats found in the evidence-3
- Evidence score61
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 productDigitalOcean — official product page
- official pricingDigitalOcean pricing
- official docsDigitalOcean docs — products
- open sourcecoollabsio/coolify
- open sourcekubero-dev/kubero
Integrity checks
What held up, and what did not.
