Build your own app with PocketContext Core · Which one are you?

Build your own app · no code

Describe your business. Get an app that’s yours.

Tell an AI coding agent what you keep track of. Every technical question is already answered, so the whole conversation stays about your business.

One appRuns on your computerWindows, Mac, Linux
  1. You say: “I run a dog-walking business. Keep track of clients, walks and payments.” (example)
  2. Your app gets: Clients (name · phone · address), Walks (client · day · minutes), Payments (client · amount · paid on)
  3. Already decided for you: Sign-in built in. Every page and every request asks for your account. Your AI agents can use it. With your permission, and only to read and write your data. Open it on your phone. At your own web address, with a secure connection. Your data is one file. Saved safely to a folder you can sync and back up. Guessing is slowed down. Too many sign-in attempts have to wait.

Core + Template · for software engineers

Bring the data model. Core brings the rest.

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.

GoMITCore 0.1.4Template 0.4.0

One app

A single file. You run it wherever you want.

No servers to choose, no services to stitch together. One app holds everything your business needs to track.

Start

On your computer

It starts on your laptop, and only your computer can reach it until you decide otherwise.

Grow

On your own server

Give it a web address and it sets up the secure connection by itself. Nothing extra to install in front of it.

Keep

Your data stays yours

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

The questions you never have to answer.

These are the questions that usually stop a business app before it starts. They have one good answer, so we gave it once.

Which database should I use?

Already decided: one file, saved safely to your synced folder.

How do I sign in?

Built in. Every page and every request asks for your account.

Can I open it on my phone?

Yes, once it has its own web address. A one-time code signs you in.

Can my AI agents use it?

Yes, with your permission. They can read and write your data, and nothing else on the computer.

What if someone guesses my password?

Repeated sign-in attempts are slowed down, and a password needs at least 8 characters.

What about my other computers?

A private tunnel connects them to the app without putting it on the internet.

Proof, both sides

We run our company on an app built on Core.

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

Four steps. All of them about your business.

  1. Describe your business

    What you keep track of, in your own words. No technical terms needed.

  2. Your agent builds it

    Give our prompt to an AI coding agent that can run commands on a computer. It makes the app around your words.

  3. It checks its own work

    Built-in checks keep failing until the app is fully yours.

  4. You open it

    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

Four values cross the boundary.

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
)
Identity

appidentity.Identity

Every name your app answers to: app id, command, port, database and config file, env prefix, local-key header. All required, no defaults.

Policy

appserver.Policy

The complete public route allowlist, maintenance reads, the MCP scope, the public body limit, legacy refusals and the hosted budget.

Hooks

appserver.Hooks

Your product code, at the points where applications diverge.

Text

appserver.Text

Your product copy, including the sign-in and OAuth consent pages.

The division of labour

You write what makes it yours. The rest was decided once.

What you write

  • Collections: migrations for the records your app holds
  • Rules: server-side hooks for what must stay true
  • Read policy: the columns SQL may read and the fields search indexes
  • Commands: the CLI verbs your agent will call
  • Web app: the screens you use on desktop and mobile
  • Skill and tests: how an agent operates it, and proof it works

What Core already decided

  • SQLite, embedded, safe in a synced folder
  • Accounts built in, authentication on every API
  • Loopback listening, Host check, own-origin CORS
  • Private tunnel and one-time sign-in codes
  • A profile registry for several projects
  • Native HTTPS, hosted mode and MCP OAuth, ready to wire

Built for agents · Core + Template

Any data model. Three ways in.

REST API · writes

Write with rules.

Every collection gets an API, so changes go through validation instead of straight into tables.

POST /api/collections/deals/records
Read-only SQL · questions

Ask, don’t page through.

Bounded, allowlisted, read-only. The agent gets the answer, not the records.

SELECT stage, count(*) FROM deals GROUP BY stage
BM25 search · finding

Find it by words.

Full-text indexes on the fields you configure.

search "acme renewal"

Over MCP the agent gets exactly five tools: read, search, schema, query and write. No shell, filesystem or administration tools.

Security invariants

Secure by default, not by checklist.

These are contracts in Core’s tests, not settings you might forget. Windows, macOS and Linux are supported.

Auth stays on

One account, a token on every API, including SQL and search. Collection rules never open to anonymous requests.

Public fails closed

Public listeners serve only the product’s route allowlist, with exact Host and Origin checks. An empty policy denies everything.

The local key stays local

Mode 0600 in the private cache, removed at shutdown, returned by no route, stripped from every public request.

One port through the tunnel

The tunnel carries one project port on loopback. No other ports, no forwarding through the server, no UDP.

The synced file is never opened live

Copy in on start, write back through consistent snapshots and atomic renames, keep both sides on conflict.

Rate limits where it matters

Public sign-in, sign-in emails, code redemption, pending OAuth and the hosted budget answer 429 with RateLimit headers.

No reverse proxy

Native HTTPS with automatic certificates on ports 80 and 443. You point your DNS at the host.

Hosted sign-in is email codes

In hosted mode, password sign-in answers 404. The owner signs in with a one-time code sent by email.

Proof, both sides

We run our company on an app built on Core.

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

Your agent does the renaming. The checks keep it honest.

  1. Copy

    Downloads the release source and stops if it doesn’t match the checksums.

  2. Read

    Reads the rules first. They carry over unchanged, apart from the names.

  3. Rename

    Module, binary, port, database file, env prefix, headers, skill.

  4. Replace the model

    Your data model through migrations, CLI, web app and tests.

  5. Prove it

    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

Change three things. Hand it over.

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.

new-product promptTemplate 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.
Example values. Copying runs nothing.

The other side

Curious what’s under the hood?

Your developer friend will want the engineer side. Same app, explained from the inside.

Your business. Your app.

Give your AI coding agent the prompt and a few sentences about your business.

The other side

Explaining it to a client or your boss?

The business side says the same thing without a line of code.

Your idea. Your binary.

Give your coding agent the Template prompt and your data model.