A self-hosted customer-success core for B2B SaaS with explainable health scoring, churn-risk signals, renewals and revenue-at-risk prioritisation.
Why it exists
Early B2B SaaS teams can have product, billing and renewal data without having a usable daily queue for customer risk. The useful question is not “what is the score?” but “who needs attention first, why, and how much revenue is exposed?”
How it’s built
OpenRetention is a source-available customer-success system for teams that want a focused, inspectable risk workflow instead of a large enterprise suite.
- Keep the health model deterministic so every score can be explained.
- Separate usage, inactivity, payment and renewal signals instead of hiding them inside one opaque model.
- Order the risk inbox by commercial exposure so the operator sees what matters first.
- Keep deployment self-hosted and the core intentionally small enough to inspect.
Capabilities
Principles
Questions
Is OpenRetention open source?
Not before its Change Date. It is source-available under Business Source License 1.1 and the repository states the future Change License.
What does the health model use?
The deterministic model uses observable signals including product-usage decline, inactivity, payment state and renewal proximity.
Is it a full enterprise customer-success suite?
No full feature-parity claim is made. The current product is deliberately narrower and focused on self-hosted, inspectable risk and renewal workflows.