
Multi-Tenant Architecture: 3 Models & 8 Best Practices
Learn how multi-tenant architecture works, compare database isolation models, and explore six components & eight best practices for shared infrastructure.
A hybrid pricing model pairs a flat fee with usage charges. See the main types, real AI-company examples, and how to design one for your AI product.
Product wants to add usage-based charges to your AI subscription. Sales needs custom allowances for enterprise accounts. Engineering gets the tickets for metering, credit balances, plan changes, and overage enforcement.
A hybrid pricing model combines a fixed recurring fee with charges based on consumption. The pricing page may need one extra line, but the application needs rules for every request.
We'll break down the common models, real examples, and technical decisions involved.
A hybrid pricing model combines a fixed recurring charge with variable pricing based on consumption. Customers pay for a subscription or committed allowance, then incur additional charges when their usage exceeds what's included or falls into a metered category.
The fixed portion covers access to the product and its included features, and the variable portion accounts for usage such as API calls, AI credits, tokens, or compute time.
Hybrid pricing can combine subscriptions, tiers, credits, and usage commitments. Four structures cover many of the models used by AI products and API platforms.
| Model | How it works | Example |
|---|---|---|
| Base fee + overage | Fixed fee with charges beyond included usage | $79/month + $0.02 per extra API call |
| Seats + credits | Access charged per seat, with an AI credit allowance | $25/seat + shared AI credits |
| Commit + drawdown | Customer commits to a usage budget and draws against it | $24,000 annual AI credit commitment |
| Tiers + usage | Different plans include different allowances and metered features | Pro plan + paid video generations |
Each model creates different requirements for usage tracking and enforcement.
Base fee plus overage works well when customers expect regular usage but occasionally exceed their allowance.
An AI transcription service could include 500 processing minutes per month and charge for every additional minute. Customers keep the same plan while their bills reflect heavier usage.
The main risk is an unexpected bill. Usage alerts, spending caps, and clear overage rates help customers understand what they'll owe.
Our overage pricing guide covers how to calculate additional consumption and enforce spending rules.
Some collaborative AI products charge for access and provide a shared credit pool for expensive operations.
A company with 30 paid seats might receive 15,000 AI credits per month. Employees and agents draw from that allowance when generating reports, processing documents, or running models.
The tricky part comes when several agents spend credits at once. Atomic deductions prevent concurrent requests from consuming the same balance, while account-level budgets control total usage.
Enterprise buyers often prefer a committed usage budget.
A customer might commit $24,000 annually to an AI platform, and each eligible operation draws down the available commitment at its contracted rate.
An unused balance can become a commercial problem near renewal, while consumption beyond the commitment needs a defined policy.
The infrastructure must track committed amounts, spending eligibility, and drawdown history. Contracts may also include minimums, custom rates, or expiration terms.
Tiered plans can bundle different usage allowances while charging for selected features.
A Basic plan might include 1,000 document-processing credits, while Pro includes 10,000. Premium model calls could carry separate consumption rates on either plan.
Customers get a familiar upgrade path, and the provider can account for workloads with higher processing costs.
Plan upgrades need accurate entitlement updates, especially when customers change tiers halfway through a billing cycle. Our tiered pricing guide explains how allowances and feature access work across different plans.
Imagine an AI API platform charging $79/month with 8,000 included requests. Every additional request costs $0.02. The customer's monthly bill changes with consumption:
| Billing component | Calculation | Charge |
|---|---|---|
| Base subscription | Fixed monthly fee | $79 |
| Included usage | First 8,000 requests | $0 extra |
| Overage | 3,000 requests × $0.02 | $60 |
| Total monthly bill | 11,000 requests consumed | $139 |
Illustrative pricing. Actual vendor prices may differ.
The customer keeps their base subscription and pays for the extra 3,000 requests. At 6,000 requests, the bill would remain $79.
Hybrid pricing gives the provider a recurring fee while connecting additional charges to consumption. The challenge is keeping usage measurements, customer allowances, and final charges consistent.
Hybrid pricing looks different depending on what customers pay to access and what drives consumption. As of October 2026, Anthropic, GitHub, Notion, and Supabase show four ways to combine recurring charges with metered usage.
Claude Enterprise combines a $20 seat component with usage billed at API rates. The final cost depends on which models customers use and how much work those models perform.
Consider an enterprise account where one employee asks Claude to summarize documents while another runs complex agent workflows. Both have product access, but their workloads create different usage charges.
For engineers, model access and spending eligibility need separate checks. A customer may have permission to use a premium model but lack the remaining budget to authorize another request.
A developer using GitHub Copilot for code completion consumes resources differently from someone running multi-step coding agents.
Copilot addresses the difference through monthly AI credit allowances. Pro costs $10/month with $10 in base credits plus a $5 flex allotment, while Pro+ costs $39/month with $39 in base credits plus $31 in flex. Customers can purchase more when their allowance runs out.
Credit costs vary by model and task, which introduces an engineering requirement: usage needs a consistent rating system. Each operation must map to the correct credit cost, and deductions must respect the customer's available balance and spending rules.
Notion splits AI into two buckets. Business and Enterprise subscriptions include several AI capabilities, while Custom Agents draw from purchased credits priced at $10 per 1,000.
Imagine several workspace agents processing requests throughout the day. Each agent consumes credits from the same allowance, and longer workflows can cost more.
Shared credit pools introduce concurrency and allocation challenges. The system needs to track consumption across agents, prevent overlapping deductions, and give administrators visibility into where credits are going.
Supabase Pro starts at $25/month and includes $10 in compute credits. Resource charges depend on the compute instances and other services a customer uses.
A developer might run a small production database alongside a compute-heavy project. Both sit under the same account, but their resource consumption contributes different charges.
Multiple meters need consistent account-level attribution. Supabase illustrates why hybrid pricing infrastructure must connect included credits, resource usage, and billing records without losing track of which service generated each charge.
Prices are subject to change without notice. Always visit the official company websites for the most up-to-date pricing information.
The common thread across these models is the need to connect customer access with consumption. Once usage affects what customers pay, engineering needs accurate metering, current entitlements, and spending controls that work during execution.
Hybrid pricing gives customers a predictable starting point while allowing providers to charge for consumption that exceeds included allowances.
The benefits look different depending on which side of the invoice you're on.
The biggest advantage for AI products is controlling how usage maps to revenue. A customer running expensive reasoning models can generate more charges than one using basic text generation.
Predicting the final bill gets harder when AI agents enter the picture.
Challenges of hybrid pricing models
Hybrid pricing adds challenges when subscriptions, usage charges, and access rules need to work together. Four challenges deserve attention:
The engineering challenge grows with every pricing exception, especially when customers share credits across agents or negotiate custom spending limits.
Designing a hybrid pricing model comes down to five decisions: the value metric, the base fee, the included usage and overage rate, prepaid or postpaid billing, and how you test it all against real workloads.
Start with something customers can connect to the work your product performs. An AI document-processing platform might charge per document, while a developer API could meter requests or tokens.
Your billing metric can differ from your compute metric. You might charge per document while tracking tokens, model calls, and processing time to understand the cost of each operation.
Our usage-based pricing guide compares six models and their implementation requirements.
Imagine a $79/month subscription with standard model access, basic automation, and 8,000 API calls. Customers know what their plan covers, and engineering has an allowance to enforce.
But what happens at request 8,001?
Feature entitlements and usage limits need separate rules. Customers may retain API access after exhausting their allowance, with additional requests subject to overage charges, spending caps, or a hard stop.
Your existing usage data can help determine a reasonable allowance. Compare consumption across customer segments and identify which models or operations carry the highest inference costs.
A plan with 8,000 included calls and $0.02 per additional request would charge $60 in overages for 11,000 calls.
The engineering requirement is consistent rate versioning across metering, enforcement, and billing. When pricing changes, each usage event needs the rate applicable at the time of consumption.
Prepaid credits appeal to customers who want a fixed budget. Each purchase creates a credit grant with its own balance, expiration rules, and spending priority.
Postpaid overages allow approved customers to continue consuming after their included allowance runs out, with charges appearing on the next invoice.
Both require different safeguards. Prepaid credits need atomic deductions and grant tracking, while postpaid usage requires spending caps and reliable metering. Our AI credits guide covers credit wallets, grant expiration, and request-time enforcement.
A spreadsheet can tell you whether the numbers work. Production testing reveals whether the rules hold when requests overlap, operations fail, or customers change plans during active jobs.
Test these four areas before launch:
Include concurrent agents, failed reservations, retries, and mid-cycle upgrades in your tests. These scenarios expose balance discrepancies and enforcement failures that ordinary usage reports can miss.
Use the results to adjust allowances, consumption rates, and spending policies before deploying the pricing changes.
Hybrid pricing infrastructure needs entitlements, usage metering, runtime enforcement, credit tracking, and billing working from consistent customer and consumption data. Each component handles a different part of the pricing model.
| Component | What it handles | What can go wrong |
|---|---|---|
| Entitlements | Feature access, plan allowances, and limits | Outdated access rules |
| Usage metering | Consumption across accounts and features | Missing or duplicate events |
| Runtime enforcement | Spending checks before execution | Unauthorized usage |
| Credit ledger | Grants, deductions, and adjustments | Incorrect balances |
| Billing | Usage charges and invoices | Billing discrepancies |
Consider an AI agent with access to a premium model and 40 credits remaining. The next operation could cost 60 credits. Your billing provider can record the charge, but the application needs to decide whether that request can proceed.
Runtime enforcement checks the customer's current entitlement, available balance, and overage policy before authorizing the operation. If multiple agents share that allowance, atomic reservations help prevent overspending.
Metering and billing still need the final consumption records to reconcile charges with what the application permitted. Our hybrid billing engineering guide explains how these components connect, including entitlement resolution, usage tracking, and billing synchronization.
Building hybrid pricing in-house works well when you have a few plans, one usage meter, and fixed overage rates. A small set of database tables and application logic can handle the job without adding another vendor.
The harder question is whether your system can support the next pricing change. An enterprise customer wants custom rates, another needs shared AI credits, and existing customers must keep their original plan terms.
Before choosing to build, consider what your engineers will need to own:
A working first version tells you little about the maintenance cost six months later. Every new pricing rule needs testing across active subscriptions, usage records, and spending controls.
If your requirements are stable and your engineers can support the system, an in-house build remains a practical choice. Dedicated infrastructure becomes worth evaluating when pricing changes repeatedly require engineering work or shared usage introduces concurrency and reliability risks.
Before deciding, estimate the engineering effort behind your next three pricing changes. How many require new code, migrations, or changes to request-time enforcement? The answer gives you a more useful comparison than the initial build cost alone.
How many services need updating when you change an AI plan's included credits or overage rules?
If the answer involves several repositories, entitlement checks, and billing scripts, Stigg gives those decisions a shared runtime. Your application can enforce current customer allowances while Stripe or Zuora handles payment workflows.
Stigg covers the parts engineers end up maintaining:
Once you’ve designed the hybrid pricing model, it’s time to make sure every request follows its rules. Stigg's documentation shows you how to wire up the runtime.
A hybrid pricing model combines a fixed recurring fee with usage-based charges. Customers pay for baseline access, then incur additional costs based on consumption, such as API calls, AI credits, or compute time.
A hybrid pricing model example is an AI platform charging $99/month for 10,000 API calls, then $0.01 for each additional call. A customer using 15,000 calls would pay $149 for the month.
A hybrid pricing model provides predictable recurring revenue and usage-based expansion. Customers get a known starting price and can pay for additional consumption without upgrading their entire subscription.
The main difference between hybrid pricing and usage-based pricing is the fixed recurring fee. Hybrid pricing combines subscriptions with variable charges, while pure usage-based pricing charges customers according to consumption without requiring a base subscription.
The four common types of hybrid pricing models are base fee plus overage, seats plus credits, committed spend plus drawdown, and tiered plans plus usage. Each combines a fixed payment or commitment with a consumption-based component.
The main types of pricing models are flat-rate, per-seat, tiered, usage-based (including credits and tokens), and hybrid. Hybrid pricing combines a fixed subscription or seat fee with usage-based charges, so customers get a predictable base cost while the bill still scales with consumption.