# Wasmer

Official pricing: https://wasmer.io/pricing  
Category: paas · Isolation: isolate

## Pricing regimes (raw)

- **WebAssembly Edge** (resource): $0.1/vCPU-h, $0.01/GiB-h [alt]

## Features

Yes: pause/resume, persistent disk, volumes, idle auto-stop, ≥24 h sessions, SSH, public IPv4, HTTPS preview URLs, custom domains, raw TCP inbound, open internet, self-hosting, open source, Python, Node.js, wake on request, EU data residency, MCP server, gVisor or VM (no shared kernel), extra volumes, shared volumes

No: snapshots, memory snapshots, fork/clone, start from your own snapshot, your own Docker/OCI image, full VM (own kernel), Docker inside, nested virtualization, browser, desktop GUI, computer-use API, browser + desktop control, anti-bot stealth, CAPTCHA solving, residential IPs, preinstalled agents, egress allowlist, static egress IP, BYOC, GPU, arm64, 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), inbound access rules, firewall inside (nftables), secret proxy, secret proxy for any API

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

## Caveats

- Wasmer WebAssembly execution is not a full Linux VM; card isolation isolate is approximate because engine lacks wasm enum. Pricing uses active CPU plus provisioned memory.
- Pro includes separate 6 active CPU-hours, 400 GB-hours memory, 150 GB bandwidth, 1 GB volume and package storage, 1M requests and 1000 build-minutes. These category-specific allowances cannot be collapsed into fully fungible credits.
- Pro $10/mo; extra seats $5, app beyond 100 $0.25, requests $0.50/M, builds $0.005/min, volumes/packages $0.05/GB-month; databases and backups 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.

## How this provider charges


YC: Summer 2019; directory status **Active**. Research scope: public-product-researched. Source: https://www.ycombinator.com/companies/wasmer

The Operating System for Edge Computing

## Regime table

| Regime | When it applies | How billed | Numbers | Source |
|---|---|---|---|---|
| WebAssembly Edge | alt | resource; CPU active, memory alloc | $0.1/vCPU-h + $0.01/GiB-h; multiplier 1 | https://wasmer.io/pricing |
| Pro | Plan limits apply | Monthly fee; credits only as stated | fee=10; included usage=$0; concurrent=None; max session h=None | https://wasmer.io/pricing |
| Enterprise | Plan limits apply | Monthly fee; credits only as stated | fee=None; included usage=$None; concurrent=None; max session h=None | https://wasmer.io/pricing |
| Retained disk / GiB-month | Lifecycle/scope must be checked | Native add-on | $0.05 | https://wasmer.io/pricing |
| Snapshots / GiB-month | Lifecycle/scope must be checked | Native add-on | unverified, not $0 | https://wasmer.io/pricing |
| Egress / GiB | Lifecycle/scope must be checked | Native add-on | $0.1 | https://wasmer.io/pricing |
| IPv4 / month | Lifecycle/scope must be checked | Native add-on | unverified, not $0 | https://wasmer.io/pricing |

## Verified billing facts and gotchas

1. Wasmer WebAssembly execution is not a full Linux VM; card isolation isolate is approximate because engine lacks wasm enum. Pricing uses active CPU plus provisioned memory.
2. Pro includes separate 6 active CPU-hours, 400 GB-hours memory, 150 GB bandwidth, 1 GB volume and package storage, 1M requests and 1000 build-minutes. These category-specific allowances cannot be collapsed into fully fungible credits.
3. Pro $10/mo; extra seats $5, app beyond 100 $0.25, requests $0.50/M, builds $0.005/min, volumes/packages $0.05/GB-month; databases and backups 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.

30% active CPU and full provisioned memory: 8,800×(4×0.3×$0.10+8×$0.01)=$1,760. Subtract separate 6×$0.10 +400×$0.01 allowances, add $10 Pro = $1,765.40 before storage/requests/builds. 100 GB egress fits 150 GB. A 4/8 interactive machine is not assured; this is resource arithmetic, not a feasibility guarantee.

## Sources and coverage

- https://www.ycombinator.com/companies/wasmer
- https://wasmer.io/pricing
- https://wasmer.io/
- https://wasmer.io/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.