AI that ships inside apps — available Q3 2026
YAKKL Ari
Ari gives apps a controlled AI surface that feels native to the product. Vibe coders get an assistant they can embed into real screens. Developers get Credit Units, BYOK, hybrid routing, budgets, throttles, signed usage events, and an execution path that never trusts the browser.
powered by YAKKL® Ari™ Credit Units, BYOK, or hybrid policy Rust WASM client core Signed usage events
Builder Surface
Ari is the AI layer inside the app, not another detached chatbot.
Ari embeds into product surfaces through a Rust WASM core and TypeScript wrapper, then executes through the Ari runtime where identity, policy, billing, model routing, and usage events are enforced.
Ari Mark
Use a clean green circle. Drop the neon serif treatment.
Ari needs to look like embeddable infrastructure, not a novelty assistant. The primary mark uses a restrained green and Arial-style sans lettering. The alternates stay close enough to be useful without fracturing the brand.
Primary green
Recommended default. Strong green without the neon toy effect, readable at app-icon size.
Display green
Better for launch graphics, hero panels, and swag where the mark can be larger.
Forest green
Quieter and more premium. Use when Ari needs to sit beside Wallet or Meridian without shouting.
Execution Policy
Credit Units, BYOK, or hybrid routing belongs in policy, not in guesswork.
Every Ari app carries an explicit execution profile. Credit Units are the same YAKKL AI work unit used by Meridian, representing tokens, compute, cache, routing, and task cost. BYOK keeps provider billing under developer control. Hybrid policies define fallback behavior before traffic starts.
Managed execution
Credit Units are the same AI work units used by Meridian, covering tokens, compute, cache, routing, and task cost inside the Ari runtime.
Developer keys
Developer-owned provider keys can run through Ari policy with budgets, key rotation, provider controls, and usage records.
Explicit fallback
CU-first, BYOK-first, model-specific routing, and hard-stop policies give each app a clear execution contract.
Ari Pricing
Ari pricing combines product access with managed execution margin.
Subscription covers the controlled embed surface, portal policy, telemetry, verification, abuse controls, and support. Credit Units price the managed AI work. BYOK remains available for developer-controlled provider spend, but BYOK alone does not fund the runtime.
Builder preview
Founding previewFor Meridian-built apps and selected early products that need a native Ari surface, signed usage events, and basic policy controls.
- Embeddable widget
- Credit Units or BYOK
- Powered by YAKKL® Ari™ footer
App subscription plus CU
Subscription + priced CUFor apps that need developer-owned budgets, throttles, webhooks, key policy, usage records, and managed execution capacity.
- Portal policy controls
- Priced managed Credit Units
- BYOK fallback or BYOK-first routing
Governed deployment
CustomFor products that need higher request ceilings, stricter origin control, abuse review, enterprise telemetry, and custom runtime policy.
- Custom throttles
- Signed audit stream
- YAKKL platform overrides
Ari pricing is preview and subject to change. Credit Unit rates may adjust as model costs, cache economics, vendor pricing, capacity, and abuse controls evolve. YAKKL targets 30 days' notice for published CU schedule changes when vendor timing allows it. Ari embed access opens Q3 2026.
Control Layer
Embeds need authorization, budgets, throttles, and signed telemetry.
The Ari portal gives app owners key control, usage policy, event delivery, and abuse controls while YAKKL keeps platform-level authority to throttle, pause, or block traffic when risk changes.
Every embed is tied to an app, origin, and signed session
Ari verifies the app, allowed origin, active policy, session token, nonce, and expiry before execution reaches the engine.
Developer-defined ceilings with YAKKL platform overrides
Requests, tokens, output size, model access, daily spend, monthly spend, and concurrent usage stay inside policy limits.
Signed usage events for billing, analytics, and abuse review
Session start, request accepted, request blocked, fallback, throttle, budget threshold, and completion events reach the developer system.
Scoped BYOK records with pause, rotate, revoke, and audit trails
Provider keys are treated as controlled infrastructure, not casual widget settings.
Reference Build
YAKKL® Wallet™ is the first serious proving ground.
Wallet gives Ari real constraints: money movement, risk review, recovery, portfolio intelligence, security summaries, and surfaces where the AI must respect permissions instead of free-floating over the app.
Apps built with YAKKL® Meridian™ can carry Ari as a native assistant surface. The build environment defines the plugin shape, the app exposes allowed slots, Ari creates the add-on package, and secure pickup moves the approved artifact to the edge for the host app to load.