Sensitivity model
PaaS pricing calculator
The relevant PaaS premium is not the difference between two compute prices. Compare complete infrastructure bills first; only then model team cost separately with your own inputs.
Answer for the inputs set below
No managed platform in this dataset matches this workload, so there is no infrastructure total to show.
Set to: 2 vCPU · 4 GB RAM · no persistent disk · 100 GB egress · no managed database
PaaS cost model
Calculate the infrastructure bill
Rank every PaaS plan using the same workload, database, storage, and egress inputs. Unknown prices stay visible and cannot win. Team cost is optional context and never ranks.
These controls are switched off, not merely dimmed. Nothing on this page can recompute without JavaScript, so every slider and menu above is disabled in the HTML and cannot be moved by a pointer or by a keyboard. The ranking, the receipt and the sources below are the complete result for 2 vCPU · 4 GB RAM · no persistent disk · 100 GB egress · no managed database, already in this page. A copied calculator link cannot be restored here either.
No managed platform in this dataset matches the size you asked for, so the table below is empty. Lower the vCPU or memory, or set the managed database back to none, and the ranking returns.
| Rank | Provider | Compute | Database | Storage | Egress | Infrastructure total |
|---|
Receipt
- Compute
- Database
- Storage
- Egress
- Total
There is no receipt to show, because no provider carries a complete infrastructure total at these inputs. A receipt here always adds up to figures a vendor publishes, so an empty ranking produces an empty receipt rather than lines of "Unknown" pretending to be one.
Every ranked charge uses the cited price for that provider and plan. Selecting a managed database marks the total Unknown until a provider-specific verified database price is linked; unpublished storage or egress rates also cannot win.
Working comparison
Compare the options that fit this decision
| Component | Railway example | Render example | Decision use |
|---|---|---|---|
| 2 vCPU and 4 GB compute | $85/mo derived | $292/mo at Workflow Pro | Do not compare unlike runtime products |
| Egress | $0.05/GB | Unknown in this dated example | Unknown must stay visible |
| Team-cost context | Off by default | Off by default | User supplied and shown separately; never ranks |
Decision test
What changes the answer
- 01Only complete infrastructure totals are ranked. An unknown storage or egress rate stays visible and cannot win.
- 02Price the steady-state compute floor before credits.
- 03Add database and egress using the workload, not the provider's smallest example.
- 04Value only operations work the platform actually removes.
- 05Run the model again at the expected 12-month workload.
Shareable result receipt
Every line below is computed from the controls above, so the address bar, this receipt and the ranking always state one result.
No managed platform in this dataset matches this workload, so there is no infrastructure total to show.
Formula
Infrastructure premium = managed infrastructure bill − self-managed infrastructure bill; optional crossover hours = infrastructure premium ÷ user-supplied hourly team cost
Assumptions
- Set to: 2 vCPU · 4 GB RAM · no persistent disk · 100 GB egress · no managed database
- 730 runtime hours
- Published list pricing
- No paid support plan
Explicit unknowns
- Render workflow egress in this dated example
Sources and freshness
- Railway pricing retrieved 2026-07-25
- Render workflow limits and pricing retrieved 2026-07-25