Entitlements built for the AI era
Plans, add-ons, limits, and feature flags for SaaS and AI products, defined as data and enforced inside your product. Works with Stripe.
Ask anything about your accounts. A research run uses up to 25 credits.
Pricing changes shouldn't need a sprint.
How entitlement management works
From a feature in your product to a plan a customer can buy, in four steps and one check.
Define features
Boolean (SSO on or off), event-based (API calls a month), or trait-based (seats).
Feature types →Package plans and add-ons
One plan per company, any number of add-ons. Where they overlap, the most permissive entitlement applies.
Concepts →Check access in code
Pass a company key and a flag key. Schematic already knows the plan, overrides, and traits.
Flags →Connect Stripe
Map Stripe products to plans. A subscription provisions entitlements; a cancellation removes them.
Provisioning →import { useSchematicFlag } from "@schematichq/schematic-react"const canExport = useSchematicFlag("bulk-export")if (!canExport) {return <UpgradePrompt feature="bulk-export" />}// acme-robotics → true via plan entitlement (Pro)
One flag check. The answer already reflects the company's plan, overrides, and usage.
Under 50 msHow the check resolves
- 1Plan and add-on entitlementsThe plan's grants, and any add-ons on top.
- 2OverridesA company's exception wins over its plan, with an end date if you set one.
- 3No match: off by defaultThe check returns false and the feature stays disabled.
Move pricing out of your codebase
Plans, limits, flags, and overrides become data you change without a deploy.
- In-process cacheno round trip
- Schematicfirst load · p99 < 50 ms
- Your defaultuntil the first sync
Checks resolve inside your app
The SDK keeps your catalog, overrides, and usage in process and decides each check there. Changes stream to your app, so a check reflects them in real time.
Warn before the limit, enforce at it
Warnings, limit webhooks, and preflight checks.
Gate features by billing state
A boolean entitlement is a feature flag that reads the subscription. Turn a feature on for a plan, an add-on, or one company.
Built for sales-led deals
Grant one company an override with an end date, or a custom plan, without a ticket.
Iterate on pricing with plan versions
Legacy and current pricing run side by side. You decide if and when each company moves.
Works with Stripe, and the rest of your stack
A two-way sync keeps Stripe and Schematic aligned. Auth and CRM data arrive through the integrations below.
Customers and subscriptions import once
Schematic syncs with Stripe, no migration or parallel billing required.
Stripe products map to plans
Entitlements are automatically provisioned according to the subscription.
Changes flow back
Plan changes made in Schematic update the subscription. Metered usage lands as meter events.
And the rest of your stack
Docs ↗Organizations, users, and memberships import through Clerk webhooks and stay in sync.
Docs ↗Organizations, users, and memberships import through WorkOS webhooks and stay in sync.
Docs ↗Add Schematic as a destination. Your track and identify calls fill traits and metered features.
SalesforceDocs ↗A Flow HTTP callout upserts companies and traits into Schematic from your records.
Docs ↗A workflow custom code action upserts companies and traits into Schematic from your records.
WebhooksDocs ↗Subscribe to company, catalog, billing, and usage-limit events, each with a typed payload.
Integrate in an afternoon
Most teams arrive with a plan column and a pile of if-statements. Move them one check at a time, with the old branch still in place until the new one is live.
- 1Define your featuresBoolean, event-based, or trait-based. Name them the way your code already does.
- 2Map plans to Stripe productsCustomers and subscriptions import once, then stay in sync. Nothing moves off Stripe.
- 3Wrap the first checkOne SDK call beside the branch it replaces. Ship it behind your existing plan column.
- 4Delete the branchThe plan column goes. The next tier, limit, or exception is a catalog change, not a deploy.
Entitlements for every pricing motion
Same catalog, same check. Four ways teams use it in production.
“We chose Schematic because it provided the flexibility to launch, package, meter, and monitor features from one place without having to continue maintaining a homegrown system or constantly involve engineering.”
Pricing and packaging were hard-coded in application code, and a new tier took over three months to launch.
Read the Automox story →Schematic vs. the alternatives
Build it, bolt it onto Stripe, stretch a flag tool, or use Schematic. Billing tools and release flag tools do different jobs. Entitlements sit between them.
  | Build in-house | Stripe Billing + Entitlements | Release flag tool | |
|---|---|---|---|---|
Plans, add-ons, and limits as config | Yes, one catalog | You build it | Features on products; limits in your code | Long-lived targeting on segments, maintained by hand or synced |
Runtime access check | One SDK call, under 50ms with local caching | You build it and the cache | Your app provisions from a webhook | Yes, built for releases |
Usage limits per plan | Event- and trait-based | You build it | In your code | Not in the flag model |
Overrides with expiry | Yes | You build it | Edit the subscription | Per-customer targeting |
Plan versions and migration | Choose who moves | You build it | Feature changes apply next billing period | A different job |
Credits held for in-flight work | Leases and reservations | You build the ledger | Not built in | Not in the flag model |
Spend caps per hour or per user | Hourly, daily, and per-draw | You build it | Not built in | Not in the flag model |
Trials that convert or revert | Converts or moves to a fallback plan | You build it | Subscription trials; access in your code | Targeting removed by hand |
Stripe subscription sync | Two-way | You build the webhooks | Native | Not built in |
Best for | Access tied to what customers pay | Unusual needs, spare engineers | Payments, invoices, and tax | Release safety and experiments |
“We were looking for an entitlement platform, and if we had to build one ourselves we would have to relearn all the lessons Schematic has over the years. It is not really Schematic versus anyone else. It is Schematic versus being dumb and building it.”
Built for enterprise
Fast, secure, reliable.
Observability
- Audit logs and real-time events
- Client-side rule evaluation
- Replicator: reads stay in your network
Frequently asked questions
Short answers, each one backed by the docs. Still stuck? The docs and the demo both go deeper.
More on feature entitlements
Stop hard-coding your pricing
Start free with unlimited feature flags and up to 10 monetized subscriptions. Paid plans from $400 a month.