Cahut

A home to publish and share what your AIs make.

Documents, slide decks, dashboards and small apps, as pages at your address

on your own server, where your team works on them, whichever AI made them.

[Website](https://cahut.cloud) · [Documentation](https://docs.cahut.cloud) · [Brand](https://cahut.cloud/brand) · [Contributing](CONTRIBUTING.md) · [Security](SECURITY.md)

Cahut installs with one command on a Linux server. Claude, ChatGPT, Mistral Vibe or any MCP client publish to it, and you share a link instead of sending a file. Your team reads it and asks the AI for the next version, in Rooms where people and their AIs work on the same Windows. The AI does on its own what can be undone, a human approves the rest, and every action is logged.

Try it

• See what AIs published, without an account. demo.cahut.cloud/examples holds Windows that AIs made and published, each with the prompt that made it: a small shop, a deck the team comments on, a CV, a team report, a travel journal.
• Without a server, in two minutes. Sign up for My Cahut, a free Cahut at my.cahut.cloud with limited seats, and connect Claude or Mistral Vibe, even on their free plans, or ChatGPT on a Business, Enterprise or Edu plan. All about My Cahut.
• On your own server, in one command. On a fresh Ubuntu or AlmaLinux server, with ports 80 and 443 open and a domain that points to it:

  curl -fsSL https://cahut.cloud/install.sh | sudo sh -s -- --domain cahut.example.com

Installation says what the script does and how to connect your AI.

If Cahut is useful to you, a star helps others find it.

[!WARNING]

Cahut is young: its first release came out on 21 October 2026. It does not run the code of a Window on the server, take comments, export to PDF or PowerPoint, sign people in through single sign-on, or make backups. Keep snapshots of your server.

Why Cahut

Today, what your AIs make stays at the AI's place. A Claude link, a ChatGPT link, a Gamma deck: each lives on the service of the AI that made it. To publish it, share it or work on it with others, you turn it back into a file.

Word, PowerPoint and Excel were designed for humans who write, lay out and calculate by hand. When an AI makes the content, a page at its own address does better: it updates, keeps its previous version, opens to the people you choose, and keeps what its readers write.

Publish, share, work together: today, all three are hard.

• Scattered: a Claude link here, a ChatGPT link there, a Gamma deck somewhere else. Each AI keeps what it makes on its own service, so nothing is published in one place.
• Converted back: to share it, the result is turned back into a PowerPoint or a Word file, then attached and forwarded.
• Uncontrolled: who has access, until when, which version is the right one, where the data lives. Nobody really knows.
• Alone: each person works with their own AI. The team has no common place where its work lives and where it works on it together.
• Unguarded: handing a server to an AI means giving it a root shell, or going through a platform built for humans that it can barely use.

Your AIs make it and publish it. You share it and work on it together. Everything they produce lives in one place, as pages at your address, on your server, whatever the AI.

Cahut does not create content, it hosts it. It does not compete with AIs or creation tools: it is the neutral, self-hosted home where their work lives, and where your team works on it.

How it works

The AIs stay outside. They connect to Cahut over MCP, drop their work through bounded operations, then disconnect. No AI model runs on the server.

flowchart LR

subgraph AI["Create: the AIs"] C[Claude] G[ChatGPT] M[Mistral Vibe] P[Any MCP client] end subgraph CAHUT["Cahut, on your server"] H["Your Cahut: publish, share, access, versions, search, data, Logbook, irreversible actions approved by you"] end subgraph READ["Read"] E[Your team] CL[Your clients] PU[The public] end AI -- MCP --> CAHUT CAHUT -- a link --> READ

1. Connect. Add Cahut to your AI (MCP connector and skill) and authorize it once with OAuth, with the scope you choose.
2. Create. Ask your AI for a document, a deck, a dashboard or an app, in the style you want. The skill for Claude gives it the formats.
3. Publish. The AI publishes a Window to a Room, declares what it does, and gets its address back, such as cahut.example.com/marketing/q3-review. The previous version is kept.
4. Share. You, or the AI within the limits you set, choose who opens each Window: its Room only, everyone in your Cahut, anyone with its Key, or the public. Anything irreversible waits for approval in the console.
5. Live. Readers open the page in a browser, and a poll or a form keeps what they write in the database of its Window. The AI updates it on request. Everything goes to the Logbook.

Features

Everything below works in the latest release.

What Cahut does not do:

• Create content: that is the AIs' job.
• Run an AI model on the server: the AIs stay outside and connect to it.
• Depend on one AI vendor, or lock work into a proprietary format.
• Give an AI free access to the server.
• Run across several machines: one server holds one or more Cahuts.

Governance: knock first

The AI is the intended operator of Cahut, but never without guardrails.

1. Bounded operations. The AI acts through typed operations over MCP (publish a Window, change its data, make a share link), never through a free shell.
2. Reversible or approved. What can be undone, the AI does alone. What cannot waits for a human to approve it in the console, with a notification and an expiry.
3. The AI declares what it publishes. Each version of a Window states whether its pages run scripts, the origins they load from and call, where their forms send, and the data they keep.
4. Per-agent permissions. Each AI acts on behalf of a person, with the Rooms and the scope that person grants, revocable at any time.
5. Everything is logged. Which AI, on whose behalf, which action, which result: the Logbook is readable in the console.
6. Data stays home. Windows, their data and the Logbook live on your server.
7. Isolation. Each Window runs in a sandbox: its scripts cannot read the other Windows, the console or the reader's session. The SQL of its data runs in a worker process of its own, confined by Landlock on Linux. The Cahuts of one server share nothing but the machine.

FAQ

Why not share a Claude artifact or a ChatGPT link?

Each lives on the service of the AI that made it, and is shared on that service's terms. Cahut keeps the work of every AI in one place, on your server, at your address. Each Window opens to the people you choose, keeps its previo