You don’t need to code. You need to decide.
Describe what you want in plain words. Dus does the engineering: it makes the technical decisions, checks its own work and brings you only the decisions that are truly yours, with its recommendation.
- Plain words in
- Choose “I describe what I want” the first time you open Duscode. You say what the app should do; Dus picks the libraries, the structure and the steps.
- Plain words out
- Every task ends with what works now and how it was checked, then asks whether it is what you wanted: Looks good or Change something.
- Only your calls reach you
- Money, publishing, real people, real data, legal terms and accounts. Each comes as one card: what happens if you say yes or no, the cost, whether it can be undone, and Dus’s pick.
- Undo is always there
- Technical steps are recorded, and every task ends with Undo everything from this task, which puts every file back as it was.
You see the cost before it is spent.
Each task shows an estimate first and its cost as it runs, in pounds. Limits per task and per day are on every plan, Free included.
Budgets that stop
Set what a task and a day may cost. Dus finishes the step it is on and stops at the limit, then asks whether to raise it.
The right model per task
Each task goes to a model that can do it at the lowest cost, and the app names the model it used.
Usage included
Paid plans include AI usage, shown in pounds, with a warning before you run out. Or bring your own provider keys. Pricing
What a first week can look like.
An example of the path, not a promise of timing. Each step ends in something you can check.
Describe it
“A small shop for my candles, with card payments and an order list for me.” Dus asks which architecture to build with and creates the project from that stack’s official starter.
Answer the owner’s calls
“Take card payments in the shop?” arrives as one card, with what it costs and how to undo it. Dus keeps building the rest while you decide, when the plan allows.
See it working
Dus runs the checks and opens the pages in a browser. The task’s Proof of Work lists what ran and what passed, and what wasn’t checked.
Put it online
On a server you own. The first deploy waits for your go-ahead, and the previous release is kept for a one-step rollback. Hosting and domains
Keep it healthy
While Duscode is running, Watch checks the live app and asks you when something needs a decision. Scheduled jobs and a daily brief keep you up to date: Keep improving
Fair questions.
Will it get everything right?
No. Software fails sometimes, and so does Dus. What we promise is that it tells you plainly: the proof says Failed or Not checked when that is the truth, and a failed fix is never retried blindly.
Do I own the code?
Yes. It lives in a folder on your computer, in your own git repository, in your project’s own framework, so any engineer can pick it up later.
What if I want to look at the code?
Switch to the Engineer view at any time. It puts the editor and every diff beside the chat.
Is it ready for my business?
Duscode is in private beta. Which parts are ready, in beta or coming is on Capabilities, taken from the evidence.