Hobby
$0/ mo
For side projects and prototypes — enough headroom to actually ship something.
- 100k requests / mo
- 1 edge region
- 7-day log retention
- Community support
( core primitives )
One 18MB binary — install with curl, no runtime, no dependency tree to audit.
Requests route through 34 edge regions with sub-12ms added latency, p99.
Every request emits structured JSON — pipe straight into your existing stack.
Atomic rollouts with automatic rollback the moment error rates spike.
( the workflow )
Write your API surface in a single latch.yaml — routes, auth, rate limits, and retries all version-controlled next to your service.
`latch deploy` builds, ships, and health-checks a new revision — usually inside 4 seconds, no dashboard required.
Full distributed traces down to the database query, searchable by status code, latency, or customer ID.
Anomaly detection on latency and error budgets pages you in Slack or PagerDuty before SLAs break.
( status )
( live dashboard )
requests per second
▲ +21.4%cache hit rate
edge cache, last 24h
active api keys
▲ +4.7%
p99 latency (ms)
▼ -12mssla uptime
trailing 30 days
error rate
▼ -0.01%
( pricing )
Hobby
$0/ mo
For side projects and prototypes — enough headroom to actually ship something.
Team
$49/ mo
The default for production APIs — usage-based beyond the included quota.
Enterprise
Custom
Dedicated infrastructure and SLAs for teams running APIs at serious scale.
( faq )
No — Latch sits in front of your existing service as a reverse proxy. Point your DNS at us, add a latch.yaml, and routing, auth, and observability work immediately.
( get started )
Install the CLI, run `latch init`, and push your first route to production before your coffee finishes brewing.