Product capabilities
Manage product entitlements.
Define access with plans, metered usage, credits, add-ons, and customer overrides. Subscrio resolves the result inside your .NET or TypeScript application.
Define the entitlement
Choose the entitlement model.
Plans, meters, credits, add-ons, and overrides solve different access and usage needs.
Plans
Set the standard features, limits, and values included in a package. Subscriptions assign that plan to customers.
Metered usage
Give a feature its own allowance for a period. Record accepted use and enforce the limit when work is requested, as in this monthly usage quota example.
Credits
Grant a spendable balance that several actions can share. Issue credits directly or on a plan schedule, with optional expiration. See how a shared credit wallet works across products.
Add-ons
Attach reusable feature bundles or extra capacity to a subscription. Quantities let customers buy repeatable packs.
Overrides
Set an exception for one subscription without changing the plan for everyone. A timed override can end at a specific time.
Feature values can be toggles, numbers, text, or metered allowances. Compare the models in the documentation
Assign and maintain access
Sell it once or renew it.
Your application turns a confirmed order, contract, or billing event into a customer assignment. Subscrio then evaluates that assignment over time.
- Payment confirmed
- Plan assigned
- Non-expiring access
- Billing event received
- Plan assigned or changed
- Renew or end
- Trials and scheduled startsGrant trial access or schedule a subscription to become active later.
- Plan changes and migrationsMove a customer between packages or transition an expired trial to a free plan.
- Cancellation and expirationUse lifecycle dates to stop access when the agreement ends.
- Recurring and expiring creditsIssue plan credits on a schedule and control when each grant expires.
Resolve the result
Know what a customer can use now.
Subscrio combines the sources that apply to a customer and returns the feature value your application can check before doing work.
Base value
Two 10-seat packs
Before exceptions
Acme until October
Explanation methods show which sources contributed to a feature value. See how multiple subscription entitlements combine. Metered usage and credit spending use separate atomic operations with idempotent retries.
Build and operate
Use it in your stack.
The open-source entitlement engine runs with your application and stores entitlement data in your database. Add the management workflow your team needs.
Your database
Keep entitlement records with your application data and run checks without a hosted Subscrio service.
Native C# and TypeScript libraries
Resolve entitlements in your application with APIs for each language. In ABP applications, the ABP integration example shows how to keep using IFeatureChecker.
Billing system integration
Map verified purchases and subscription events to Subscrio. The optional Web Admin can process Stripe subscription events.
Extensibility and hooks
Connect entitlement changes to your own workflows through hooks and extensions.
Web Admin and REST API
Manage the catalog and customer assignments through a self-hosted interface or API.
Explanations and audit trail
Inspect why a value resolved as it did. The Web Admin provides transaction logs for customer, subscription, and Stripe activity.
Prevent Stripe Drift
A synchronization workflow will detect when Stripe and Subscrio subscription records diverge and help bring them back into sync. Read how Stripe drift happens.
Common questions
Questions about Subscrio entitlements
Can I use Subscrio for one-time purchases?
Yes. After your billing system confirms a purchase, create a non-expiring subscription to the purchased plan. Subscrio does not collect the payment.
How are metered usage and credits different?
Metering tracks one feature's allowance for a period. Credits are a spendable balance that several actions can share. Subscrio supports both models for different features.
What happens when an add-on and an override affect the same feature?
Subscrio combines the plan value and applicable add-ons first. An active subscription override replaces that result for the feature.
Can a customer have more than one subscription?
Yes. Subscrio resolves each eligible subscription and combines their values using the configured rule for that feature.
Does Subscrio replace billing or user permissions?
No. Billing confirms purchases and renewals; your integration updates Subscrio. Your application still authenticates users and decides which users may perform an action.
Next step
Start with one entitlement check.
Define a feature, set a plan value, assign a customer, and resolve the result in your application. Add usage, credits, and exceptions when your product needs them.