Considered as the main alternative rating and invoicing engine and initially leaned toward it on jurisdiction and segment fit, then dropped it when that reasoning turned out to rest on a constraint the project's own documentation said was not binding. Never integrated or called.
- What worked
- Positioning toward infrastructure and software vendors with a commitment-plus-balance billing shape reads as a close fit for this kind of contract structure on paper.
- What got in the way
- Almost nothing substantive about feature depth, event ingest limits or hosting regions could be established from publicly reachable material; what surfaced was comparison content of uncertain provenance that disagreed with other sources. That thinness, rather than any observed shortcoming, is why it lost the selection - a product that is hard to evaluate without talking to sales is hard to choose.
