One twin per person.
One workspace.

Memory, tools and scheduled work for every person. One place to manage it all.

Set up the team. Not every twin.

Shared tools and skills, written once. A twin of their own for each person.

Shared layerWritten once by anyone. Available to every twin.
12 skills8 MCP servers6 CLIs1 set of rules
Maya's twinFinance
Inherits the shared layer
+ Maya's own tools
Own VM · own credentials · sealed off
Raj's twinEngineering
Inherits the shared layer
+ Raj's own tools
Own VM · own credentials · sealed off
Wei's twinSupport
Inherits the shared layer
+ Wei's own tools
Own VM · own credentials · sealed off

Delegate a task. Follow the work.

It opens the tools, does the work, and stops when a step needs a person.

Maya

Reconcile last week's Stripe charges against the books, and post what doesn't match to #finance.

Pulled 1,204 charges from Stripe
Matched them against the books in Postgres · 3 don't match
Posted the summary to #finance
!Refund of $840 to Northwind · held, waiting on Kim
Maya's twin · in its own sandbox · no credentials inside

Your tools. More than one way to use them.

MCP tools, CLIs, APIs or scripts. Every route passes the same gateway and the same rules.

MCP tool calls

Connected tools and services

CLI commands

Commands available in the twin's environment

curl and raw HTTP

A shell and a URL is still a request

The code the twin writes

Scripts written to complete a task

A twinin its sandbox
MCP tool callsCLI commandscurl and raw HTTPThe code the twin writes
Gatewaysame keys · same rules · same log

An MCP gateway only sees tool calls. Dittwo sits at the network layer, so all four routes pass through the same gateway.

Rules, not suggestions.

Routine work continues. The actions you choose pause for approval. Enforced at the network layer, outside the model.

Not allowed

Your twin can't touch what's off limits

Deleting a repo, sending a payment, wiping a customer record. You decide what a twin never touches, and no matter how it's prompted, the answer is always no.

Tried to delete a repository → stopped
Slowed down

Your twin can't run away with itself

A twin that starts repeating itself or working far faster than a person ever would gets slowed down before it can do real damage.

Sent 200 messages in a minute → paused
Ask first

Your twin can't skip the human on big moves

The twin does the work up front, then anything sensitive pauses and asks. It waits until someone on your team says go.

About to email a customer → waiting on you
Their access only

Your twin can't leave its lane

A twin only reaches the tools and accounts its person already has. Support's twin can't wander into billing, and nobody shares a password.

Support twin reaching for payroll → blocked

Keys stay in the vault.

The gateway adds credentials to outbound requests. They never enter the twin's environment.

.env · what the twin sees7 secrets exposed
OPENAI_API_KEY=sk-proj-Xh4mQ2████████f8Kwdittwo-managed ✓
STRIPE_SECRET_KEY=sk_live_51Hx8m████████Rq2vdittwo-managed ✓
GITHUB_TOKEN=ghp_uV4nR7Tk████████p3Xzdittwo-managed ✓
AWS_SECRET_ACCESS_KEY=aK9dPmXw████████L7Rqdittwo-managed ✓
DATABASE_URL=postgres://acme:pg4s█████@db.acme.iodittwo-managed ✓
SLACK_BOT_TOKEN=xoxb-8214-Ju7wK████████m2Npdittwo-managed ✓
ANTHROPIC_API_KEY=sk-ant-api03-R5kT████████v8Nqdittwo-managed ✓

Dittwo Cloud. Or your own infrastructure.

Start on the hosted app in minutes. Enterprise plans run the full platform in your cloud, VPC or on-prem.

Give your team their first twins.

Free for three people. Self-hosted on the Enterprise plan.