# Shuttle

Official pricing: https://www.shuttle.dev  
Category: paas · Isolation: not published · DISCONTINUED

## Pricing regimes (raw)


## Features

Yes: ≥24 h sessions

No: volumes, automatic snapshots, snapshots on demand, agent harness API, inbound access rules, 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/shuttle.json → feature_evidence

## Caveats

- Discontinued or closed to new customers, confirmed on the live site 2026-09-29. Homepage https://www.shuttle.dev/ still renders the old 'Build Backends. Fast.' marketing page with no shutdown banner, which is why the earlier pass saw it as live; the shutdown notice is only in the docs (docs.shuttle.dev/docs/shuttle-shutdown). GitHub API: shuttle-hq/shuttle archived=true, pushed
- DISCONTINUED: Shuttle announced it is ceasing operations; Community tier data deleted from beginning of 2026, Pro projects stopped Jan 16 2026, Growth customers migrated individually. GitHub repo shuttle-hq/shuttle archived (last push 2026-01-09). Marketing homepage and docs remain online as a static shell; console.shuttle.dev redirects to the homepage; /pricing 404.
- 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.

## How this provider charges


YC: Summer 2020; directory status **Inactive**. Research scope: public-product-researched. Source: https://www.ycombinator.com/companies/shuttle

Rust app hosting

## 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 | https://www.shuttle.dev |
| Current applicable tariff unverified | Plan limits apply | Monthly fee; credits only as stated | fee=None; included usage=$None; concurrent=None; max session h=None | https://www.shuttle.dev |
| Retained disk / GiB-month | Lifecycle/scope must be checked | Native add-on | unverified, not $0 | https://www.shuttle.dev |
| Snapshots / GiB-month | Lifecycle/scope must be checked | Native add-on | unverified, not $0 | https://www.shuttle.dev |
| Egress / GiB | Lifecycle/scope must be checked | Native add-on | unverified, not $0 | https://www.shuttle.dev |
| IPv4 / month | Lifecycle/scope must be checked | Native add-on | unverified, not $0 | https://www.shuttle.dev |

## Verified billing facts and gotchas

1. YC Inactive but public home/docs remain online, so not automatically dead. /pricing 404. Need current commercial availability and pricing confirmation before ranking. Serverless Rust deployment, not a full Linux workspace.

## 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/shuttle
- https://www.shuttle.dev/
- https://docs.shuttle.dev/welcome/introduction
- https://www.shuttle.dev/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.