On your computer
It starts on your laptop, and only your computer can reach it until you decide otherwise.
Build your own app · no code
Tell an AI coding agent what you keep track of. Every technical question is already answered, so the whole conversation stays about your business.
Core + Template · for software engineers
An MIT-licensed Go library for single-owner apps that ship as one binary. Sign-in, sync-safe SQLite, HTTPS, MCP OAuth and a private tunnel are decided once, and Crew tests them every day.
One app
No servers to choose, no services to stitch together. One app holds everything your business needs to track.
It starts on your laptop, and only your computer can reach it until you decide otherwise.
Give it a web address and it sets up the secure connection by itself. Nothing extra to install in front of it.
Everything lives in one file, in a folder you can sync. To back up, stop the app and copy the folder.
Skip the hard part
These are the questions that usually stop a business app before it starts. They have one good answer, so we gave it once.
Already decided: one file, saved safely to your synced folder.
Built in. Every page and every request asks for your account.
Yes, once it has its own web address. A one-time code signs you in.
Yes, with your permission. They can read and write your data, and nothing else on the computer.
Repeated sign-in attempts are slowed down, and a password needs at least 8 characters.
A private tunnel connects them to the app without putting it on the internet.
Proof, both sides
Crew is the board where our AI agents share the work and we approve what goes out. It runs on Core every day, so every answer on this page gets tested daily.
How you get it
What you keep track of, in your own words. No technical terms needed.
Give our prompt to an AI coding agent that can run commands on a computer. It makes the app around your words.
Built-in checks keep failing until the app is fully yours.
In your browser on your computer first. Later at your own web address, on your phone too.
You need an AI coding agent that can run commands. No agent, or no time? We build custom apps.
The seam
Everything that is yours goes into appserver.New. Non-test Core code never names a product; a scan enforces it.
// The whole seam between your // product and the library: appserver.New( appidentity.Identity, // every name appserver.Policy, // public allowlist appserver.Hooks, // your code appserver.Text, // your copy )
appidentity.IdentityEvery name your app answers to: app id, command, port, database and config file, env prefix, local-key header. All required, no defaults.
appserver.PolicyThe complete public route allowlist, maintenance reads, the MCP scope, the public body limit, legacy refusals and the hosted budget.
appserver.HooksYour product code, at the points where applications diverge.
appserver.TextYour product copy, including the sign-in and OAuth consent pages.
The division of labour
Built for agents · Core + Template
Every collection gets an API, so changes go through validation instead of straight into tables.
Bounded, allowlisted, read-only. The agent gets the answer, not the records.
Full-text indexes on the fields you configure.
Over MCP the agent gets exactly five tools: read, search, schema, query and write. No shell, filesystem or administration tools.
Security invariants
These are contracts in Core’s tests, not settings you might forget. Windows, macOS and Linux are supported.
One account, a token on every API, including SQL and search. Collection rules never open to anonymous requests.
Public listeners serve only the product’s route allowlist, with exact Host and Origin checks. An empty policy denies everything.
Mode 0600 in the private cache, removed at shutdown, returned by no route, stripped from every public request.
The tunnel carries one project port on loopback. No other ports, no forwarding through the server, no UDP.
Copy in on start, write back through consistent snapshots and atomic renames, keep both sides on conflict.
Public sign-in, sign-in emails, code redemption, pending OAuth and the hosted budget answer 429 with RateLimit headers.
Native HTTPS with automatic certificates on ports 80 and 443. You point your DNS at the host.
In hosted mode, password sign-in answers 404. The owner signs in with a one-time code sent by email.
Proof, both sides
Crew, the workspace we use every day, runs on the same library, so its decisions get tested daily. Applications pin an exact Core release; Crew 0.30.1 pins Core 0.1.4.
From prompt to product
Downloads the release source and stops if it doesn’t match the checksums.
Reads the rules first. They carry over unchanged, apart from the names.
Module, binary, port, database file, env prefix, headers, skill.
Your data model through migrations, CLI, web app and tests.
The last check fails until nothing of the template is left.
To build, the agent needs Go with CGO and a C compiler, Node.js 24, pnpm and GNU Make. The Windows cross-compile also needs Zig.
Start
Give it to an AI coding agent that can run commands. Set the name, the port and the data model to your own: for a business, that’s the things you keep track of. The prompt is pinned to Template 0.4.0.
Follow the released prompt at
https://github.com/pocketcontext-labs/pocketcontext-template/releases/download/v0.4.0/new-product.md
Make a new product named DealBook (lowercase dealbook, default port 8120)
from pocketcontext-template, with this data model: deals, contacts and follow-ups.The other side
Your developer friend will want the engineer side. Same app, explained from the inside.
Give your AI coding agent the prompt and a few sentences about your business.
The other side
The business side says the same thing without a line of code.
Give your coding agent the Template prompt and your data model.