0 Get started
The question procurement actually asks is not which features you have. It is where the data lives, who can reach it, and whether you can prove what happened. Those are the questions this kit was designed around rather than retrofitted to.
What you would compose
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.
pithy add auth
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.
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
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
In practice
Every capability runs in your Worker, in your Cloudflare account, against your D1. There is no Pithy-operated service in any request path, so there is no vendor to add to a risk register as a processor of your customers' data.
The dashboard is the one thing that reaches in, and it does so as a client rather than a host: it holds a private key, you hold and can revoke the public one, and every call it makes lands in your own audit trail under its own actor kind. What the vendor did is answerable separately from what your users did. Revocation is a row you delete, and it needs nothing from us.
What it costs
The capabilities are free at any scale, on any number of applications — MIT, except audit, which is FSL-1.1-MIT and converts to MIT two years after each release. What the dashboard sells is the admin interface itself — the screen your team administers the application from, and the work of keeping it correct. Reading is free forever, and seats are never charged for, because a team should not pay per head to administer what it already owns.
The infrastructure bill is Cloudflare's, on your own account, at your own negotiated rates.
Cloudflare sets and changes these prices; their pricing page is the authority, not this one. Pithy itself is free and always will be.
Add one capability, deploy it, and see the shape before you commit to the rest.