Websites and hosting decision
Railway
A small team can implement a useful subset (git deploy, container hosting, TLS, basic DB, logs) with open-source components, but replicating Railway's global scale, high-throughput private networking, integrated enterprise features, and polished multi-environment UX is not practical for a single developer or small project.
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 Railway 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.
- railwayapp/nixpacks★3,544 GitHub starsMITApp source + Nix packages + Docker = Image↗
- railwayapp/railpack★1,139 GitHub starsMITZero-config application builder that automatically analyzes and turns your code into an image↗
- railwayapp/cli★585 GitHub starsMITRailway CLI↗
- railwayapp/templates★382 GitHub starsMITRailway starters↗
What a replacement has to do
- Provide a minimal hosting service that accepts a Git repo or Docker image, builds the app, runs it in containers, exposes a public domain with TLS, stores attachments/DBs, and shows basic logs/metrics.
What it still won’t have
- High-performance global private networking and 100 Gbps internal transfer
- Integrated multi-region autoscaling and large replica/VM limits
- Built-in PR preview orchestration and unlimited ephemeral environments at scale
- Managed enterprise features (SSO, audit log retention, HIPAA BAA) and dedicated VMs
- Tight integrated UI/console with 100+ API GraphQL surface
What remains hard
- Infrastructure at scale
100 Gbps internal networking without VPC configuration.
- Brand trust
Join 2M+ developers building with Railway
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 6 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 using GitHub Actions, Docker, and a single k3s cluster on a small cloud VM pool (e.g., 3 x t3.small). Implement: 1) Git-based build pipeline that builds and pushes Docker images; 2) a controller that maps repos to services and deploys containers with environment variables; 3) an ingress layer (Caddy or nginx) that issues Let's Encrypt TLS and routes custom domains; 4) a managed Postgres service with automated daily backups; 5) a lightweight web UI (React + Express) to create projects, view logs, and start PR preview environments. Out of scope: multi-region/global networking, enterprise SSO/audit retention, hyperscale replica counts, and proprietary agent functionality. Include error handling, retries for transient failures, health checks, and basic unit/integration tests for the build pipeline, deploy controller, and ingress routing.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 4 cited sources+3
- Price verified on pricing page+3
- Hard moats found in the evidence-3
- Evidence score60
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 · 4
Every page the run actually retrieved.
- official productRailway — product
- official pricingRailway Pricing
- official docsRailway Features
- open sourcezeitwork/zeitwork
Integrity checks
What held up, and what did not.
