Cost

Measured template windowCopy Anchor Link

The template's recorded healthy window runs from 2026-10-01 23:49:50.131926 UTC to 23:53:19.548163 UTC. The calculation sums the arithmetic mean of equally spaced provider samples across fourteen runtime services, excluding the sample application and the provider's pre-window boundary bucket.

Repeating that window for a thirty-day month gives $96.34 in compute. This is an extrapolation of a short observation, not an invoice, capacity forecast or guarantee under your traffic.

Download the original measurement and calculation.

CalculationCopy Anchor Link

The recorded calculation uses Railway's published per-minute rates:

43,200 minutes × (9.31265506742857 GB × $0.000231/GB-minute
               + 0.17020029523809524 vCPU × $0.000463/vCPU-minute)
= $96.33712567411749, rounded to $96.34

A thirty-day month contains 43,200 minutes. Rates are sourced from Railway pricing; verify them again before budgeting. The formula and unrounded inputs are preserved in the measurement file.

Excluded costsCopy Anchor Link

The compute estimate excludes volume storage, bucket storage, service egress, workload growth, plan charges and included credit. Do not treat it as your total monthly bill. Native S3 uploads incur service egress.

Configure Railway usage alerts, project quotas, inbound filters and SDK sampling based on your measured workload. Track consumer lag and storage growth as well as memory and CPU.

Demo estimate is separateCopy Anchor Link

The later read-only synthetic demo measurement is a different workload. Its window, 2026-10-02 03:49:30 UTC to 03:53:52.463489 UTC, produced a recorded $102.98 per thirty-day month, including measured volume storage and a conservative bucket allocation, plus public service network egress.

That estimate is also an extrapolation. Do not substitute it for the template compute-only figure or add the figures together. See the demo calculation and demo cost notes.