Cost
A historical idle sample, with arithmetic and explicit limits.
Historical idle measurement
Source: the template's COST.md, cost-summary.json, and raw docs/cost/ exports. The test ran in bounty-test-elk-3 on a Pro workspace from 2026-10-01 21:08:18.971916 UTC to 21:12:18.989018 UTC, a measured 240.017102 seconds.
No producer, SSH, deployment, or Kibana browser traffic ran during the window. Platform probes and background work remained.
| Service | Samples | Mean RAM (GB) | Mean CPU (vCPU) |
|---|---|---|---|
| Elasticsearch | 8 | 1.585055744 | 0.059367437 |
| Logstash | 8 | 0.729494016 | 0.012570813 |
| Kibana | 8 | 0.898765312 | 0.041415975 |
| Total | 3.213315072 | 0.113354225 |
Conditional monthly scenario
At the Railway rates cited in COST.md, checked on 2026-10-01, maintaining those sampled RAM and CPU means gives $34.40/month for RAM and CPU. This is arithmetic from a short idle sample, not a monthly invoice, capacity forecast, or proven minimum.
10 × RAM GB + 20 × vCPU
+ 0.15 × actual occupied volume GB
+ 0.05 × actual public egress GBRates are USD per billing month for RAM and CPU, and per GB for occupied volume storage and public egress as specified by Railway. Consult Railway pricing before budgeting.
What changes the bill
Actual traffic, indexing load, retention, disk occupancy, and public egress change usage. Memory includes native memory and filesystem cache, not just heap. Allocated volume capacity is not occupied storage.
Storage and egress are excluded from the RAM/CPU scenario. Workspace subscription and included usage credits must not be double counted. Free or Trial compatibility and sustained-load capacity have not been validated.
Evidence boundary
No new cost window was measured while building this documentation site. The live showcase is a separate workload and its cost should not be inferred from this idle test. Inspect the template's raw exports and provenance hashes before using the estimate in a budget.