# Lapdev

Official pricing: https://lap.dev/pricing/  
Category: dev-env · Isolation: container

## Pricing regimes (raw)

- **Native product meter; not a general-purpose 4-vCPU/8-GiB VM** (sizes):  [alt]

## Features

Yes: fork/clone, pause/resume, volumes, idle auto-stop, ≥24 h sessions, custom image (Docker or snapshot), HTTPS preview URLs, open internet, private networking, BYOC, open source, live fork (no pause), EU data residency, inbound access rules, shared volumes

No: snapshots, memory snapshots, persistent disk, 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, preinstalled agents, SSH, public IPv4, egress allowlist, static egress IP, self-hosting, SOC 2, HIPAA, SSO, GPU, arm64, Windows, macOS, Python, Node.js, HTTP method/path egress rules, wake on request, live resize, memory fork, MCP server, 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

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

## Caveats

- Customer supplies Kubernetes cluster and pays its provider independently.
- Future GA prices unpublished; zero beta fee is temporary, not permanent list promise.
- Kubernetes pod isolation depends on customer runtime; no default hardware microVM assurance established.
- No provider-neutral total can be calculated without cluster/node/storage/network SKUs and utilization.
- Native billing cannot be reduced to a 4-vCPU/8-GiB price. No matching engine sizes, by design.
- Maintenance signal (2026-09-29): public repo lapce/lapdev last commit 2025-11-24 (lapdev-cli v0.2.0); status.lap.dev serves an expired TLS cert (notAfter 2026-09-22) and a Vercel DEPLOYMENT_NOT_FOUND 404; api.lap.dev (named in docs as required egress target) returns NXDOMAIN. Site, pricing page, docs and app.lap.dev login are live; latest blog post 2026-02-17.
- Licence is open-core: AGPLv3 except the lapdev-enterprise directory (separate Enterprise License); GitHub reports NOASSERTION.

## How this provider charges


As of 2026-09-28. Current public beta is free PLATFORM SOFTWARE, not free cloud compute. HN launch 2024-03-23 item 39801399; old remote-VM pricing is not current Kubernetes product pricing.

## Regimes

| Regime | When it applies | How billed / numbers | Source |
|---|---|---|---|
| Beta platform licence | Native product usage | $0 while public beta; external Kubernetes resources excluded. | [Primary pricing](https://lap.dev/pricing/) |
| Post-GA platform fee | Native product usage | Unknown; planned active-environment subscription plus own infrastructure. | [Primary pricing](https://lap.dev/pricing/) |
| Public beta | Account plan | $0/month; No platform fee during beta; own Kubernetes compute/network/storage billed externally; unlimited developers/catalogs advertised. | [Primary pricing](https://lap.dev/pricing/) |
| GA future subscription | Account plan | Unpublished / sales; Planned subscription by active environments; not yet priced. | [Primary pricing](https://lap.dev/pricing/) |

## Gotchas

- Customer supplies Kubernetes cluster and pays its provider independently.
- Future GA prices unpublished; zero beta fee is temporary, not permanent list promise.
- Kubernetes pod isolation depends on customer runtime; no default hardware microVM assurance established.
- No provider-neutral total can be calculated without cluster/node/storage/network SKUs and utilization.

## Required worked example

4 vCPU / 8 GiB, 50 concurrent × 8 h/day × 22 days = **8,800 instance-hours**, 30% CPU, 50 GiB retained snapshots and 100 GiB egress.

**Unknown total, not $0.** A platform licence contributes $0 during beta, but the customer must provision enough Kubernetes CPU/RAM for 50 × 4 vCPU/8 GiB if all are reserved, and pay running nodes, 50 GiB retained state and 100 GiB transfer. Active 30% CPU does not automatically make node allocation 30% billable.

## Feature evidence

- https://docs.lap.dev/llms-full.txt
- https://github.com/lapce/lapdev