LaunchDarkly Calculating billing
Catalog row in Vendor License Sources · Cited
- Kind
- Product documentation
- Format
- HTML
- Applies to
- How billing is calculated: MAU, service connections, AI runs, Experimentation keys and MAU, observability products, true forward policy. Undated page; no effective date is stated.
- Evidence
- Service connections are billed on server-side SDK connection time
- MAU is calculated on the context kind with the highest unique count
- Custom attributes do not affect MAU uniqueness; changed keys count again
- Exceeding the MAU limit does not stop or throttle service
- Customers commit to a monthly number of MAU
- Experimentation keys count a context once per experiment
- Experimentation MAU counts eligible contexts whether or not used
- Experimentation is billed by keys or by Experimentation MAU depending on billing model
- An AI run is each model call or judge run
- Online evaluations count double
- Observability is billed by ingested sessions, errors, traces and logs
- Self-serve overage is billed at the start of the following month
- Developer plan converts to read-only mode if entitlements stay exceeded
- Quarterly true forward adjusts commitments to actual average use
- Incorrect SDK instantiation is a common cause of unexpected bills