DOSIA × ByteSpike — one team, two products, one workflow
DOSIA is the desktop client. ByteSpike is the multi-provider gateway. They ship separately on purpose — but the combination is the shape our team actually wanted: one account, one key, one bill, every frontier model.
Customers occasionally ask whether DOSIA and ByteSpike are the same product. Same team, but no — they are two distinct products that happen to compose. DOSIA is a macOS client that hosts agent workflows; ByteSpike is a gateway that puts every frontier model behind one Anthropic-compatible API. Either works on its own. Combined, they cover the loop we kept rebuilding for ourselves.
DOSIA — the client
DOSIA holds the opinions about how a power user wants to talk to models: a native macOS surface, the five-layer file system that lets a Session/Personal/Project/Role/Enterprise scope live side by side, a skill marketplace for repeatable workflows, and a Provider abstraction that's intentionally not vendor-locked. Plug any compliant backend into the Provider slot and DOSIA keeps working.
ByteSpike — the backend
ByteSpike holds the opinions about how a gateway should behave: one Anthropic-style key for every supported provider, two protocols (Messages and Chat Completions) on the same base URL, failures don't bill, every response carries an estimated_credits header. Multimodal endpoints — image, video, embeddings, rerank — share the same key. The Console gives orgs wallet-level controls, per-member quotas, and sub-key derivation for individual deployments.
Why we keep them separate
- Different release cadences — DOSIA ships fortnightly desktop builds; ByteSpike pushes gateway changes the moment an upstream provider's protocol shifts. Bundling them would force one product to drag the other.
- Different SLAs — the gateway has uptime obligations that a desktop client doesn't. Coupling the deploy pipelines would mean every DOSIA bugfix risks the API-tier customers, and every gateway maintenance window would lock DOSIA users out.
- Different audiences — DOSIA is for the operator who wants the chat surface; ByteSpike is for the engineer wiring an agent into a backend, a CI pipeline, or another client (Cline, Continue, Cursor). One product per audience keeps the docs honest.
Why the combination is better than either alone
When the same account funds both, three frictions disappear at once. The model picker in DOSIA hydrates from ByteSpike's /v1/models endpoint — adding a new upstream model to ByteSpike makes it show up in DOSIA on the next prompt, no client release needed. Credit estimates flow from gateway to client: DOSIA's token-usage strip surfaces ByteSpike's per-request cost in the same status row that holds latency, so the human at the keyboard sees the price as it lands. And one bill arrives at month-end — no reconciling five provider invoices against your usage log.
“The right way to ship a client and a gateway as one workflow is to let each ship at its own cadence, but design the touchpoints so the user experiences them as one thing.”
The composite user profile
The customer we keep meeting at every demo: a senior engineer or a two-person team that wants to evaluate Claude, GPT-5, Gemini, DeepSeek, and Kimi against the same prompt without keeping five SDK readmes open. They don't want a chat tab — they have DOSIA. They don't want to negotiate five contracts — they have ByteSpike. They want one credit balance and a model picker that always has the latest version. That's the customer we built both products for.
What's coming next at the seam
All three of the items below are tracked roadmap, not committed launch dates — figure on 2026 Q3 as the realistic window, with the SSO piece closest to landing.
- Sign in with ByteSpike — one OAuth click from DOSIA's first-run wizard provisions the API key and wires the provider automatically. No more copy-paste from the Console.
- MCP integration in DOSIA — image-tools / video-tools / text-writing-tools load against the user's ByteSpike permissions, surfacing image / video / external-LLM endpoints as native main-brain tools rather than a separate panel.
- Skill plugin v2 with gateway awareness — skills running inside DOSIA can request ByteSpike-side feature flags (caching, fallback chain, retry budget) without leaving the skill manifest.
Both products are free to start: DOSIA at bytespike.ai/dosia, ByteSpike at console.bytespike.ai/sign-up. The composite story works best when you try them together — but pick whichever side of the seam matches what you're already missing.