Auth, payments, storage, media, vector, games. Capabilities that compose into your own Worker, on your own Cloudflare account. Open source. Stays out of your way.
pithy init
pithy add auth
pithy add payments --with-prerequisites
pithy deploy
The part that decides it
Not a policy, and not a promise. There is no Pithy-operated service in any request path, because there is no Pithy-operated service at all.
Every capability executes in your Worker, against your D1, KV and R2, on your Cloudflare bill. Nothing is copied anywhere else, because there is nowhere else.
A policy can change quietly. This cannot: nothing in the kit holds a client for a server of ours, so there is no switch to flip and no migration for us to announce.
It holds a private key; you hold and can revoke the public one, and everything it does lands in your own audit trail. So does an agent you connect, with its own credential, marked as an agent. Revoking either is a row you change.
01 — The kit
Every one runs in your Worker, against your D1, KV and R2. Add a module, not a framework — and nothing you skip costs you anything. Most serve more than one kind of app, so filter rather than browse.
Real git repositories for your own customers, on Cloudflare Artifacts. An owner, a grant per person, and tokens that live fifteen minutes.
pithy add artifacts
A queryable trail of every security-relevant action, attributed to the right actor.
pithy add audit
Passwordless sessions, mobile and web both first-class. Magic link, email OTP, Google, Apple, GitHub, Facebook, Microsoft.
pithy add auth
Consent recorded the way a regulator asks to see it, from a checkbox to a signed authorization. Email's marketing mail and tracking follow it.
pithy add consent
Let a management client reach into your own Worker, with no data plane in between.
pithy add controlplane
Every send is a durable job: scheduled, retried, tracked. No mail ever sent inline.
pithy add email
Language for your app — negotiated per request, rendered through one seam. No tables, no bindings, no error codes of its own.
pithy add i18n
An analytical tier for event and telemetry data — one schema object derives the ingest stream, the table and the query types.
Rank your players. Submit a score, read the standings — daily through all-time.
pithy add leaderboard
A per-user balance for your app's economy — chips, gold, gems, credits. Correct by construction.
pithy add ledger
Room codes, invites, friends and matched queues. Every path lands players in one session.
pithy add matchmaking
Your users connect Claude or ChatGPT to your app. Each agent acts as the person who approved it, through your own routes, with that person's role.
pithy add mcp --floor power:agents:use
Store, track and enrich images, video, audio and documents. Config picks the backend.
pithy add media
Authoritative sessions on Durable Objects. The server holds what no client can be trusted with.
pithy add multiplayer
Accounts, the people in them, and the roles you declare — with invitations bound to an address and ownership that moves only when somebody accepts it.
pithy add organization
Five payment rails resolving to one cross-rail entitlement, in your own Worker and your own D1.
pithy add payments
Skill and experience per player, per pool. Elo, Glicko-2 and TrueSkill ship built in.
pithy add rating
One encrypted store per environment, a worker-only master key, and automatic at-rest rotation.
pithy add secrets
General file storage in your own R2 bucket, with an owner, a quota, and a link you can take back.
pithy add storage
An inbox that lands mail in your own D1, classifies it on your own AI, and knows who sent it.
pithy add support
The roster, the invitations and the fourteen-day clock Google Play makes you run.
pithy add testers
A humanity check that stacks on any route. It answers is this a human, never who is this.
pithy add turnstile
Semantic search over your own content. Workers AI embeds, Vectorize indexes, D1 keeps the text.
pithy add vector
02 — Why Pithy
Every capability runs in your Worker, your Cloudflare account, your D1 and KV. There is no Pithy-operated service in any request path, because there is no Pithy-operated service.
Workers, D1, KV, R2, Vectorize, Queues, Durable Objects, Workflows and Workers AI. Nothing to host, nothing to bolt on, and no region to pick.
MIT-licensed. Read it, fork it, own it. Published as @pithy-sh/* on npm, and --eject is always there if you want the source in your repo.
Pithy's plugin for Claude Code splits the work across a server, a web client, a mobile client and a runner, each on the model you choose. It drives the same CLI you do, deploys only on your yes, and files what the kit cannot do. Building a game? pithy-games adds a Unity client and playtests.
Once the app is live, an agent can help run it through pithy mcp, with a scoped, audited credential of its own. Compose mcp() and your users can bring theirs, each acting as the person who approved it, through your routes.
/plugin marketplace add pithy-sh/pithy#release
/plugin install pithy@pithy
03 — Who it's for
Authoritative sessions, matchmaking, skill rating, leaderboards and an economy.
Payments, a support inbox and a front end — the work you cannot hire out.
Store billing on both rails, token-first auth, and the Play closed-test clock.
An audit trail that answers who could reach what, a person's data exported or erased across every capability, regulated fields marked and encrypted, and a dashboard that never holds your data.
04 — Open source
MIT-licensed and developed on GitHub. You can have it running on localhost without an account of any kind.
A star costs you nothing and is how the next person finds it.
05 — The whole idea
Add what you need, skip what you do not, and pay Cloudflare for what you actually run. There is no tier to outgrow and no bill from us.
A backend kit for Cloudflare. Open source, composable, out of your way.
You run it in your own Cloudflare account. There is no Pithy service in the path, and no Pithy bill.