Naming Convention

A DBaaS plan name tells you three key facts about the service without opening a table:

SegmentExampleMeaning
TierpremiumRedundancy & backup profile (Hobbyist —> Premium)
Node Count9xNumber of nodes in the cluster (omitted on single-node plans)
RAM per Node16Memory in GB for each node; aligns with Exoscale Compute flavors

Reading a Plan

premium-9x-16 —> Premium-tier cluster, 9 nodes, 16 GB RAM each.

Tier Quick Reference

  • Hobbyist
    single node, basic SLA, hourly backup (1 copy)
  • Startup
    single node, hourly + rolling 3-day daily backups
  • Business
    2 nodes, hourly + 14-day retention, 99.99 % SLA
  • Premium
    3 nodes, hourly + 30-day retention, 99.99 % SLA

Details (CPU, storage, price) live in the DBaaS plan tables.

Why the Pattern?

The scheme is shared by all engines (pg, mysql, kafka, opensearch, valkey, grafana) so teams can:

  • Spot Capacity
    larger last number = more RAM
  • Spot Resilience
    higher tier = more replicas/backups
  • Compare Costs
    same tier & size behave similarly across zones

NOTE
when creating or updating a service via CLI/API, the plan-string is the only argument you need to switch hardware, redundancy or price class.