Modules
Connectors to your apps, each tested in a sandbox and approved before anyone can use it. Version diffs and drift checks show what changed.
Self-hosted orchestration
Describe a process across your apps in plain language. AI drafts the Flow, a person approves it, and the engine runs exactly that version, with each member's own access.
Apache 2.0 · Runs on your own infrastructure · Your data stays with you
Why Dittoly
Many tasks we hand to an AI are the same task, asked again and again: each time it costs tokens and energy, and the same request can come back worded or done differently. Dittoly turns that task into small, tested modules joined in a Flow, so it comes back fast, the same way every time, without asking a model again.
Need judgment in a step? Keep an AI step there, with a pinned model and a cost cap. The Insights page counts the tokens and money each Flow saved by not asking an AI every time.
How it works
Say what should happen across your tools, or upload a plan as a PDF. Dittoly asks about anything unclear before it drafts.
AI drafts the Flow from approved modules. Every step, input and permission is visible, and you can edit it on a canvas.
A person reviews what the Flow can read, write and reach, then approves that exact version. Policies can require more than one approver.
The engine runs only the approved version, with each member's own credentials. If you lack access, a teammate runs that one step with theirs.
What you get
Connectors to your apps, each tested in a sandbox and approved before anyone can use it. Version diffs and drift checks show what changed.
Automate a process, then connect Flows into bigger ones that run in parallel, with pinned versions and recorded tests shown to the approver.
From an alert to a draft pull request with a regression test that fails before the fix and passes after. Java, Kotlin, Python, Go, Rust, C#, Ruby, PHP and TypeScript.
Turn approved Flows into internal apps for your team, laid out by AI, versioned and approved like everything else, and exportable.
Pinned models, per-run cost caps, team budgets and automatic stops when a control fails. Text a model wrote waits for a sign-off before it can change anything.
Expose approved Flows to Claude, ChatGPT or Copilot as tools over MCP, signed in as each person, with scoped and expiring agent identities.
Security and governance
Dittoly runs on your servers. Code it builds and tests runs in locked-down containers that cannot see Dittoly, its database or your network, only the hosts each step declares.
Get started
A Linux host with Docker 28 or later. 2 vCPU and 4 GB of memory is the minimum; 4 vCPU and 8 GB is recommended for sandboxed build and fix steps. The server guide covers requirements, single sign-on, HTTPS, upgrades and backups.
# get the code and configure
git clone https://github.com/SudoDevStudio/dittoly.git dittoly
cd dittoly && cp .env.example .env
# start Dittoly, PostgreSQL and RabbitMQ
docker compose up -d --build
# create the first admin
docker compose exec dittoly \
node dist/src/cli/bootstrap.js admin
Documentation
Set up your first module and Flow in five steps, then find a short guide for each feature: what it is, when to use it and exactly what to click.
Questions
Dittoly is self-hosted orchestration software. You describe a process across your apps in plain language, AI drafts it as a Flow from approved modules, a person approves that exact version, and the engine runs it with each member's own access.
It is a different kind of tool. Claude, Codex and other AI models and assistants answer questions and do tasks when you ask them. Dittoly is orchestration software on your own servers that turns a repeatable process into a Flow: AI drafts it, a person approves that exact version, and the engine runs it the same way every time, with each member's own access and a full audit trail. It works with these models rather than replacing them: Dittoly uses Anthropic, OpenAI or Ollama models to draft and for AI steps, and it can give approved Flows to Claude, ChatGPT or Copilot as tools over MCP.
No. AI is used once, to draft the modules and the Flow. After that, steps that call your apps run as code, without a model, so they spend no tokens and give the same result for the same input. Tokens are spent only by AI steps you choose to keep, which have pinned models and cost caps, and the Insights page shows the tokens and money each Flow saved.
Yes. Dittoly is released under the Apache License 2.0, and you run it on your own infrastructure.
Dittoly runs on your own servers with Docker, alongside PostgreSQL and RabbitMQ. Your data stays on your infrastructure. Code that Dittoly builds and tests runs in locked-down containers that cannot reach Dittoly, its database or your network, only the hosts each step declares.
A Linux host with Docker Engine 28 or later and the Compose v2 plugin. The minimum is 2 vCPU and 4 GB of memory; 4 vCPU and 8 GB is recommended for sandboxed build and fix steps.
Nothing AI drafts runs until a person approves it. The approver sees what the Flow can read, write and reach, policies can require more than one approver, and the engine runs only the approved version. Text a model wrote waits for a sign-off before any step that changes something; text from an app or a webhook waits wherever it would choose a destination or something to run. An approver can accept a named path in advance, with a written reason, and that acceptance is recorded in the audit log.
Java, Kotlin, Python, Go, Rust, C#, Ruby, PHP and TypeScript. A fix arrives as a draft pull request with a regression test that fails before the fix and passes after.
Yes. Dittoly can expose approved Flows as tools over the Model Context Protocol (MCP), with each person signed in as themselves and with scoped, expiring agent identities.