Skip to content

Add-on Plans

Plan slugs follow the format <service>:<plan>. Use them with watasu addons:create:

Terminal window
watasu addons:create postgresql:standard-0 --app my-app

The dashboard always shows the current price, available regions, and exact resource numbers per plan. This page is the slug reference and the rough shape of each tier.

Plan slugTierNotes
postgresql:hobby-0HobbyCheapest. Manual backups only. Good for prototypes and review apps.
postgresql:hobby-1HobbyA step up from hobby-0 for slightly larger workloads.
postgresql:standard-0StandardProduction tier with scheduled backups.
postgresql:standard-1StandardMore storage and compute.
postgresql:standard-2Standard
postgresql:standard-3Standard
postgresql:standard-4Standard
postgresql:premium-1PremiumHigh availability with replication.
postgresql:premium-2Premium
postgresql:premium-3Premium
postgresql:premium-4PremiumLargest tier.
Plan slugTierNotes
valkey:hobby-0HobbySmallest, ephemeral.
valkey:hobby-1Hobby
valkey:hobby-2Hobby
valkey:standard-0StandardPersistent with manual backups.
valkey:standard-1Standard
valkey:standard-2StandardScheduled backups on supported plans.
valkey:premium-0PremiumHigh availability.
valkey:premium-1Premium
valkey:premium-2Premium
valkey:premium-3Premium
Plan slugNotes
clickhouse (default)Use the dashboard for the current plan ladder.

ClickHouse plans differ on storage, compute, replication, and backup behavior. Pick deliberately based on dataset size and query concurrency.

Plan slugNotes
redpanda (default)See the dashboard for current tiers.

Plans differ on broker count, retention capacity, and throughput.

Plan slugNotes
object-storage (default)See the dashboard for storage and bandwidth tiers.
Plan slugNotes
logsTiered by ingest rate and retention.
metricsTiered by active series count and retention.
tracesTiered by ingest rate and retention.

The first time you attach any of these to an app, Watasu provisions Grafana automatically. See Observability Overview.

A few rules of thumb:

  • review apps and prototypes → hobby tiers (postgresql:hobby-0, valkey:hobby-0)
  • staging → one tier below production
  • production → match the workload, not the price ladder. Run smaller, watch metrics, scale up if needed.

For the operational implications of plan choice (durability, backups, retention), see each add-on’s individual page.