A cloud for small software — running on your own Mac

The app you just built,
shared in one link.

Kitchen Table turns any folder on your Mac into a live, private app. Ask your agent to build it, then hand the people you choose a link — no server, no signup, no deploy.

Free forever for individuals · open source · your files never leave your machine
Every folder you're serving, its address, and who's on it right now.
You built it in five minutes.
Why does sharing it take an afternoon?

Deploying small software still means cloud accounts, hosting bills, and CI pipelines — just to send someone a link. Kitchen Table is the entire cloud, quietly running on your desk.

SAY IT ONCE

Tell your agent. It's live before your coffee.

Every agent gets a first-class MCP interface — it can scaffold the app, write the files, set who can see it, and mint a share link, start to finish, in one conversation.

Claude Code · kitchentable MCP
Build us a packing list for Portugal and share it with Priya.
On it — scaffolding the app, writing files, and minting a private invite for Priya.
create_apppacking-listfolder + app.json
write_fileindex.html · style.css · data.js4 files
set_visibilityinvitedapproved devices
create_invite_link--expires 7dlink minted
get_app_urlURL + QR
Done — Packing List is live and shared with Priya (Invited, expires 7d).
kitchentable.app/i/9fK2-mZq8vL
Text it to Priya, or let her scan the QR.
shared by Adarsh · Invited
Portugal Trip 🧳
Passports
Sunscreen
Adapters (x4)
Hiking boots
Priya & 3 editing
SHARING

Share it like handing someone a key.

Give each person their own invite link, see who's actually using it, and revoke just theirs — without cutting anyone else off. The people you share with never make an account.

Magic links with optional expiry & device pinning
Per-link usage counts — know who's really using it
A per-app privacy dial: Standard, or Strict end-to-end
FROM "MY EYES ONLY" TO "ANYONE WITH THE LINK" — ONE CLICK EACH
Private

Your own devices only

Network

Anyone on your local network

Invited most used

Link holders, on approved devices

Public needs relay

Anyone with the URL, anywhere

ALWAYS IN CONTROL

Nothing runs without your yes.

Every new device asks permission, like pairing Bluetooth — right from a desktop notification you can approve or deny without opening the app. And every open and deploy is logged, so you always know who touched what.

Approve or deny device access from the banner
See fingerprint, browser & OS for every request
A full feed of opens, deploys & offline events
01 — BUILDERS

Make it in Claude Code. Ship it here.

Technical or not — if you use agents or artifacts to make personal tools, this is your deploy target.

02 — HOUSEHOLDS

A link over WhatsApp. That's the whole setup.

Family and friends install nothing and create nothing. They tap a link or scan a QR, and they're in.

03 — TEAMS

A shared shelf of internal tools.

Sprint boards, trackers, dashboards, prototypes — with roles and a team library on the paid tier.

OPEN CORE

Free on your desk. Paid off it.

Local
For individuals, on your machine
$0 forever
Download
✓ App library & instant serving
✓ Per-app SQLite storage API
✓ All four sharing levels
✓ Device pairing & access log
✓ Built-in MCP server & CLI
✓ Versioning & one-click rollback
Team
Shared internal tools
$12/user/mo
Talk to us
Everything in Table, plus
✓ Org accounts & email invites
✓ Roles: owner, editor, viewer
✓ Shared team app library
✓ Centralized access logs
ON THE RELAY · PER-APP PRIVACY

One dial per app:
reachable, or unreadable.

Serving a copy while your Mac sleeps means our servers hold that copy. True end-to-end means the link dies with your machine. You can't have both at once — so you choose, per app, the moment you switch the relay on.

WHAT WE ASK WHEN YOU FLIP IT ON

"Should this app stay reachable when this machine is asleep?"

StandardSTAYS REACHABLE

The link keeps working even when your laptop is asleep.

Snapshot failover — served from an encrypted-at-rest copy while you sleep
Encrypted in transit and at rest
TLS ends at the edge — Kitchen Table can technically read it
Best for everyday apps and anything Public.
StrictEND-TO-END

The operator could not read it if it wanted to.

End-to-end via SNI passthrough — the relay sees only ciphertext
TLS terminates inside your own daemon
No snapshot — offline means offline
Best for finances, journals, anything private.
Sensible defaults, never silent: Invited and Private apps start Strict, Public apps start Standard — and the guarantee is enforced by the open-source daemon, not by trusting our servers.
EARN TRUST

Nothing is served, shared, or run without your visible consent.

No arbitrary code runs on your host in v1 — the only code that executes is the JavaScript in a viewer's own browser, sandboxed by the browser.

Strict app isolation

One app can never read another app's storage.

End-to-end by default

Invited & private apps run Strict — the relay sees only ciphertext.

Explicit device approval

Every new device asks first — like Bluetooth pairing.

Everything is logged

Every open & deploy is visible to you, the owner.

Questions

Never. A viewer taps a link, sees a one-moment “shared with you” screen while their device pairs, and they are in the app. No login, no install, no account — ever, in the free tier.

On the free local tier the link pauses while your machine is asleep. On the paid Table tier it depends on the app’s relay mode: Standard-mode apps keep working from an encrypted snapshot (writes queue and reconcile when you wake), while Strict-mode apps stay fully private and simply go dark until you’re back.

Yes. Everything is local-first in plain folders on your machine. On the relay you pick per app: Strict apps are end-to-end (the relay sees only ciphertext, even in principle), Standard apps are encrypted in transit and at rest. Apps are strictly isolated from each other, and every access is logged for you.

The desktop app, the protocol, and the CLI are open source under a permissive license. The relay protocol is open and self-hostable — the paid product is the hosted convenience and team features.

That is the whole point. A built-in MCP server lets any agent list, create, write, set visibility, mint invite links, read storage and logs — everything the UI can do — end to end in one conversation.

No. If you can ask an agent to build a tool and drop a folder somewhere, you can share it. The person sharing might not think of themselves as a developer at all.

Pull up a chair.

Turn the folder you already have into something you can hand to anyone. Free, open source, running on your desk in minutes.

Download for MacRead the docs