A Credit Unit is a unit of work
One CU covers the managed resources needed for a piece of work — so the number tracks what you get done, not a provider-specific meter.
A Credit Unit funds YAKKL-managed execution — the routing, optimization, and model work behind a task. Choose the subscription that fits your workflow, then add credits when you need more managed throughput.
Orchestrator includes 250 Credit Units a month. Founding pricing through January 31, 2027.
One CU covers the managed resources needed for a piece of work — so the number tracks what you get done, not a provider-specific meter.
Each plan opens a different band of managed execution. Pick the subscription that matches how you work first, then add credits when the workload grows past it.
Bring your own provider keys when you want direct vendor billing. Use Credit Units when you would rather hand the execution path over. Both work at once.
Credits and your own provider keys are not an either/or. Pick the billing shape that fits, and change it whenever it stops fitting.
BYOK lets YAKKL run through your own model accounts so you keep direct provider billing and account-level visibility.
CUs use YAKKL-managed keys so YAKKL can optimize the execution path for better workflow density, cleaner handoffs, and less operational friction.
Hybrid mode lets YAKKL use CUs first while keeping your own keys available when you want direct-provider access or a clean fallback path. This means if you run out of CUs, you can still run the request with your own keys with no downtime.
Each plan opens a different managed execution range, from guided preview through governed volume.
Orchestrator is where YAKKL-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.
Choose the credit block that matches how much managed execution you want available. Blocks stack on top of whatever your plan already includes.
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.
Expiry: 30-day expiry
A practical refill for individual builders who want enough CUs to keep momentum without stepping into a larger commitment.
Expiry: 60-day expiry
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
A heavier individual refill for operators who want YAKKL-managed execution available whenever work spikes.
Expiry: 120-day expiry
A longer individual runway with better unit economics for buyers who want managed execution ready at all times.
Expiry: 120-day expiry
A serious CU reserve for heavy individual workflows that want lower cost per unit and fewer refill decisions.
Expiry: 180-day expiry
The largest published individual CU block for operators who want sustained managed throughput without moving into team buying yet.
Expiry: 240-day expiry
The entry shared CU block for delivery groups that want pooled managed execution without building a large inventory position up front.
Expiry: 30-day expiry
A stronger shared refill for teams that rely on YAKKL regularly across planning, reviews, builds, and delivery.
Expiry: 60-day expiry
A larger pooled position for teams with heavier agent usage, denser reviews, and more parallel execution.
Expiry: 90-day expiry
Built for sustained throughput across multiple seats, longer workstreams, and more frequent managed execution.
Expiry: 120-day expiry
The highest published team block before the conversation turns into enterprise volume planning.
Expiry: 180-day expiry
The entry business CU block for governed environments that need dedicated routing, larger throughput, and predictable managed execution.
Expiry: 365-day expiry
A stronger business volume position for organizations running larger workflows, denser audits, and more continuous execution.
Expiry: 365-day expiry
Built for heavier governed usage where YAKKL-managed execution supports multiple teams or sustained operational demand.
Expiry: 365-day expiry
The highest published business CU block for organizations that need large managed-execution inventory under controlled routing.
Expiry: 365-day expiry
Pick the subscription that matches how you work — the included Credit Units cover most months. Add a block when a build spikes past them.
Product launches, Founder's Program windows, engineering updates, and platform releases. No spam, and one-click unsubscribe.