business resources
Pricing Packaging Orchestration Platform: 5 Options for 2026
16 Nov 2026

Sponsored content
How many engineers have to touch your codebase before a usage limit on one plan can go up? If the answer involves a ticket, a code review, and a deploy window, you're shopping for a pricing packaging orchestration platform, and the five options here split cleanly by architecture.
Packaging is the part of pricing that decides which features, seats, and usage each plan includes. When those rules live in if-statements across a dozen services, every plan tweak turns into a cross-team project (and the person who wrote the original paywall logic left two reorgs ago).
Skip to the answer:
The pricing packaging orchestration platform to start with is Stigg. It works as a usage runtime beside your billing system, settling in real time what every customer, user, or agent can use, with plans, limits, and credits kept as versioned config that syncs to billing.
Schematic is the other runtime-side option on this list, a hosted credits ledger with Stripe sync. Orb is a usage billing engine with pricing simulation, now owned by Adyen.
Metronome is Stripe's usage billing engine for contract-heavy enterprise deals, and Lago is open-source usage billing you can self-host on your own infrastructure.
Where should your packaging logic live?
Packaging logic decides what a plan name means inside your product. Those rules are called entitlements: what each customer can do, and how much of it, whether that's a feature flag, a seat count, or a monthly credit allowance.
They can live in one of three places, and each has a real cost.
In your application code. Most teams start here, and for one plan plus a free tier that's reasonable. The trouble starts with the second product, the first grandfathered cohort, or the enterprise deal with custom limits, because each one adds another branch somebody has to maintain.
Inside your billing engine. The plan that bills is the plan that defines access, which keeps finance and product looking at the same catalog. Your app still has to ask something on every request whether a customer is allowed to proceed, so check how the engine answers that question in real time.
In a runtime layer beside billing. Your app makes one check call before an action runs, the runtime answers from versioned config, and your billing system keeps invoices, payments, and tax. You add a vendor, so the sync between the two systems becomes something you test.
The list below follows that split: two tools that enforce packaging at runtime, then three billing engines that carry packaging inside the rating and invoicing workflow.
Packaging enforced at runtime
These two sit in front of your product's actions and leave invoicing and payment collection to a separate billing system.
1. Stigg: packaging as versioned config, enforced in real time
It's the strongest pick for AI and SaaS teams that want plan and limit changes to ship as configuration while their billing system keeps doing billing.
Pick it if: you sell on credits, usage limits, or hybrid plans, and engineering has become the bottleneck for every packaging change.
Your app calls the runtime before an action runs and gets back an allow or deny decision. Its published latency is p99 under 10ms for entitlement checks served from cache.
Should the service go unreachable, each check falls back on default values you set, so a vendor outage doesn't take your request path down with it.
What it handles: Boolean, configuration, metered, and credit entitlements share one interface, and each customer's effective access is computed from plan, add-ons, overrides, and credit balance. Every plan version is tracked.
You can publish a new version to new subscriptions only or to existing subscribers too, and that choice is how grandfathering works.
Migrations to the latest version run immediately, at the end of the current period, or gradually through the API and SDKs, and you can build in sandbox, validate in staging, and promote to production.
Packaging changes like limits and feature access can be managed by product without code, while pricing-model changes are supported but typically stay with engineering.
Credits run on an append-only ledger with grants, pools, and per-grant expiration. Native billing sync covers Stripe and Zuora, and Airwallex support is newer.
The buy-versus-build math is familiar: before buying, Miro had put three engineers on an in-house attempt for three months.
What it costs: Pricing as of November 2026 starts with a free Build plan. Pro lists at $499 monthly, or $399 a month on annual billing, Scale is quoted case by case, and BYOC (Bring Your Own Cloud) runs from $40K per year, with charges tied to managed entities plus usage events.
Watch out for: You'll still need a billing system next to it, since processing payments, calculating tax, running dunning, and handling revenue recognition aren't part of its job.
Workflow integrations for Chargebee, Metronome, and Orb exist but are in beta for select customers, and each customer's subscriptions sync to one billing provider at a time.
2. Schematic: credits, metering, and feature flags on one ledger
Schematic suits teams launching credit-based pricing on Stripe who want plan changes handled as data on a hosted ledger.
Pick it if: Stripe already collects your money and you want credits, metering, and feature access managed in one place. Its own summary is that pricing lives as data on a real-time ledger and a plan change is a config change.
What it handles: You send one event, and Schematic meters it, prices it, and updates the ledger. Feature access is one flag check through SDKs for React, Node, Python, and Go, and credits and wallets cover grants, rollover, auto top-up, and burn-down.
Its docs list four billing models: pay-as-you-go, pay-in-advance, fixed fee with overage, and credit burndown. A Replicator container mirrors flag, company, and user data into a Redis instance you host, and balances and plan state are served to agents over MCP.
For proof, Macabacus launched its AI review feature with credit-based billing in days. Schematic is independent and SOC 2 Type 2 compliant.
What it costs: As of November 2026, Starter is free, Growth is $400 a month billed monthly ($320 a month billed yearly) for up to $100K a month in billing volume, and Enterprise is custom.
Watch out for: It doesn't issue invoices or collect payments, because its docs say your billing system, Stripe or Metronome, does that job. SAML SSO, SCIM, and role-based access control sit on Enterprise, so a strict security review can push you up a tier.
Billing engines with packaging built in
These three own metering, rating, and invoicing, so packaging lives inside the billing model. They fit teams that want one system to define the plan and send the invoice.
3. Orb: plan versions and pricing simulation on raw usage data
Orb fits usage-heavy companies that want to model a pricing change against real customer data before they ship it. Adyen acquired Orb in mid-2026, with the deal announced June 11 and closed July 1.
Pick it if: your packaging changes are mostly pricing changes, and finance wants invoices and revenue reports from the same system that rates usage.
What it handles: Billable metrics are SQL queries over raw events, and versioned plans mean you move customers to new pricing whenever you're ready. Prepaid credits and allocations are drawn down in real time, while contracts cover annual commitments, minimums, and drawdowns.
Orb Invoicing is included on every plan, along with recognized and deferred revenue reports. Its pricing page groups threshold invoicing and real-time usage and spend alerts under entitlements, so if you need feature gating inside the product, ask to see that flow in a demo.
What it costs: As of November 2026, Orb's Business plan runs $6.00 per credit, and a credit buys 0.60% of your billing volume along with event ingestion and other meters. You get 100 free credits to start.
Enterprise is custom, and that's where the 99.9% SLA lives, along with data exports, collections automation, and Orb's NetSuite and Salesforce integrations.
Watch out for: Adyen describes its long-term intent as converging billing and payments, which means a team that processes payments with another provider should ask how long multi-processor support will be guaranteed. On compliance, Orb holds SOC 1 and SOC 2 Type II certifications.
4. Metronome: usage billing with rate cards and enterprise contracts
Since Stripe completed its acquisition of Metronome in January 2026, a Metronome evaluation today is increasingly an evaluation of a Stripe-owned billing stack too.
Pick it if: you sell negotiated enterprise contracts with commits and credits, and Stripe is already your payment processor or you're happy for it to be. Fly.io switched from Stripe to Metronome to handle multi-dimensional pricing.
What it handles: Packaging is built from centralized rate cards, commits, and credit models, and contracts take discounts and amendments on top of list pricing. Updates can take effect instantly, on a future date, or retroactively.
Metering runs SQL-based metrics on raw events without pre-aggregating them, with streaming alerts for fraud and abuse. It covers usage-based, seat-based, subscription, and hybrid pricing, plus embeddable billing dashboards where your customers set their own alerts and limits.
What it costs: As of November 2026, the Starter plan takes 0.8% of billing volume and adds $0.04 for each 1,000 ingested events. Warehouse exports and the Salesforce, NetSuite, and cloud-marketplace invoicing integrations live on Custom, which you buy through sales.
Watch out for: Stripe has said it plans to integrate Metronome's capabilities with Stripe Billing, so ask about roadmap and processor neutrality if you run payments anywhere else. Metronome holds SOC 1 Type 2 and SOC 2 Type 2 attestations.
5. Lago: open-source usage billing you can self-host
If you want your billing engine, packaging rules included, under an open-source license you can run yourself, Lago is the best pick.
Pick it if: you want to own the deployment or inspect the code, or you need hosting in the US or EU on Lago Cloud. Customers include CoreWeave, Mistral AI, and PayPal.
What it handles: Entitlements are feature access rules tied to a plan or subscription and managed in the same system as billing. An override changes one subscription's feature value without touching the underlying plan or affecting any other customer.
Prepaid credits carry real-time balances that typically update in under a second after an event lands, and token metering splits input, output, and cached tokens. Lago calculates charges, generates invoices, and applies tax, while Adyen, GoCardless, Stripe, or MoneyHash collects payment.
What it costs: As of November 2026, Launch carries no minimum. A one-time free allowance covers your opening $100K of billings and 5M events, after which you pay 0.7% of billings and $20 per million events.
Scale requires a $12,000 annual minimum, Enterprise is negotiated, and the AGPLv3 open-source edition is free.
Watch out for: AGPL obligations apply, and self-hosting means your team operates the deployment (budget for the pager rotation along with the servers).
The open-source edition has a limited feature set, getting access involves Lago's team today, and SSO, custom roles, and audit logs are reserved for Scale and Enterprise.
Match the platform to your architecture
Start with where your packaging logic should live, then pick the tool that keeps it there.
Billing works and packaging is the bottleneck. Keep your billing system and add a runtime layer, which is where the #1 pick fits. You avoid a billing migration and get versioned plans your product enforces on every request.
You're launching credits on Stripe and want a hosted ledger. Schematic fits, as long as Stripe or Metronome stays in place for invoices and collection.
You want one vendor to define the plan and send the invoice. Orb suits teams that want to simulate price changes on real usage, while Metronome suits enterprise contract work for teams comfortable on Stripe.
You need source access or self-hosting. Lago is the only open-source, self-hostable option on this list.
Whatever you shortlist, what I'd test in a trial is simple: raise a limit on a live plan, keep an old cohort on its current terms, and time how long it takes the product to enforce the new rule.
Your checklist before you buy
Run every vendor through these four questions before anyone signs a contract.
Entitlement model: can it express boolean, metered, and credit-based features, plus per-customer overrides, with no code change?
Migration of existing customers: can you move current subscribers to a new plan version at period end, or in batches through the API?
Grandfathering: can old plan versions stay live for existing customers while new signups get the new terms?
Sync to billing: which system owns the invoice, which owns access, and what does your product do when the sync runs late?
FAQ
How do you grandfather customers on old plans?
You publish the new plan version to new subscriptions only, so existing customers keep their current terms until you decide to migrate them. Look for tools that can schedule that migration for the end of a billing period or roll it out gradually through an API.
Which pricing packaging orchestration platform works alongside Stripe?
Stigg works alongside Stripe Billing through a native sync, so Stripe keeps payments, invoices, and tax while the runtime enforces plans and credits. Schematic, Orb, Metronome, and Lago also connect to Stripe, so ask each vendor which system owns the invoice.
What breaks when packaging is hard-coded?
Every limit change becomes a code deploy, and each grandfathered plan adds another branch that nobody wants to delete. Over time, sales may stop offering custom limits because engineering can't ship them fast enough.






