Nothing is served, shared, or run without your visible consent.
Kitchen Table is local-first and open source. The security model is simple enough to hold in your head — here's exactly how it works.
The security model
Everything you make lives in plain folders on your own machine. The Kitchen Table daemon serves those folders to the devices you approve, over local HTTPS. In v1, no arbitrary code runs on your host — the only code that executes is the JavaScript inside a viewer's own browser, sandboxed by that browser.
That means the blast radius of any single app is a browser tab. There is no server-side execution to compromise.
Encryption on the relay
When you make an app reachable away from home, you choose its relay mode per app. The choice is honest about the trade-off, because you cannot have both snapshot failover and true end-to-end at once.
TLS terminates at the edge; an encrypted-at-rest snapshot keeps links alive while your Mac sleeps. Encrypted in transit and at rest — the edge can technically read these apps.
SNI passthrough: the edge routes ciphertext by hostname only and TLS terminates inside your daemon. The operator cannot read it. No snapshot — offline means offline.
Invited and Private apps default to Strict; Public apps default to Standard. The guarantee is enforced by the open-source daemon, not by trusting our servers.
Device authorization
Every new device asks permission before it can open an app — like pairing Bluetooth. You see its fingerprint, browser, and OS, and approve or deny from the app or straight from a desktop notification. Sessions can be named and revoked individually at any time.
App isolation
Each app gets its own isolated storage. One app can never read another app's data, and the storage API is scoped to the app that owns it. Apps are served on distinct origins, so the browser's same-origin policy keeps them apart too.
Data at rest
Your source and data stay in plain folders you control. Any relay snapshot (Standard mode only) is encrypted at rest on our servers and deleted when you turn the relay off or delete the app. We never store your files beyond what a live snapshot requires.
Responsible disclosure
Found something? We want to hear from you. Report vulnerabilities privately and we'll acknowledge within two business days. Because the daemon and protocol are open source, you can audit the guarantees on this page yourself.
hello@touchai.ltdPrivate disclosure · we acknowledge within two business days