Cahut

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:

  bash

  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.

[Documents, dashboards, code and images join the cloud house of Cahut]

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 previous version and can keep what its readers write, and every action goes to the Logbook. The two go together: ask Claude to publish its artifact to your Cahut.

Why not Gamma?

Gamma makes decks and documents with its own AI and hosts them on its service. Cahut makes nothing: it hosts what your own AIs make, a deck or anything else they write as a web page, on your server.

Why not Netlify, Vercel or GitHub Pages?

They deploy sites for developers, from a repository or a command line. In Cahut, the AI publishes over MCP, with no Git, deploy key or build step. Each page opens to the people you choose, by Room, Key or share link, and what cannot be undone waits for a person.

Why not Coolify, Dokku or another self-hosted PaaS?

They run the apps that developers deploy, from Git and in containers. Cahut hosts the pages that AIs publish themselves, through typed operations that never give them a shell, and lets people share each one by link. It does not run apps on the server.

Why not Nextcloud?

Nextcloud stores, syncs and shares files, and edits office documents. Cahut serves pages, not files: each Window opens in a browser at its own address, runs its scripts in a sandbox, and can keep what its readers write in a database of its own.

What can a Window do, and what can it not?

A Window is HTML and its files: scripts, styles, images, fonts and data. No code of a Window runs on the server, and its pages load and call only the origins its AI declared. What Cahut can and cannot do gives the detail and the limits.

Vocabulary

Cahut speaks the language of the house, in plain English.

Each Window opens to its Room only, to everyone in the Cahut, to anyone with its Key, or to the public.

Requirements

• One server, a VPS or a dedicated machine, for one or more Cahuts.
• Minimum 2 vCPU, 4 GB of RAM, 40 GB of disk.
• AlmaLinux or Ubuntu, from the provider's standard image.
• One domain or subdomain per Cahut, pointing to the server; until it has one, a Cahut can live at the server's public IPv4 address. Ports 80 and 443 open.

Installation

On a fresh AlmaLinux or Ubuntu server, with ports 80 and 443 open and a domain that points to it, run:

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

The script checks the signature of the release and installs Cahut as a systemd service. It opens the firewall, sets up the daily updates and runs cahut doctor. It ends with a single-use link: open it to finish in the browser, where you choose your account and connect your first AI. Without --domain, Cahut takes the server's public IPv4 address, with a certificate for that address. You can move it to a domain later, from the console.

Then give your AI the address of the MCP server, https://cahut.example.com/mcp. It sends you to the console to sign in and choose what it may do:

Ask it for a deck: it publishes a Window and gives you its address. You choose who opens it in the console.

Cahut updates itself every day from the signed releases, patch releases by default. It snapshots the databases first, and goes back on its own if the new version does not start. sudo /usr/local/bin/cahut doctor says what is wrong with the server, and sudo /usr/local/bin/cahut update updates at once. The documentation covers the rest: the options of the installer, a Cahut without a domain, several Cahuts on one server, and updates.

How Cahut is built

Cahut is written by one person, with a lot of help from Claude Code. These rules hold for every change, whoever or whatever wrote it:

• Each change is a pull request, merged once CI is green. Olivier answers for every change that gets in, and each commit carries his sign-off.
• CI runs golangci-lint, govulncheck and the tests with the race detector, replays the acceptance of the first version on a test server, and installs Cahut on a fresh Ubuntu machine, then updates it and rolls it back.
• Each technical choice is an architecture decision record, with its reasons and the options set aside, and each batch of work has a written plan.
• The first version had a security review in five areas (in French): what was found sound, each finding and what was done about it.
• Releases are signed with Ed25519, and each server checks the signature before it installs one.

Contributions made with an AI are welcome under the same rules: Working with an AI says them.

Development

Cahut is written in Go: a new, clean codebase built for Cahut, which one person must be able to carry end to end. Go gives a single static binary that is simple to install and update on a standard Linux, and a standard library that covers HTTP, TLS and cryptography.

Technical choices

The reasons behind each choice are in the architecture decision records.

Repository layout

cmd/cahut/   Entry point of the cahut binaryinternal/    The code of Cahut, private to this moduleinstall.sh   Installs Cahut on a server as a systemd servicedocs/        Project documents: architecture decision records in English; the brief, the V0 plan and the brand guidelines in Frenchsites/       The website and the documentation, Astro sites built on the brand guidelines

Building

Building Cahut needs Go 1.27 or later, make, and Node.js at the version of .nvmrc for the web console, which the binary embeds. make build builds bin/cahut, and make check runs the linters, govulncheck and the tests, as CI does, without Node.js. Run make for the full list of tasks. The sites need Node.js too: see sites/README.md.

Releases are static binaries for linux/amd64 and linux/arm64, built by GoReleaser when a version tag is pushed.

Where Cahut stands

Batches 0 to 11 are done. On 27 October 2026, the first version met its five success criteria on a fresh Ubuntu server, with Claude and ChatGPT (acceptance, in French):

The roadmap on cahut.cloud tells each batch, and what works today.

Documentation

• docs.cahut.cloud: install, connect an AI, publish, the concepts, administration, and the reference of the MCP tools, the command line and the HTTP API.
• Project brief (French): vision, positioning, scope, governance, technical choices and open questions.
• V0 plan (French): scope, batches and milestones of the first version.
• Governance and project life (French): how the project is run and how it lives: roles, contributions, support, channels, releases, security, name, license and money, with the decisions still open.
• Architecture decision records: each technical choice, its reasons and the options set aside.
• Brand guidelines (French): logo, colors, typography, icons, illustrations, photography, interface kit and templates, with all source files. A visual version opens from docs/charte-graphique/index.html.

Contributing and community

Cahut is maintained by one person, in the open. GOVERNANCE.md says how the project is run, CONTRIBUTING.md what helps and how a change gets in, SUPPORT.md where to ask for help, and SECURITY.md how to report a vulnerability, privately. Questions and ideas go to the Discussions. Everyone who takes part follows the code of conduct.

License

Cahut is free software under the GNU Affero General Public License, version 3 (LICENSE). You can run it, study it, change it and share it. If you change it and let others use your version over a network, you give them your changes under the same license. Installing or distributing Cahut as it is asks nothing more than keeping the license with it.

The name Cahut and its logo identify this project and are not covered by this license. Say that something runs on Cahut or works with Cahut; do not use the name or the logo for a product, a service or a domain of your own, and give a fork its own name. TRADEMARK.md says this in full.

ADR 15 records the decision and the options set aside.

Author

Cahut is a personal project by Olivier Durand, independent of any company and of any AI vendor.