Billing and Limits

Watasu is meant to feel simple, but real apps run into real limits. This page is the map.

What you pay for

	What it is
App compute	Pod count × pod size × time. Bigger pods and more replicas cost more.
Add-ons	Each add-on plan has its own price. Higher tiers add capacity, durability, replication, and scheduled backups.
Bandwidth	Generous included egress on most plans; heavy outbound traffic can cost extra.
Observability	Logs, metrics, and traces have plan-tiered ingest, retention, and active series limits.

Limits that shape usage

Depending on the area:

• runtime — max replicas per process, max pod size, total team budget
• storage — database storage size, object storage bucket size
• monitoring — active metric series, log ingest rate, log retention window, query range
• add-on backups — frequency, retention, count of stored backups

Team runtime budget

Each team has a runtime budget that gates aggressive scaling. You’ll see it most when:

• you scale processes up significantly
• you choose larger pod sizes
• you provision multiple heavier add-ons in parallel

If you hit a ceiling, the dashboard tells you which dimension is the bind.

Plan choice is a workload decision

Plans aren’t just a price tier. They shape:

• durability and replication
• scheduled backups vs. manual-only
• query and ingest performance
• retention windows

Pick based on what your workload actually needs. The cheapest plan that fits is the right one — but if you guess wrong upward (over-provisioned) you waste money, and if you guess wrong downward (under-provisioned) you wake up at 3am.

See Add-on Plans for the full plan catalog.

Tips

• match plans to workload, not to the price ladder
• keep staging on smaller plans than production
• review observability plans before a traffic surge — log ingest is a common surprise
• don’t ignore limit warnings in the dashboard. They almost always become incidents if you do.