The operator machine hosts the control surface and durable state.
Provider lanes
One runtime across local models, subscriptions, and APIs.
Heiwa does not pretend every provider is identical. It gives operators one routing surface across three honest lanes: local inference, OAuth-backed provider CLIs, and API-key providers.
Current framing
Provider surface
Providers still own auth and inference internals. Heiwa owns operator routing, evidence, session control, and local coherence.
| Provider | Lane | What the operator brings | Where inference runs | Heiwa's role |
|---|---|---|---|---|
| Ollama | Local | Installed local runtime and local models | On the operator machine | Discovery, routing, receipts, and operator control |
| Claude Code | OAuth CLI | Claude Max or related Anthropic account in provider CLI | Provider-managed inference via local CLI | Runtime orchestration around the provider-owned tool |
| Codex | OAuth CLI | ChatGPT Plus or OpenAI account in provider CLI | Provider-managed inference via local CLI | Unified routing and receipts with the rest of the runtime |
| Gemini CLI | OAuth CLI | Google AI Pro account in provider CLI | Provider-managed inference via local CLI | Shared operator surface across Google and non-Google lanes |
| Antigravity | OAuth CLI | Provider-owned Google lane through local CLI | Provider-managed inference via local CLI | Additional routed capacity under one local runtime |
| OpenAI API | API key | API key | Provider API | Route selection, operator context, approval, and evidence |
| Anthropic API | API key | API key | Provider API | Same runtime surface without provider lock-in |
| Google AI API | API key | API key | Provider API | Bring API access into the same operator flow as local and CLI lanes |
| OpenRouter | API key | API key | Remote gateway | Optional remote lane, not the product center of gravity |
Honesty boundary
Heiwa is not fake parity.
Discovery, routing metadata, and install support do not imply equal execution depth across every provider surface. Heiwa should say which lanes are local, which are provider CLI wrappers, and which are API-key integrations.
Heiwa wraps and routes. It does not claim ownership of provider internals.