Sign in Get started

Documentation

Learn the Kitchen model

Kitchen is a different way to store, sync, work on, and collaborate on code. Start here, then explore the repository docs for full depth.

Vision

Cloud holds truth. Disk is a mirror.

Mission

Make the model obvious.

Core guides

The Kitchen Way

15 min

The problem with today's four-system stack, and why cloud-held truth with a live mirror changes the daily loop.

Most developers stack Editor → Files on disk → Git → Remote hosting
Kitchen collapses storage, sync, work, and collaboration into one model
The Sync Store is authoritative; your disk is a live view

Getting Started

10 min

Six invariants to memorize before writing code against the Sync Store.

Files are rows — orgs and projects are dir files
Versions are insert-only — no upsert on content
Mirror is a view — clients talk to the Sync Store directly

Three Modes of Work

10 min

Solo live sync, async concurrent edits, and live collab — when to use each.

Solo: save → version insert → mirror on other devices
Async: two version heads → fork → Pierre Merge by line-pick
Live collab: Collab agent + relay → checkpoint → version

Git Comparison

10 min

For developers with strong git muscle memory — fair comparison, not a takedown.

Git excels at release trains, semver, and async review at scale
Kitchen optimizes for live sync and editor-agnostic collaboration
Teams can use both — Kitchen is a different default, not a replacement mandate

Six invariants

Memorize these before implementing against the Sync Store.

Files are rows — orgs and projects are dir files
Versions are insert-only — no upsert on content
Mirror is a view — web talks to Sync Store directly
Sync is live — Convex reactivity in the web client
Merge is human — Pierre / line-pick UI
Collab → checkpoint — no collab_sessions table

Ready to try it?

Create an account and set up your first org in minutes.

Get started free

Visual overview on the four layers and three modes diagrams.