Business docs | BIZ-3

Yui | revenue models and mission principles

Draft 1, Sep 24 2026. Card BIZ-3. Public, like the rest of the project (Chris, Sep 24: "everything can be totally visible").

Chris, in the pitch (rec 366): "The goal is that you download this app, you put in your credit card and you're off to the races with a multi-agent in your life." And: "Image generation is in no way free. So people have to pay for it." And: "In all phase ones, we're plugging into outside services and then slowly but surely we bring them in house."

The short version

Part 1 | Mission principles

These are rules, not slogans. Each one says what it forbids.

  1. The open core is free forever. Anyone who brings their own agent (Hermes, OpenClaw, any MCP agent) and their own keys gets the full app: every preset, every screen, per-agent themes, voice, full screen. We never move a free feature behind a paywall later. Apple's rule 3.1.2(a) already forbids taking away paid-for features; we hold ourselves to the same rule for free ones.
  2. We charge only where we carry a cost. Hosted model calls, image and video generation, voice, hosting, human support. If a feature costs us nothing to serve, it is free.
  3. No dark patterns. No ads. No fake scarcity or countdown timers on offers. No streak guilt or engagement-bait notifications. No pre-checked upsells. Cancel in two taps inside the app, no survey wall. Price per unit shown before every charge. Credits never expire (Apple requires this for IAP anyway, and we would do it regardless).
  4. Privacy by default, on device first. Agent tables, keys (Keychain) and history live on the phone. Sync is opt-in and encrypted. We never sell data, never train on user data, never share it with advertisers. The privacy page lists every table we hold, as it does today.
  5. Fair pricing. Credit prices show cost plus a published margin. BYO keys keep working on every paid tier, so nobody is forced to buy our credits. Unused months get handled the Kagi way where possible (credited back, not kept).
  6. Accessibility is never a paid feature. Dynamic Type, VoiceOver, high contrast, voice in and text out, big tap targets: free on every tier.
  7. Discounts for people with less. Students, teachers and nonprofits get a standing discount (Obsidian gives 40%).
  8. The glad-a-month-later test. Before any paid feature ships, ask: would a user be glad they paid for this a month later? If the honest answer is "they forgot to cancel", it does not ship.

Part 2 | The ground rules Apple sets

These shape every model below.

Part 3 | The models

Each model: what it is, comparables with sources, rough numbers, pros, cons, what it needs built, and when.

Model A | Hosted agents subscription ("Yui Plus")

What: for people with no agent. Download, subscribe, and Yui runs an agent for you (roadmap Phase 4 "hosted default agent", plus starter agents from the onboarding interview). This is the "put in your credit card and go" version.

Comparables:

Cost of goods (my estimate, not sourced): Anthropic list prices: Haiku 4.5 $1 in / $5 out per million tokens, Sonnet 5 $2 / $10, Opus 5.5 $4 / $20; cached input reads cost about a tenth of the input price. A typical agent turn with the Yui skill and recent history is roughly 8k input tokens (85% cached) and 400 output tokens.

Rough price to test: $11.99 a month or $99 a year, with a generous included allowance shown in plain numbers (for example "about 600 conversations a month"), then optional top-up credits. At 15% Apple fee, $11.99 nets about $10.19. A normal user leaves roughly half as margin; a heavy user is carried by top-ups, not by throttling in silence.

Pros: the largest market (people with no agent). Predictable revenue. Matches Chris's end-state vision. Cons: the only model with real inference risk. Competes on price with $8 to $20 general chatbots that have far bigger budgets. Needs onboarding good enough that a non-technical person gets value in the first five minutes. Needs built: hosted agent runtime on the relay (Phase 4), onboarding interview and starter agents (Phase 4), accounts (done, YUI-6), usage metering per user, StoreKit 2 subscriptions and receipt validation, a plain usage meter screen, spend caps. When: Phase 4 to 6 (Feb to Jun 2027). Price only after the beta measures real per-user cost.

Model B | Usage credits for images, voice and model calls

What: consumable IAP credit packs. Spend them on image generation, video, premium voice, and model calls for people without their own keys. Chris named image generation as the easiest first step.

Comparables:

Rough numbers (estimate): a $4.99 pack nets $4.24 after the 15% fee. At fal's $0.025 to $0.04 an image, 80 images cost us $2 to $3.20, leaving $1 to $2.20 for relay, storage and margin. Publish the rate: "1 image = 5 credits, a $4.99 pack = 400 credits."

Pros: simplest thing to sell. Pay for what you use, no subscription guilt. Revenue tracks cost exactly, so no inference risk. Directly answers Chris's "image generation is in no way free." Cons: Apple takes 15% of a thin margin. Credits cannot expire, so unused balances are a permanent liability on the books. Low revenue per user on its own. Needs built: key vault and BYO image keys first (Phase 3), the media pipeline (YUI-21), StoreKit consumables, a credit ledger in yui_ tables with restore, per-action price shown before spending, spend cap. When: Phase 3 to 4 (Jan to Feb 2027). First paid SKU.

Model C | Pro presets and themes

What: paid cosmetic packs: designer themes, icon sets, special preset styles.

Comparables:

Rough numbers: small. $1.99 to $4.99 one-time packs, or bundled into Plus. Expect this to cover design time, not fund the company.

Pros: zero marginal cost. Easy to understand. Cons: conflicts with the product. Per-agent looks (YUI-20) and "ask an agent to restyle the app" are core features, so the theming engine and agent-made themes must stay free. Selling looks the agent could generate for free feels cheap and fails the glad-a-month-later test. Recommendation: skip selling themes directly. Offer an Obsidian-style supporter pack instead (one-time $25, early builds, a supporter badge, a few designer themes as a thank-you). Honest, and it doubles as a way for BYO users to fund the open core. Needs built: runtime theme tokens (YUI-20, Phase 2), non-consumable IAP. When: supporter pack any time after public launch. Low priority.

Model D | Team and business tier with connectors

What: agents that run a business, not just a workout. Shared agents for a team, connectors (HubSpot, Google Calendar, Gmail) via MCP and OAuth, shared tables (CRM), admin controls, audit log.

Comparables:

Rough price to test: $15 to $20 a seat a month, minimum 3 seats. B2B sales to organizations may qualify for Apple's enterprise-services exception (guideline 3.1.3(c)) and bill outside IAP. Verify before relying on it.

Pros: highest revenue per user, lowest churn. Fits PostScarcity AI's client work: the same agents Chris builds for clients could ship to them inside Yui. Cons: the heaviest build (admin, roles, shared data, security review, SSO later). Connectors mean holding third-party OAuth tokens, which raises the privacy stakes. It pulls the product toward enterprise and away from "genuinely help people." Needs built: connector library v0 (Phase 4), shared encrypted sync (Phase 3, currently optional), roles and admin, audit log, org billing. When: after public launch (H2 2027). Pilot it earlier with one or two PSAI clients as a paid setup, no product tier yet.

Model E | Paid hosting and support for other people's agents (relay connector)

What: Phase 5 opens Yui to other people's Hermes installs via Hermes's relay connector contract (hermes gateway enroll). Two things can be sold on top:

  1. Managed hosting: Yui runs your Hermes agent for you, always on, no Mac mini needed.
  2. Setup and support: paid onboarding for people who want their agents built and wired up by someone who knows how.

The relay connection for a user's own self-hosted agent stays free (principle 1).

Comparables:

Rough price to test: managed Hermes hosting at $15 to $25 a month, models on the user's own key (or bundled with Plus). Setup packages priced as PostScarcity AI services, not app SKUs.

Pros: the Nabu Casa model is the closest match to Yui's values: the paid service funds the free core, and users pay because it is convenient, not because they are locked in. Serves the Hermes and OpenClaw crowd, the stated early adopters. Cons: hosting other people's agents means running their code and tools: security isolation, abuse handling and support load are real costs. Small market until agents go mainstream. Needs built: multi-tenant relay (Phase 5), connector enrollment, isolated agent runtime (Cloudflare Workers + Durable Objects or containers), monitoring, a status page. When: Phase 5 (Mar 2027) for the free relay; managed hosting after the beta shows demand.

Model F | Sponsorships and grants for the open-source project

What: money that funds the open core directly.

Comparables and facts:

Pros: aligned with the mission, no product compromise, grants are non-dilutive. Cons: small and unpredictable. Grants take weeks of writing and reporting. Needs the code to actually be public under an OSI license first (see open questions). Needs built: public repos with a clear license, a contributor guide, a funding page on yuigui.com. When: now. The NLnet deadline is six weeks out.

Part 4 | Features each model needs, by roadmap phase

Part 5 | Recommended sequence

  1. Now (Phase 0 to 2): stay free, fund the core. Decide the license and which repos go public. Open GitHub Sponsors. Apply to NLnet by Nov 3 2026 for the Yui Lines spec, conformance suite and relay protocol (the reusable, public-good part). Enroll in Apple's Small Business Program.
  2. Phase 3 to 4: image credits first. The smallest honest paid thing. Tests willingness to pay with zero inference risk, and Chris already named it.
  3. Phase 4 to 6: Yui Plus. Hosted agents with an included allowance. Priced from beta data, not from this document.
  4. Phase 5 onward: managed hosting for other people's agents, the Nabu Casa play. Paid convenience that funds the free core.
  5. After launch: team tier with connectors. Pilot with one or two PSAI clients first.
  6. Optional: supporter pack instead of selling themes.

Why this order: each step funds the next and none of them risks the principles. Credits come before the subscription because they carry no inference risk. The subscription comes before teams because a team tier built before the consumer product works is enterprise software with no product under it.

Part 6 | Risks

Open questions for Chris

  1. Open source: which repos go public, and which license? Recommendation: Apache-2.0 for the app, the Yui Lines spec and the Hermes plugin. OSI-approved (not n8n-style fair-code), because grants and community trust depend on it.
  2. Roadmap question 5 still stands: product to sell, or personal tool that might become one? This document assumes a product.
  3. NLnet application by Nov 3 2026: yes or no? (Outbound, needs your sign-off before anything is sent.)
  4. OK to publish a short, public version of the eight principles on yuigui.com?

Sources

All accessed Sep 24 2026 unless dated. Items marked secondary come from third-party pricing roundups because the vendor page blocked automated fetches; verify before quoting publicly.

Try Yui, or help build it

Get the alpha

The MVP is done and Yui is in alpha, open to anyone with an iPhone on iOS 26. Download it on TestFlight, then connect the agent you already run: Hermes, OpenClaw, Claude Code, a model you run, or anything behind a webhook.

Star it on GitHub

Yui is open source under Apache 2.0. Star the repo, open an issue, or send a pull request.

Lend your agent

Spare tokens on Claude or ChatGPT Codex? Your agent can pick a card off our backlog and open a pull request. Yui@home, like SETI@home.

Want a hand getting in?

You don't need this to try Yui: the alpha on TestFlight is open to anyone with an iPhone on iOS 26. Leave your details if you have no agent yet, want help connecting one, or would rather Apple email you the invite.

  1. Yui emails you a link to confirm your address.
  2. We read your request, and reach out if you asked for help.
  3. Apple emails you a TestFlight invite.
  4. Open it on your iPhone, install Yui, and sign in with Apple.

We use this only to get you into Yui. Privacy.