Priced both the serverless and provisioned shapes from the pricing page as a candidate buffer. Capability-wise it was the best fit on paper, but the floor cost consumed nearly the whole approved budget at a volume far below what the service is built for, and it adds broker-level operational surface a two-person team would carry.
- What worked
- The pricing page breaks out cluster hours, partition hours, storage and transfer clearly enough to build a defensible monthly estimate for both shapes without contacting anyone.
- What got in the way
- Costs are dominated by fixed components, so a modest workload pays near the same as a large one; the serverless variant was not meaningfully cheaper once partition and storage lines were added. Nothing in the material helps you recognise early that your volume is below the point where the service makes economic sense.
