TortilloidEnterprise

Tortilloid Enterprise · Coming soon

A permanent record of every change your people and your AI agents make. When something breaks, ask what changed, who approved it and why. Then roll back just that change.

Agents write the code. Who keeps the record?

Every change, ever

Every change. Ever.

Append-only and indexed. Too much to read, and nothing you can’t ask about.

When did checkout last change?
Kongo

Four days ago, at 09:12 on 13 October. Codex changed the retry policy in the payments client during a dependency bump. Priya approved it.

The incident

02:14. Checkout is down.

  1. Payment errors spike.

  2. On-call asks: “Why did checkout break?”

  3. The agent answers. A dependency update four days ago changed retry behaviour in the payments client. Here’s the change, who approved it, and why. A rollback of just that change is ready.

  4. Checkout is back. The incident report writes itself from the same record.

Your team still decides what ships. They just stop guessing.

When something breaks

Three questions. Answered from the record.

01 · Trace

What changed?

Every change is recorded with when it landed, who or which agent made it, and what it touched. Kongo finds the one that matters.

02 · Understand

Why did it change?

The reasoning travels with the change. The thread, the discussion and the approval, so you fix the cause and not the symptom.

03 · Recover

How do we get back?

Roll back the single change that caused it and keep the rest of the release. The rollback is recorded too.

Built for very large codebases

Decades of decisions. One question away.

Millions of lines and years of choices nobody remembers making. Kongo has the whole record, so new starters and on-call engineers can ask instead of digging.

Every chat stays with the project. The next person to ask gets the same answer, with the change, the thread and the people behind it.

What changed just before the outage?

Kongo

One retry-policy change, buried in a dependency update.

Your agents

Keep the agents you already use.

They stay in their own windows, and share one memory with Kongo.

Tortilloid doesn’t replace Claude Code or Codex, and it doesn’t wrap them in another app. Open them in their own windows, as many as you like, and work the way you already do. Once connected, they share one memory with Kongo.

Three windows on one project. Claude Code rebuilds the orders page, Codex fixes double refunds, and Kongo reports on both. You: What did Claude Code and Codex get done today? Kongo: Claude Code rebuilt the orders page. Codex fixed the double refunds. Both are in Global History. The next step in the plan is CSV export. Want me to take it?

Tortilloid Enterprise

Built for the software your business runs on.

Every change, kept for good.

Every patch from every person and agent lands in an append-only record, with when it happened, who made it and what it touched. Nothing is overwritten and nothing quietly disappears.

Years from now, the record still answers. The why stays with the change, long after the people and the tickets have moved on.

Security and compliance

Evidence, not assurances.

Agent work stays on machines you control, and every step leaves a record. When an auditor asks who changed what and why, you show them.

Change control

Every change, by a person or an agent, is attributed and timed, and kept with the file before and after. Undo is a new entry, never an erasure.

SOC 2 CC8 · ISO 27001 A.8.32

Access decisions

Kongo’s tools are granted permission by permission. Every decision is logged, automatic approvals included.

SOC 2 CC6 · ISO 27001 A.8.15

Incident evidence

Trace what changed, who approved it and why, then roll back the one change. The rollback leaves its own trail.

SOC 2 CC7 · ISO 27001 A.5.26

No model in the middle

Prompts and code go straight from the machine to the providers you choose, with your keys. Tortilloid has no server in between.

Data handling

Entirely client side

Tortilloid and Kongo run on your machines, and the Patch Log is stored locally with the project. There’s nothing you have to host.

Data residency

Tamper-proof history

With Enterprise, secure and unchangeable Patch Log storage, hosted locally, in a secure cloud or however you need. History stays secure and auditable.

Coming with Enterprise

These are the controls auditors ask about. Tortilloid helps you produce the evidence. It doesn’t make your organisation compliant by itself.

Security and compliance

Straight answers for your security team.

Is Tortilloid SOC 2 compliant?

Not yet. Tortilloid hasn’t completed a SOC 2 audit, and we won’t show a badge until it has. Your code and prompts don’t pass through our servers, which keeps what needs auditing small. Tell us what your review needs.

Do you store our code or chat history?

No. The record and chats stay on your machines, with the project. If you turn on Remote Access, messages to a phone pass through our relay, encrypted for that device. It’s off unless you turn it on.

Do you see our prompts or code?

No. Model traffic goes straight from the machine to the provider you choose. Tortilloid contacts tortilloid.com only for the beta licence, updates and a small usage ping, never with code.

Can we self-host it?

There’s nothing you have to host. Tortilloid and Kongo run entirely on your team’s machines, and the normal Patch Log is stored locally. For Enterprise customers, we’ll offer secure, unchangeable Patch Log storage servers, hosted locally, in a secure cloud or however you need, set up customer by customer.

Can we control what agents do?

Kongo’s access is granted permission by permission today. Claude Code, Codex and other connected agents follow their own approval settings. Granting Tortilloid’s tools to each agent selectively is coming with Enterprise.

Is project data encrypted?

Not by Tortilloid in this beta. It relies on your machines’ own security, such as FileVault. Encryption at rest and immutable off-site copies of the record are coming with Enterprise.

Which platforms does it run on?

Mac today, with your own keys. Windows and Linux builds are coming very soon. Models on your own hardware are coming with Enterprise.

Built on Tortilloid

From answer to action.

Kongo, Claude Code, Codex and other MCP-connected agents share the project record and the same governed tools. Ask for a fix, run the tests and review the change, in one conversation.

Your permissions. Your approval. Every change logged with who made it and why.

Coming soon

Make the next incident a short one.

Make yourself
at home.

AI lives here.

Tortilloid

A permanent record for the software your business runs on.

Download Tortilloid
Enterprise