📄 markdown🕑 70d ago🚀 PaaS🧱 5 services
PlanetScale
planetscale.com ↗Pricing is primarily fixed monthly by chosen cluster/instance SKU, with no metered usage, add-ons, seats, or sales gating shown. Complexity comes from the large number of in-plan configuration options (CPU/memory, architecture, and storage variants) across multiple managed Postgres and Vitess services, which can make initial selection less straightforward but ongoing costs are predictable once selected.
model: gpt-5
0🧾
Pricing clarity
Easy to read
0🤖
Agent easiness
Breezy for bots
How we scored it 🧮
Every page starts at 100. Each kind of complexity subtracts points — here's the math.
🧾 Pricing clarity
79- Base score+100
- 5 plans to compare-14
- 173 in-plan configuration choices-14
- Spans 5 distinct services to navigate-4
- Plan breadth is reasonable for a 5-service platform+11
- Total79 / 100
🤖 Agent easiness
100- Base score+100
- Total100 / 100
The pricing tree 🌳
tap any branch to explore💳 Flat rate💱 USD🪜 5 tiers
The tiers 🪜
Postgres EBS HA (3-node)
- ✦High availability: 1 primary + 2 replicas
- ✦EBS-backed storage
- ✦Architecture choices: arm64 or x86-64
Postgres EBS non-HA (single node)
- ✦Single node (non-HA)
- ✦EBS-backed storage
- ✦Architecture choices: arm64 or x86-64
Postgres metal (3-node)
- ✦High availability: 1 primary + 2 replicas
- ✦Bare metal with included storage
- ✦Architecture choices: arm64 or x86-64
Vitess non-metal (3-node)
- ✦High availability: 1 primary + 2 replicas
- ✦Non-metal instances
- ✦Architecture: x86-64
Vitess metal (3-node)
- ✦High availability: 1 primary + 2 replicas
- ✦Bare metal with included storage
- ✦Architecture: x86-64
Watch out for 🕵️
- ⚠️Many in-plan configuration choices (numerous SKUs by vCPU/memory, architecture, and included storage across each service)