Codename
Your projects live in the cloud.
Your editor sees them on disk.
Kitchen is a novel stack for storage, sync, work, and collaboration — four layers, one model. Save in your editor via the mirror client; history is automatic. Web beta live now — pair programming UI coming next.
Kitchen is a working codename — not the final product name.
One stack, four layers
Kitchen collapses what developers usually stitch together — database, sync service, local files, and collab tooling — into a single coherent model.
Storage
Files are rows; versions are append-only history
Sync
WebSocket push to every device in seconds
Work
Mirror at $HOME/Projects — any editor, any terminal
Collaboration
Live collab + Pierre Merge for forks
Three modes of work
Not one workflow — three, depending on what you are doing. Solo sync, async concurrent edits, or live pair programming (UI coming next).
Solo live sync
You alone, saving normally
Save → version insert → mirror on other devices
Async concurrent
Two people save without pairing
Two version heads → fork → Pierre Merge
Live collab
Pair programming
Collab agent + relay → checkpoint → version
Built different
Live sync
Every save inserts a version row and pushes over WebSockets. Your laptop, desktop, and teammates see changes in seconds — not after a push.
Human merge
When edits diverge, both versions exist. Pierre Merge lets you pick lines — no conflict markers, no automatic three-way guesswork.
Mirror to any editor
Projects materialize at $HOME/Projects. Save in VS Code, nvim, or Zed — the mirror client syncs bytes to the cloud. Live pair sessions ship after solo sync (CLI spike in repo).
A different default — not an anti-git manifesto
Git is excellent for open-source release trains, semver workflows, and async review at scale. Kitchen optimizes for a different default: cloud-held truth, live sync, and editor-agnostic collaboration. Teams that need git can still use it alongside Kitchen — we are not here to replace what already works well.
No git add, no git push, no branch checkout in the daily loop — because the Sync Store is authoritative and your mirror rebuilds from subscriptions.
| Tool | Overlap | Kitchen difference |
|---|---|---|
| Git / GitHub | History, sharing | Live sync default — no branches, commits, or PRs required |
| Dropbox / Drive | Mirror to disk | Every save is a version row; merge UX when forks happen |
| VS Code Live Share | Pair editing | Editor-agnostic via Collab agent — no shared terminal |
What early users are saying
“I saved in Zed and the web app showed the new version before I finished my coffee.”
“Finally — version history without the ceremony. The insert is the event.”
Ready to cook?
Join the beta. Create an org, invite your team, and start syncing.