# Heroku

Official pricing: https://www.heroku.com/pricing/  
Category: paas · Isolation: container

## Pricing regimes (raw)

- **Cedar Common Runtime dynos (Basic/Standard shared; Performance dedicated)** (sizes): Basic ? vCPU/0.5 GiB $0.00972/h; Standard-1X ? vCPU/0.5 GiB $0.03472/h; Standard-2X ? vCPU/1 GiB $0.06944/h; Performance-M ? vCPU/2.5 GiB $0.34722/h; Performance-L ? vCPU/14 GiB $0.69444/h; Performance-L-RAM ? vCPU/30 GiB $0.69444/h [alt]
- **Eco dynos: $5 flat for a 1,000 dyno-hour pool (personal apps only)** (pool) [alt]
- **Cedar Private Space dynos (dedicated; requires a Private Space)** (sizes): Private-S ? vCPU/1 GiB $0.17361/h; Private-M ? vCPU/2.5 GiB $0.34722/h; Private-L ? vCPU/14 GiB $0.69444/h; Private-L-RAM ? vCPU/30 GiB $0.69444/h; Private-XL ? vCPU/62 GiB $1.04167/h; Private-2XL ? vCPU/126 GiB $2.08333/h [alt]
- **Cedar Shield Private Space dynos (HIPAA/PCI)** (sizes): Shield-S ? vCPU/1 GiB $0.20833/h; Shield-M ? vCPU/2.5 GiB $0.41667/h; Shield-L ? vCPU/14 GiB $0.83333/h; Shield-L-RAM ? vCPU/30 GiB $0.83333/h; Shield-XL ? vCPU/62 GiB $1.25/h; Shield-2XL ? vCPU/126 GiB $2.5/h [alt]
- **Fir (next-gen, Kubernetes) dynos; requires a Fir Private Space** (sizes): dyno-1c-0.5gb (Classic) 1 vCPU/0.5 GiB $0.03472/h; dyno-2c-1gb (Classic) 2 vCPU/1 GiB $0.06944/h; dyno-1c-4gb (General Purpose) 1 vCPU/4 GiB $0.11111/h; dyno-2c-8gb (General Purpose) 2 vCPU/8 GiB $0.22222/h; dyno-4c-16gb (General Purpose) 4 vCPU/16 GiB $0.44444/h; dyno-8c-32gb (General Purpose) 8 vCPU/32 GiB $0.88889/h [alt]

## Features

Yes: idle auto-stop, ≥24 h sessions, custom image (Docker or snapshot), your own Docker/OCI image, SSH, HTTPS preview URLs, custom domains, static egress IP, private networking, SOC 2, HIPAA, SSO, arm64, Python, Node.js, Go, Java, wake on request, webhooks, EU data residency, MCP server, inbound access rules

No: snapshots, memory snapshots, fork/clone, pause/resume, persistent disk, volumes, start from your own snapshot, full VM (own kernel), Docker inside, nested virtualization, root, browser, desktop GUI, computer-use API, browser + desktop control, anti-bot stealth, CAPTCHA solving, residential IPs, preinstalled agents, public IPv4, raw TCP inbound, egress allowlist, self-hosting, BYOC, open source, GPU, Windows, macOS, HTTP method/path egress rules, live resize, live fork (no pause), memory fork, automatic snapshots, snapshots on demand, agent harness API, hosted agent API (their own agent), gVisor or VM (no shared kernel), firewall inside (nftables), secret proxy, secret proxy for any API, extra volumes, shared volumes

Unknown: everything else. Evidence (source + quote) per feature: https://battleships.dev/data/providers/heroku.json → feature_evidence

## Caveats

- Cedar CPU units are relative 1x/12x/50x, not vCPUs; do not equate them. Fir Compute 4CPU/8GB $300/month needs Private Space; public table alone does not yield all-in total. Eco $5 is 1000-hour shared pool, not per-dyno always-on rate. Disk ephemeral, paid data separate.
- Null values mean unknown, not free/unlimited. No model-token cost, tax or unverified ancillary charge included.
- Native browser/device/task/credit prices with unknown CPU/RAM are deliberately non-priceable. Check regime before interpreting any partial resource estimate.
- Product status: since 2026-02-06 Heroku is in a 'sustaining engineering model ... rather than introducing new features' (Salesforce). No pricing change for card-paying customers; Enterprise contracts closed to new customers. Fir roadmap items (GPU dynos, Fir autoscaling/Shield/Common Runtime) may not ship.
- Start rate: Platform API token bucket of 4,500 calls, refilled ~75/minute per account; each dyno scale / one-off run is an API call, so bursty 'one dyno per task' use tops out around 75 starts/min per account (plus 50 concurrent Standard one-offs / 5 Performance one-offs per app).

## How this provider charges


YC: Winter 2008; directory status **Acquired**. Research scope: public-product-researched. Source: https://www.ycombinator.com/companies/heroku

Cedar and Fir dynos

## Regime table

| Regime | When it applies | How billed | Numbers | Source |
|---|---|---|---|---|
| Native product; see regime notes | Incomplete or non-resource economics: rates remain null, never interpreted as free. | resource; CPU alloc, memory alloc | Unknown or native-unit billing; see facts below | http://heroku.com |
| Current applicable tariff unverified | Plan limits apply | Monthly fee; credits only as stated | fee=None; included usage=$None; concurrent=None; max session h=None | http://heroku.com |
| Retained disk / GiB-month | Lifecycle/scope must be checked | Native add-on | unverified, not $0 | http://heroku.com |
| Snapshots / GiB-month | Lifecycle/scope must be checked | Native add-on | unverified, not $0 | http://heroku.com |
| Egress / GiB | Lifecycle/scope must be checked | Native add-on | unverified, not $0 | http://heroku.com |
| IPv4 / month | Lifecycle/scope must be checked | Native add-on | unverified, not $0 | http://heroku.com |

## Verified billing facts and gotchas

1. Cedar CPU units are relative 1x/12x/50x, not vCPUs; do not equate them. Fir Compute 4CPU/8GB $300/month needs Private Space; public table alone does not yield all-in total. Eco $5 is 1000-hour shared pool, not per-dyno always-on rate. Disk ephemeral, paid data separate.

## Worked example

Requested: 4 vCPU/8 GiB, 50 simultaneous × 8 h/day × 22 days = **8,800 instance-hours**, 30% CPU; 50 GiB snapshots and 100 GiB egress. A month is 730 hours only when explicitly used in rate conversion.

**Total: unknown.** This product does not publish a verified complete 4-vCPU/8-GiB tariff and/or the service bills a different unit. Fifty concurrent instances and eight-hour sessions are not automatically supported. Neither 30% utilization nor retained snapshots can be converted into free resources. Use the native plan terms above and request the missing CPU/RAM, retention, egress and concurrency quote.

## Sources and coverage

- https://www.ycombinator.com/companies/heroku
- https://www.heroku.com/
- https://www.heroku.com/pricing/
- https://devcenter.heroku.com
- https://heroku.com/llms.txt

Page captures and documentation indexes/bundles are in `raw/`; provider JSON lists the evidence paths. HN query results were captured separately as `<id>--hn.txt`; they are discovery leads, not current tariff authority. Downloaded docs do not imply every feature was verified; unsupported assertions remain null.