Pre-1.0
What changed and when is the changelog; what exists to compose is the capability catalog; what will not change is accepted limits; and getting help is where to raise the rest.
The docs carry no version in the URL while that is true. At 1.0 this tree is frozen as the first archived version.
What ships
The shipping capabilities, each with its own tables, routes, error domain and audit actions. The catalog lists every one.
A CLI where every command takes --json, with one deliberate exception.
A control-plane seam that is present and denying until you connect something.
An OpenAPI contract for every route, and an AsyncAPI contract for every socket. pithy contract writes each Worker’s documents, your own routes included, and the kit publishes its own as docs/openapi.generated.json and docs/asyncapi.generated.json. Every socket frame is versioned by one rule: the socket contract.
Two front ends you scaffold and then own. pithy ui add react writes a web app onto the Worker’s own origin. pithy ui add react-native writes an Expo app for iOS, Android and the web, over a bearer session. Be clear about how far the native one has been proven: the kit typechecks it against React Native’s own types, renders its screens under react-native-web, and tests each native module path against a stub. It does not run it on a phone in CI. Runs on an iOS and an Android device are a release checklist item, not a merge gate.
An agent team for Claude Code. The pithy plugin installs from the kit’s release branch, so it moves only when a release does. The pithy-games add-on adds a Unity client, game design and playtests on top of it.
What is not built, and is on the list
| State | |
|---|---|
| Lakehouse | No package. pithy add lakehouse does not work. The page is a plan, written down so you can decide whether to wait |
| Audit in its own database | Defaults to the shared app database today |
| A generated reference site | The routes are described by the OpenAPI document and the CLI by pithy schema --json, but the reference pages here are hand-written, not rendered from either |
| Minting R2 access-key pairs | Cloudflare exposes no API for it, so provisioning writes the pair you supply |
| Images and Stream credentials | The permission catalog carries no keys for them |
| Store-API reconciliation for testers | Google exposes no opt-in count, so the number stays an estimate |
What is deliberately not planned
Real-time action netcode. A fixed high-rate tick loop never hibernates, which is the exact cost the multiplayer design avoids. Use Photon.
Rooms, chat, presence, broadcast. Cloudflare ships PartyServer and maintains it. Use that.
A Postgres adapter. It is Cloudflare-only, and it will stay that way. Is Pithy for you? says so at greater length.
An SDK per client platform. There is an HTTP API, a token model built for native clients, and an OpenAPI and an AsyncAPI document every language can generate from or write against. There is no Swift, Kotlin, Unity or Godot package that Pithy maintains; Unity names the generator and the version to use. React Native is the one exception: @pithy-sh/ui-react-native and the TypeScript clients it calls through, because a React Native app shares the web front end’s language and most of its screens.
A registerable email template. The runtime forbids compiling one where it runs, and two other reasons are on the page.
Locales
en is complete. es is an unreviewed first pass, and its files say so in their own heads.
Licensing
MIT throughout, with one exception: @pithy-sh/audit ships under FSL-1.1-MIT — free for any purpose except a competing product, converting to MIT two years after each release.
The control-plane seam is MIT and never gated. It is the code that runs in your Worker, and restricting it would make you can build your own client untrue.
Where the limits are written down
Accepted limits records the races that cannot be closed — because a limit nobody recorded reads as a limit nobody saw.
Compatibility records the Node floor and the compatibility date, and why moving one is not an upgrade.
Dated claims
Anything about a price or a competitor carries an as-of date, because both change and neither is ours to control.