Ducens SHEET 07 / 08
Ducens · Sheet 07 / 08 The name

Ducens is Latin for leading.

DŪCĒNS · PRESENT PARTICIPLE OF DŪCŌ · TO LEAD, TO GUIDE

The mark is a green circle ahead of a grey robot. Green is the living, human thing. Grey is the machine: neutral, capable, behind. The order is the whole point.

Ducens exists so you lead AI, and it never leads you.

Why

07·B

I built the first version of Ducens for myself. I saw the hype around agentic operating systems and wanted one, so I started building it, just to keep my own stack straight. At first it was only supposed to help me finish another project.

But building it meant learning everything at once, and everything I was learning came from somewhere else: a video, a thread, a doc, someone's post. So I built a pipeline that captured all of it automatically, every useful thing turned into a note, so nothing would get lost. It worked. Then I drowned in the notes. That is how hard it is to keep an overview in this space: the system I built to stop myself drowning became the next thing I was drowning in.

Then I noticed something. The people around me who had started with AI before I did had mostly stopped. They got stuck on Replit, never understood what half their extensions actually did, gave up somewhere before automation. Not because they were not capable. Because nobody makes this legible. Every answer lives in a different tab, every tool wants full access, and no one tells you where anything is stored. And that is the ones who started. Most people never do, because without a lot of time to spend, learning this is close to impossible.

Then there are the people who did learn it. Right now that knowledge is an edge, and the edge gets sold. I have watched people charge a company ten thousand euros for a website they built in half an hour, and small businesses hand over their last paycheck for a site with no backend behind it. That gap is not talent. It is knowing your stack. The people paying could have done it themselves, if anyone had shown them how.

You have probably seen a version of this before. People left behind by the internet, by a new Windows, by an iOS update, not because they were incapable, but because it moved faster than anyone was willing to explain it. It is happening again, right now, faster. Some days it feels like it could be us.

So Ducens became the thing I needed on day one: one surface where you manage your whole stack and learn how to build one, which extensions are worth it, which providers are worth it, what any of it actually does, with you staying the one who leads it. That is why Learn exists, taught properly, in small pieces, without assuming you already know the words. That is why Loop exists, because the most powerful things in AI are the hardest to get started with, and that is backwards.

I want my parents to have this. I want my friends to have it. I would rather people run AI than the other way around.

PAUL · BUILDING DUCENS

What Ducens will not do

CONSTRAINTS, PUBLISHED07·C
N-01

Never bundles compute.

Your keys, your bill, no margin taken in the middle.

N-02

Never sells or brokers your data.

N-03

Never cripples trust features to sell an upgrade.

Receipts, previews and approvals work on every tier, forever. Limits are capacity limits, never safety or honesty limits.

N-04

Never runs an action you have not seen and approved.

N-05

Never ships something that does not work to hit a date.

If that is the deal you want, the waitlist is Sheet 08. Join it.

Next: Waitlist →