A Railway alternative when you want one machine and one number
Railway is good at turning a repository into a running service. It supports private networking, volumes, replicas, preview environments and a broad range of workloads. If per-second resource billing fits how you operate, it can be the right choice.
Lathe is for a narrower case: a solo builder or small team whose app, database and auth fit on one machine and who would rather choose one monthly number than meter every running service.
Prices below were checked against Railway's official pricing on September 22, 2026.
The billing model is the main difference
Railway's Hobby plan is $5 a month with $5 of usage included. Pro is $20 a month with $20 included. Running services are metered per second. Railway currently lists memory at about $10 per GB per month, CPU at about $20 per vCPU per month, volumes at $0.15 per GB per month and service egress at $0.05 per GB.
That model is flexible: stopped services stop costing CPU and memory, and small workloads can stay near the plan minimum. It also means the final bill depends on the resources each service holds and uses.
Lathe plans are $15, $29, $49 and $89 a month. The price is for one machine. Apps, Postgres, Auth, Redis, CouchDB and NATS can share it, with storage, backups and 20 TB of outbound traffic included. There is no extra line for a second service, a database connection, an auth user or a request.
| Question | Railway | Lathe |
|---|---|---|
| Monthly model | Plan minimum plus metered resources | One fixed machine price |
| App and data layout | Separate services joined by private networking | App and engines on one machine |
| Scaling | Replicas and high per-service ceilings | Upsize one machine; no horizontal scaling |
| Storage | Volumes billed per GB | Machine disk included |
| Egress | $0.05 per GB for services | 20 TB included |
| Operations | Managed service platform | Managed machine with a narrower product |
When Railway is the better fit
Choose Railway when you want replicas, ephemeral environments, services that scale or sleep independently, or workloads too large or too varied for one machine. Its free and low-minimum plans are also better for experiments that use almost nothing.
Railway is a platform for composing services. Lathe deliberately is not.
When one machine is simpler
A small app often needs one web process, Postgres, authentication and perhaps Redis. On Railway those are distinct resources, which is useful when each must scale alone. On Lathe they share a capacity budget and one failure boundary, which is simpler when the whole product is small enough to fit.
The trade is explicit. One machine means no high availability, no automatic failover, no horizontal scaling and no point-in-time recovery. Backups run daily and seven are kept. Support comes from two founders by email.
Use a real month, not a slogan
Railway publishes clear rates and usage controls. Take the CPU, memory, volume and egress from an actual month and calculate that total. Compare it with the Lathe machine size the same workload needs.
If independently scalable services and replicas are worth the metering, use Railway. If the product fits on one machine and the goal is one app, one database, one auth service and one bill, Lathe is the alternative.
Lathe has a 14-day Mini trial with no card. Test a staging workload, not an important production system, and keep the option that matches the architecture you actually need.