Host Cookd yourself

The same code that runs cookd.thatlev.com runs on your own server. Your practice then never touches ours.

The source code isn’t public yet, so there’s nothing to download for now.

What you need

Node 24 and Postgres 17 (16 works), or Docker, which brings both.
A public HTTPS address for anything beyond testing on localhost.
At least one sign-in method: a Resend account with a verified domain for email codes, or a Google OAuth client.

Docker Compose

In the code’s folder, copy the example environment file, set a database password, a 32+ character secret, your public address and a sign-in method, then start it:

Terminal

cp .env.example .env
docker compose up -d --build

Compose starts Postgres, applies database migrations and serves Cookd on port 3000. Put a TLS reverse proxy such as Caddy in front of it for real use.

Vercel and any Postgres

Create a Postgres database (Prisma Postgres, Neon, Supabase and others work).
Import the repository in Vercel with apps/web as the root directory.
Add the environment variables, then apply migrations from your machine before the first deploy.

Point the extension at your server

Open the Cookd extension’s options, set Server to your address (for example https://cookd.example.com) and sign in. AI apps connect to <your address>/api/mcp.

Full guide

Every environment variable, the reverse proxy setup, Google and Resend configuration, updates and backups are in docs/SELF_HOSTING.md in the source code.