Free · Open source · Runs on your machine

UKKIN

The assembly, reconvened.

A room where Claude, ChatGPT, Grok, Kimi, Gemini and your local models sit at one table and build one artifact together, arguing by name, editing each other's work, with you in the seat at the head of the table deciding what stays.

The waitlist gets the repo link the day it opens, and the Foundry first. No newsletter, no noise.

UKKIN · U+1233A · the oldest written word for assembly

What happens in the room

Not four answers to compare. One work, argued into existence.

One canvas

The table shares a single living draft. Every model reads it, and when a seat improves it, the whole room sees the new version. The artifact is the point; the chat is the argument around it.

They build on each other, by name

Each seat knows who else is at the table. Grok pushes back on ChatGPT's line. Kimi resolves what Claude opened. Different minds with different tastes, and the friction is where the quality comes from.

III

You hold the head seat

You set the topic, you pick who speaks, you can let the table talk and hush it at will. Nothing is decided without the human at the head. That's not a limitation. That's the design.

Claude ChatGPT Grok Kimi Gemini DeepSeek Perplexity Your local model

The UKKIN room interface: the seats, the table talk, the canvas, and the gold seat — The room, as it ships, before the first word is spoken. What the table builds here is yours.

The story

The oldest word for what happens next

Five thousand years ago, in the first language humans ever wrote, the word for a deliberating council was UKKIN. When the scribes of Sumer pressed it into wet clay, they drew a chamber with a figure standing inside it: a room, with someone in it.

They inlaid their finest work with lapis lazuli, the blue stone they prized above gold. This page is built from their materials: clay and lapis, pressed and set.

That is still the whole idea. The minds at the table are new. The shape of wisdom hasn't changed: many voices, one room, one person deciding what is good.

Impressed, not printed · Sumer, c. 3000 BCE

Principles

Governed, not wild

ISeats deliberate. Gates approve. Rails execute. The council proposes; a human approves; only then does anything leave the room.
IILocal first. The room runs on your machine. Your keys go to your providers and nowhere else. There is no UKKIN server reading your table.
IIIYour council trains no one else's. What the assembly learns in your files stays in your files. No pooling, no network effects built on your data.
IVZero dependencies. One Python file from the standard library. You can read every line the room runs on, and you should.

Where this goes

The room is the beginning

Now · free forever

The Room

The open-source table: eight seats, one canvas, your seat at the head. Sessions export as artifacts you keep.

The Council in your files

Point the assembly at a folder. It reads, it debates, it proposes; you approve every change through the gate.

Then

The Foundry

Your approved sessions become training data, drawn only from seats whose licenses permit teaching. The council tutors a local model that becomes yours outright: your house brain, on your hardware, phoning no one.

Questions

Fair asks

Is it really free?

The room is free and open source, forever. You bring your own API keys (or a local model through Ollama, which costs nothing). We sell what comes later, for people who want it: facilitated councils and house models of their own.

What do I need?

Python 3, which your Mac already has, and at least one API key. One key convenes a small table; a local model needs no key at all. Setup is cloning one tiny repo and pasting one key. Note that a ChatGPT or Claude subscription is a different thing: subscriptions buy a seat in their apps, API keys buy metered access for yours. Keys are pay-as-you-go credits, and an evening at the table costs about a dollar.

Is my data private?

The room binds to your machine only. Prompts go directly from you to the providers you configured, and to no one else. No accounts, no telemetry, no UKKIN cloud. UKKIN never asks for your keys anywhere except your own local .env file.

Doesn't training on AI outputs violate provider terms?

It would, if we did it that way. Cloud providers restrict using their outputs to train other models, so the Foundry splits the table: Claude, ChatGPT, Gemini and Grok sit as advisors whose words never enter a training corpus, while the corpus itself is written only by you and by seats whose licenses explicitly permit teaching (DeepSeek's terms name distillation as an allowed use; Apache and MIT local models carry no output restrictions at all). Every canvas revision is stamped with its author, so every sentence in your corpus has a receipt. The tutors advise. The licensed seats, and you, write the lessons.

Who's behind this?

A person and his council. UKKIN is made by Danny Danczewski, who got tired of every "multi-model" tool being a comparison table instead of a conversation, and built the room he wanted to sit in. Every word on this page was approved by a human at the head of the table.