administration
Billing and plans
How VaultTerm plans, trials, grace periods, and entitlements work in SaaS — and how on-prem reads its tier from a signed license instead.
Updated Jun 23, 2026
VaultTerm offers four plans — Free, Pro, Team, and Enterprise — and enforces what each plan can do through a plan-entitlement matrix. The matrix maps a plan tier to the features and limits available to it, so feature gating is driven by the active tier rather than scattered through the code.
Plans and entitlements
The four tiers progress from individual use to organization-wide use. Higher tiers unlock more collaboration, longer audit retention, and additional administrative and integration capabilities. Exact feature boundaries are defined by the entitlement matrix and can change as the product evolves; the Audit logs page lists one concrete example — audit retention scales from 7 days on Free to unlimited on Enterprise.
The matrix is the single source of truth for what a tenant may do. When a subscription changes tier, the entitlements that govern the tenant change with it.
Trials and the grace window
New subscriptions can start on a trial, and a past-due subscription gets a grace window before its features lapse.
| Variable | Default | Purpose |
|---|---|---|
TRIAL_DAYS | 14 | Length of the trial period for a new subscription. |
GRACE_DAYS | 7 | Days a past-due subscription keeps its entitlements before lapsing to Free. |
The sequence for a paid plan that stops paying:
- The subscription goes past due.
- For
GRACE_DAYS, entitlements are retained so a transient payment failure does not immediately cut off access. - If the account is still past due when the grace window closes, features lapse to the Free tier — data is retained under Free’s limits, not deleted.
Checkout (SaaS)
In the SaaS deployment, checkout and subscription management run through Razorpay.
- Subscriptions are created and managed through Razorpay, with webhooks confirming payment and subscription state.
- Indian GST is applied at checkout: intra-state sales split into CGST and SGST, and inter-state sales use IGST, based on the configured seller state and rate.
GST behavior is environment-configurable (seller state, GSTIN, and rate), so the deployment computes the correct tax split for each customer.
On-prem: tier from the license
A self-hosted deployment has no billing catalog and does not talk to Razorpay. Instead it reads its tier from the signed license. The license carries the entitled tier; the entitlement matrix then applies that tier exactly as it would for a SaaS subscription. The license is cryptographically signed, so the tier cannot be forged. See Licensing and activation for how licenses are issued, verified, and activated.
Related pages
- Licensing and activation — how on-prem derives its tier.
- Audit logs — a concrete per-plan entitlement (retention).
- admin console — where billing and license state are surfaced.