Websites and hosting decision
Static.run
A competent developer can build a useful self-hosted replacement in about a week using object storage, a CDN, and ACME; no durable moats are evident in the product pages so keeping costs low by self-hosting is realistic.
Visit website↗Built by Musharof, who ships 3 products in this index
Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off32 h to build
$20/mo3 h/mo upkeep
No published price to break even against.
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 Static.run alternatives, with the arithmetic →
What a replacement has to do
- Upload static files, serve them from object storage behind a CDN with automated TLS, allow custom domain DNS verification, and provide a minimal web UI to manage projects and edit files.
What it still won’t have
- Polish and integrations of a managed product (dashboard UX, account recovery flows, community support)
- Guaranteed unlimited traffic and hosting SLA offered by the vendor
- Built-in user management, social logins, and any proprietary operational hardening
- One-click hosted scaling, managed backups, and hosted analytics
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Static.run does not publish a price we could read, so there is nothing to compare against. What building costs is below.
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-hostable static-site hosting service using Node.js (Express) for the API, AWS S3-compatible object storage for files, CloudFront (or Cloudflare) for CDN, and React for the web UI. Core features in scope: project creation, file upload and listing, inline code editor for HTML/CSS/JS files, deploy-to-storage flow, CDN invalidation, custom-domain DNS verification, automated TLS issuance/renewal via ACME, and basic access control (per-project public/private switch). Out of scope: multi-tenant billing, analytics, server-side dynamic rendering, and enterprise SLAs. Include error handling, logging, unit tests for API endpoints, and README deployment instructions (Terraform or CloudFormation templates) to provision S3+CDN+DNS.
How we checked
How the score was reached
- Build verdict base78
- An open-source build was found+5
- 5 cited sources+3
- Evidence score86
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 productStatic.run — Home
- official pricingStatic.run — Pricing
- official docsStatic.run — Docs
- open sourcecoollabsio/coolify
- open sourceglitternetwork/pinme
Integrity checks
What held up, and what did not.
