Meet Dus, your AI engineering team. From your first idea to production, Dus plans, writes, reviews, tests, deploys and looks after your software. Work with your team, choose your AI models, and stay in control of every important decision.
Deployed to your server over HTTPS. The previous release is kept, so rollback is one step.
The real Duscode app, with a sample project.
The kind of work Dus takes on for a project, from a first feature to the routine that keeps it healthy. Each one ends in something you can check.
4 of 4 requirements proven in a browser
HTTPS, health check, one-step rollback
Checked on the head and on the merge result
Two options, costs and undo for each
Its own budget and a record of each run
Cause found, proven with a test, then fixed
Dus carries a task from your sentence to software running on your server, and stays with it afterwards. Two moments are always yours: the calls that cost money or can’t be undone, and the first time anything goes live.
Reads the project and writes a plan, with a cost estimate first.
plan · route · estimateMakes the technical calls and explains them. Asks you about money, publishing and anything permanent.
You decideWrites the code in your project’s own framework, a reason on every change.
diffs · reasonsRuns your typecheck and tests, and checks pages in a real browser.
Proof of Work · SealChecks the change and the merge result on your machine, your server or your existing CI.
check receiptsDeploys to your server over HTTPS, checks it’s healthy and keeps a one-step rollback.
First deploy: you decideChecks your live app, notices what breaks, fixes what you’ve allowed and asks about the rest.
health · incidentsSomething breaks? Watch opens an incident, Dus finds the cause, and the fix goes round the same loop: reasoned, decided, built, verified, merged, live.
Five things in the app make the work easy to trust at a glance. Each one is built from what actually ran, never from what the model says about itself.
Every technical decision, with the evidence it rests on. Anything unproven is marked as an assumption.
∴ DusMigrate in two steps; drop the old column after the report has moved.
Decisions that are yours arrive as one card: what it costs, what it means, how to undo it, and Dus’s pick.
Take card payments in the shop?
Each step shows Reasoned, Decided, Built. Built turns green only when a check ran after the last change.
The task’s cost as a track: spent, reserved for the call in flight, and the forecast to finish, before your limit.
£0.31 spent£0.07 reserved≈ £0.24 to finishlimit £1.00
The outcome, from the proof record only: sealed, sealed with gaps named, or not sealed and why.
The chat in the middle, the plan, changes and checks on the right, and everything else one click away. These are real screenshots. The product overview
Each task ends with what works now and how it was checked, then asks if it’s what you wanted.
Money, publishing, credentials and anything permanent come as one card in plain words. Technical calls stay with Dus.
A denser layout with the editor beside the chat. Every change opens as a diff you can comment on or revert.
Each part of your live system with its reading, every incident with its stage, and the calls that need you.
The same app on a small screen, with Today, Calls, Tasks and Watch in a tab bar, so a decision never waits for your desk.
Six duties per project. Switch on what Dus should own; each duty ends in something you can check.
Plans the work, writes the code in your project’s own framework, and runs your tests.
Ends in: a Proof of WorkCommits, opens the pull request and checks each change before it merges: on your machine, your server or your existing CI.
Ends in: a merged changePuts your app on your own server, checks it’s healthy and keeps a one-step rollback. The first deploy is always your call.
Ends in: a live addressChecks your live systems, notices when something breaks, fixes what you’ve allowed and asks about the rest.
Ends in: a resolved incidentRuns checks, reports and clean-ups on a schedule you set, each with its own budget.
Ends in: a record of each runFinds the cause, proves it with a test, fixes it and shows you the evidence.
Ends in: a passing testWatching while your computer is off is coming soon. Dus asks before anything that costs money, goes public or can’t be undone, and tells you plainly when something didn’t work. Which parts are shipped, in beta or coming, from the evidence: Capabilities
Duscode runs on your computer, next to your code. Nothing about your setup is locked in.
Each task starts on the cheapest model that can do it and moves up only when checks fail. Or pin one.
Your app runs on a server you own, over SSH, with HTTPS and a rollback kept.
Approvals, budgets and a vault, so Dus works fast without working unchecked.
The same Dus and the same projects, wherever you like to work.
For Windows and Linux. It updates itself, and every file is signed with Duscode’s release key.
DownloadRun duscode in a project on macOS, Linux or WSL, and work in your browser.
Pro, Max and Team include AI usage every month, and Dus routes each task to the cheapest model that can do it, so it goes further. Or bring your own provider keys for less.
Prices exclude VAT. Launch prices, which may change as we learn from early users. Top up from £10 when you need more.
We’re letting people in small groups, so each one gets proper attention while Dus learns real work. Tell us what you’re building.
Dus is the reasoning engine inside Duscode: it plans, builds, tests, ships and watches software, and explains its decisions. Dus reasons and proposes; you approve what matters. That's the promise: intelligent autonomy with human oversight.
The name is inspired by the Dutch word dus, "thus, so, therefore", which we read as reasoning that leads to action.
No. Dus makes the technical calls and asks you only the owner’s ones, in plain words, with a recommendation. If you do write code, the Engineer view puts the editor beside the chat. More in For founders.
On your own server. Dus deploys over SSH, serves it over HTTPS, checks it’s healthy and keeps the previous release for a one-step rollback. The first deploy always waits for your go-ahead.
You use an API key from your AI provider, such as Anthropic or OpenAI. Duscode calls the provider directly from your machine with that key, and the provider bills you at its own prices. Duscode adds no markup to that and never sees your bill. On Pro, Max and Team you don't need a key: usage comes with the plan.
Duscode ships with presets for Anthropic, OpenAI, Gemini, DeepSeek, xAI, Mistral, Groq, OpenRouter, Together, Fireworks, Cerebras, Moonshot and Qwen, plus local models through Ollama or LM Studio and any OpenAI-compatible endpoint you configure. Routing chooses among the ones you have keys for.
Only in the requests Dus makes to an AI model. With your own key, they go straight to the provider you choose. On Duscode credits, they pass through Duscode Cloud on the way, and we keep what each call cost, not what it said. Your keys go only to the provider they belong to. The provider's data policy applies; see Security.
Yes. Free costs nothing and keeps the verification gates and budgets, because they protect your code and your money. Pro adds automatic routing, helper agents, the savings dashboard and the VS Code extension.
Dus leads. You decide.