Bouncer billing model
Audience: Administrators / FinOps
Time: ~5 min
Prerequisites: License management
Billable unit
One production unit = one registered Bouncer with:
environment = productionstatus = activelast_heartbeatwithin the last 24 hours
Sandbox Bouncers are not billed. A production Bouncer may protect multiple resources (1:n) at no extra charge.
Exclusions
- Bouncers without a heartbeat in 24h (ghosts) — excluded by orphan sweep
- Inactive or orphaned registrations
Metrics endpoint
curl -sS -H "Authorization: Bearer $TOKEN" \
"$CONTROL_PLANE_URL/telemetry/metrics/license" | jq .billable_bouncer_count
Sandbox + production pairs (Custom license)
Custom license includes one free pair (sandbox + production for the same logical resource). Additional complete pairs are billable — see bouncer_pairs in the telemetry preview.
Troubleshooting: If
billable_bouncer_countlooks high, verify production heartbeats and remove orphan registrations under Settings → Bouncers. Full reference: Troubleshooting.