DDOX OS.

DDOX OS · ddox.ai

One workspace.
Every AI you bring.

Your AI, but it only bills you when it's actually thinking.

DDOX OS is a chat and code workspace built around a simple refusal: your work should not be held hostage by whichever model you started with. Connect the providers and subscriptions you already have, switch between them in the middle of a conversation, and the thread, the project, and the code come with you. Underneath, a resident harness — DoxBot — holds the context, does the carrying, and calls in your big model only for the moments that are actually thinking.

Try the live sample See everything it does
DoxBot — the DDOX OS resident: a glossy dark-blue orb with cyan arch eyes and a waveform line

DoxBot, the resident at the center of DDOX OS. One orb, every surface — never a stock face, never a different character.

The founding feature

Switch providers. Keep your place.

Start a conversation with one provider, switch to another for the follow-up — the follow-up still knows what came before. Nothing gets re-explained. Nothing starts over. Where a provider's own terms allow it, you can bring your existing subscription; where they don't, DDOX OS says so plainly and offers the sanctioned route instead.

DDOX OS — sample workspace Scripted sample — not the product itself
Provider

⟳ Same conversation · same project · nothing re-explained

YouWrite a small rate limiter for our sign-in form.
DDOX OS · OpenRouterHere is a first pass — five attempts in fifteen minutes, keyed to the account:
function rateLimit(attempts, email) { const key = `signin:${email}`; if (attempts.get(key, 15 * 60) >= 5) return 'locked'; attempts.add(key); return 'allowed'; }

The providers above are real routes in DDOX OS — hundreds of models through OpenRouter and DeepInfra, or models running on your own hardware. In the product, everything runs under your own accounts, subscriptions, keys, and licences.

The Hybrid system

A resident carries the context. Your model does the thinking.

Most of a conversation isn't thinking — it's carrying: remembering, organising, waiting, checking. DDOX OS's resident seat holds all of that inside the harness, so your frontier model is only billed for the moments it earns. A verifier seat judges Hybrid answers before they land, and every response shows which seat did the work — the receipt behind the promise.

Resident seat

An always-on model of your choosing holds the resident role — identity, memory, and context — for little-to-nothing while idle. The big model doesn't pay rent on your conversation.

Verifier judging

A second seat checks Hybrid answers before they reach you, so the cheap path never becomes the sloppy path.

Spend attribution

Every answer carries its attribution: which seat did the work, and where the spend went. Tunable in Settings, visible by default.

answer · carried by the resident — judged by the verifier — thinking by your model

The receipt every Hybrid answer carries: which seat did the work.

How Hybrid works →

DoxBot

Not a chatbot bolted on. A crew, with a coordinator.

Arm DoxBot from the composer and a mode — Assist, Swarm, or Dox — dispatches a real crew through the execution runtime: digest-bound plans, per-seat budgets, a heartbeat journal, and DoxBot coordinating up to twelve bots at once. DoxBot stays with you after the app closes, travels to where the work is, and only interrupts when he genuinely needs your call — which lands as a real decision you can approve or deny, not a notification to dismiss.

A DoxBot swarm — a group of dark-blue orbs with cyan rings and role glyphs

A crew in formation: up to twelve bots, with DoxBot coordinating.

Meet DoxBot →

Live sample

Don't take our word for it. Click through it.

A working miniature of DDOX OS runs right in your browser: the chat page answers, the Activity feed moves, and Swarm Center dispatches its twelve-bot crew — while the rest of the navigation sits in place, present but closed, exactly as it does here. It is a sample, labelled like one; the full surface is the product.

Open the live sample

The discipline layer

A harness that verifies itself — with receipts.

DDOX OS runs its work through a supervision harness: every supervised item carries evidence, stuck work escalates on a ladder instead of vanishing, and terminal states are verified, never assumed. The harness's current release closed its perfection programme 15 of 15:

292
assertions in the full battery, zero regressions
33 / 33
test groups passing at install
14 / 14
planted faults caught by mutation testing
15 / 15
perfection criteria closed for harness v3.4

From the harness perfection record, 2026-11-08. Permission modes (Observe / Assist / Act / Full) are enforced by one structural policy gate every tool call passes before it executes — safety that is architectural, not procedural.

Editions

Base opens first. Hybrid is the full system.

DDOX OS Base is the focused workspace — chat, code, and provider switching with persistent context — at $29.99, one time, all updates included. DDOX OS Hybrid adds the resident system at $9.99 or $19.99 a month. Neither is on sale yet: checkout opens when the launch gates close, and the list below hears first. No refunds — all sales are final — and that will be stated again at checkout, before any purchase.

Editions and pricing →

Mailing list

Be there when DDOX OS opens.

One email when DDOX OS opens. Nothing else, no noise.