Why Crovver?
Building billing is slow, fragile, and a distraction from your core product. Crovver gives you:Payment Provider Agnostic
Swap between Stripe, Khalti, eSewa, or others without changing your
application code.
Entitlement Engine
Gate features by plan in one line. No custom permission logic needed.
Seat-Based Billing
Built-in capacity tracking with proration on upgrades. Works for B2B
workspaces out of the box.
Usage Limits
Track API calls, storage, messages — enforce limits without custom infra.
How It Works
Crovver exposes a set of APIs your app calls, a React SDK for the frontend, and a webhook receiver for payment provider events. Your app never talks to Stripe directly — Crovver does. Crovver never stores payment credentials. All provider secrets are managed through a secrets manager (Infisical or Vault).Key Primitives
| Concept | Description |
|---|---|
| Org | Your company — the top-level entity in Crovver |
| Tenant | A billing unit inside your app (a workspace, a user, a company) |
| Plan | A pricing tier with features, limits, and a price |
| Subscription | A tenant subscribed to a plan |
| Entitlement | Whether a tenant can access a specific feature |
Next Steps
Quickstart
Get your first subscription running in under 10 minutes.
Core Concepts
Understand the data model before you integrate.
React SDK
Add paywalls and feature gates to your frontend.
API Reference
Full reference for every endpoint.