About PlutusDoc
The signature was never the hard part.The work around it was.
PlutusDoc is an agent operated document workspace. This page is the part of the story that does not fit on a landing page: why we built it, the beliefs it is built around, and the god we named the agent after.
Where this started
Everyone was adding chat boxes. We started over instead.
By the time we started, signing was a solved problem and had been for a decade. Type your name, click a box, done. Yet agreements still crawled. Drafts sat unwritten because nobody had an afternoon. Contracts went out and nobody noticed they were never opened. Reminders lived in someone's head until they left it.
Then agents arrived, and the category responded by bolting a chat box onto the filing cabinet. The assistant could summarize the contract and answer questions about it, and then it handed the work straight back. Every real step was still a form, and still yours.
We thought the missing piece was not a way to talk about the work but a way to hand it over, with rules. So we wrote the rules first. Every capability in the product became a governed action with a scope, an approval gate where it matters, and a place in the audit trail. Only then did we add the agent, into a workspace where everything it could do was already accounted for.
- governed actions in one shared registry
- 19governed actions in one shared registry
- of them stop and wait for your approval
- 7of them stop and wait for your approval
- OAuth scopes, granted one at a time
- 10OAuth scopes, granted one at a time
- audit trail behind people and agents alike
- 1audit trail behind people and agents alike
What we believe
Four beliefs, each one checkable.
Most company values are adjectives on a wall. Ours are decisions, and every one of them left a mark on the product that you can go and find.
Work beats advice.
An assistant that can only talk is a search box with manners. If a task is worth building an agent for, it is worth giving that agent the actual tool, not a script about the tool.
In the product
Plutus holds the same nineteen actions a person does, and runs them as work rather than suggestions.
Delegation is not surrender.
Handing work to software should never quietly hand over judgement. The moments that commit you, creating, editing, sending, are exactly the moments software should stop and look at you.
In the product
Seven of the nineteen actions cannot finish without your explicit approval.
Open at the boundary.
Your agent should not have to live in our tab to be useful. A workspace built for agents has to welcome the ones you already run, on their terms and your authority.
In the product
An MCP server and a REST API reach the same action registry as Plutus, behind OAuth 2.1 rather than pasted keys.
Provable beats plausible.
Automation you cannot audit is a liability with a nicer interface. If you cannot show who did what, on whose authority, months later, the work was never really delegated. It was abandoned.
In the product
Every action, human or agent, lands in the same timestamped trail with the address and device behind it.
The name
Blind on purpose.
Plutus was the Greek god of wealth, and the detail everyone forgets is our favorite: Zeus blinded him so that he would deal out fortune without checking whose side anyone was on.
That felt like the right patron for an agent that moves agreements around all day. The same rules for every document, the same gates for every request, whoever is asking, and no exception it can be charmed into. We built the blindness in as scopes and approval gates, then named the agent after the idea.
The Doc part is because it works on documents. Naming things has two halves, and we spent our imagination on the first one.
The road here
Built in the order trust had to be earned.
The tempting order is agent first, accountability later, demo on day one. We went the other way. It took longer, and that was the point.
An editor worth trusting
Fields that stay where they were put, placeholders that fill once and land everywhere, and finished PDFs flattened so nothing floats above the page.
A record worth citing
One private link per recipient, every view and download on file, and reminders that go out on a schedule instead of on memory.
The action layer
Every capability rebuilt as a governed tool. Nineteen actions, ten scopes, seven approval gates, one registry serving all of it.
The agents
Plutus in the panel, your clients over MCP, your systems over REST. Three ways into the building, one set of rules inside it.
The rest of the story is the product.
Seven days of everything, with no card. Ask Plutus for a draft, connect a client you already run, then read the trail both of them left. And if you would rather talk to a person, we read every note sent to dev@plutusdoc.com.