Entitlement layer between product and billing for plans, feature limits, credits, and overages.
Schematic is an entitlement management platform that sits between your application code and your billing system. Instead of hard-coding plan logic — which features a customer gets, how many units they can consume, what happens at the limit — engineering teams define plans, feature flags, and usage limits in Schematic and check them at runtime via API. It layers on top of Stripe-style billing, adding the packaging brain that raw billing systems lack, and ships embeddable components for customer-facing plan and usage views. B2B SaaS teams use it to change packaging without redeploying code.
Which of the capability map's modules Schematic covers — each links to the module's own page, with every tool that supports it.
| Module | Phase | Depth | Note |
|---|---|---|---|
| Win the Deal | |||
| Freemium Limit Management | Digital Commerce | Supported | |
| Trial Provisioning & Management | Digital Commerce | Supported | |
| Self-Serve Upgrade Nudges | Digital Commerce | Partial | Limit events can drive upgrade prompts, but campaign-style nudge orchestration lives elsewhere |
| Fulfill & Bill | |||
| Entitlement Management (Feature Flags, Caps, Access) | Fulfill & Activate | Core | Plans, feature gates, and usage limits defined centrally and versioned as packaging changes |
| Wallet / Credit Drawdown | Consume & Meter | Supported | Credit balances that features draw down against, bridging prepaid models into enforcement |
| Overage & Burst Policies | Consume & Meter | Supported | Configurable behavior at the limit — block, allow overage, or route to upgrade |
| Grow Revenue | |||
| Entitlement Enforcement (Real-Time) | Platform & Intelligence | Core | Runtime API and SDK checks answer whether this customer can use this feature right now |
| Embeddable UI Components | Platform & Intelligence | Supported | Drop-in components for plan pickers, usage meters, and customer portals |
It occupies a deliberately narrow seam most stacks handle badly: the gap between a feature-flag tool that knows nothing about billing and a billing system that knows nothing about your application's features. Treating entitlements, metered limits, credit balances, and upgrade paths as one runtime-checkable model is the distinctive move.
No — it assumes one. Billing platforms own invoices, payments, and subscriptions; Schematic owns what the subscription entitles the customer to inside your product. It syncs with billing so a plan change there updates enforcement immediately.
Feature flags answer whether a flag is on for a user; they have no native concept of plans, metered limits, credits, or billing state. Teams do build entitlements on flags, but they end up re-implementing plan logic, usage counting, and billing sync themselves — exactly the layer Schematic packages.
By overlap on the capability map — computed, not curated.