CU are managed work units
Use CU when you want Meridian to handle managed routing, optimization, compression, and execution strategy for heavier work.
Meridian Credits
Use CUs when you want Meridian to carry more of the routing, optimization, and managed model execution workload.
Choose the subscription that fits your workflow, then add credits when you need more managed throughput.
Use CU when you want Meridian to handle managed routing, optimization, compression, and execution strategy for heavier work.
Each plan unlocks a managed execution range. Choose the subscription first, then add CU when the workload grows.
Keep provider billing under your own keys when direct control matters. Use CU when Meridian-managed execution is the better fit.
Core Model
Credit Units support Meridian-managed routing, model use, compression, retrieval, and execution work.
BYOK lets Meridian run through your own model accounts so you keep direct provider billing and account-level visibility.
CUs use Meridian-managed keys so Meridian can optimize the execution path for better workflow density, cleaner handoffs, and less operational friction.
Hybrid mode lets Meridian use CUs first while keeping your own keys available when you want direct-provider access or a clean fallback path. This means if run out of CUs, you can still run the request with your own keys with no downtime.
Eligibility
Each plan opens a different managed execution range, from guided preview through governed volume.
Free starts with a guided managed preview built to deliver a fast, tangible first win. After that, Free can extend the experience with Starter and Small CU blocks.
Builder turns the guided preview into real repeatable delivery. It keeps BYOK available, reduces setup friction, and opens Starter, Small, and Medium CU blocks.
Pro+ is where Meridian-managed execution becomes a primary workflow choice, with deeper research, richer artifacts, guided builds, and the strongest individual Founding offer.
Teams buy pooled managed throughput for shared execution, faster coordination, manager visibility, and parallel delivery across the group.
Business adds corporate auth, stronger security controls, and a serious shared operating model for companies that want annual purchasing without full enterprise procurement.
Enterprise keeps CU inside governed routing, dedicated pools, and custom commercial review.
Published Blocks
Choose the credit block that matches how much managed execution you want available.
Guided preview
The fastest way to get to something tangible. Ideal for landing pages, small app shells, campaign assets, first-pass content, and quick proof of concept work. CUs are units of work, not raw token buckets.
Expiry: 60-day expiry
Individual refill
A practical refill for individual builders who want enough CUs to keep momentum without stepping into a larger commitment.
Expiry: 90-day expiry
Individual refill
The strongest refill available in Pro. It fits repeated site builds, denser coding sessions, stronger content pipelines, and regular managed execution.
Expiry: 90-day expiry
Pro+ Refill
A heavier individual refill for operators who want Meridian-managed execution available whenever work spikes.
Expiry: 120-day expiry
Pro+ Refill
A longer individual runway with better unit economics for buyers who want managed execution ready at all times.
Expiry: 180-day expiry
Pro+ Refill
A serious CU reserve for heavy individual workflows that want lower cost per unit and fewer refill decisions.
Expiry: 365-day expiry
Pro+ Refill
The largest published individual CU block for operators who want sustained managed throughput without moving into team buying yet.
Expiry: 365-day expiry
Teams
The entry shared CU block for delivery groups that want pooled managed execution without building a large inventory position up front.
Expiry: 90-day expiry
Teams
A stronger shared refill for teams that rely on Meridian regularly across planning, reviews, builds, and delivery.
Expiry: 120-day expiry
Teams
A larger pooled position for teams with heavier agent usage, denser reviews, and more parallel execution.
Expiry: 180-day expiry
Teams
Built for sustained throughput across multiple seats, longer workstreams, and more frequent managed execution.
Expiry: 365-day expiry
Teams
The highest published team block before the conversation turns into enterprise volume planning.
Expiry: 365-day expiry
Business
The entry business CU block for governed environments that need dedicated routing, larger throughput, and predictable managed execution.
Expiry: 365-day expiry
Business
A stronger business volume position for organizations running larger workflows, denser audits, and more continuous execution.
Expiry: 365-day expiry
Business
Built for heavier governed usage where Meridian-managed execution supports multiple teams or sustained operational demand.
Expiry: 365-day expiry
Business
The highest published business CU block for organizations that need large managed-execution inventory under controlled routing.
Expiry: 365-day expiry