The hard part of shipping alone is not the feature. It is everything around it: taking money in five places, answering the mail, sending the mail, and putting a sign-in screen in front of it. Each of those is a week you do not have, and each of them is already written.
What you would compose
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
A per-user balance for your app's economy — chips, gold, gems, credits. Correct by construction.
pithy add ledger
Store, track and enrich images, video, audio and documents. Config picks the backend.
pithy add media
Five payment rails resolving to one cross-rail entitlement, in your own Worker and your own D1.
pithy add payments
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
In practice
pithy add auth gives you passwordless sign-in. pithy add payments gives you Stripe, Paddle, Lemon Squeezy and both app stores resolving to one entitlement. pithy ui add react scaffolds the front end into the same Worker — including the sign-in screens, the paywall, and the pricing and subscription screens, because you composed auth and payments.
One origin, one deploy, no CORS. Then pithy add support puts the mail that follows into your own D1, classified on your own AI binding and already linked to what the sender bought.
What it costs
Cloudflare's free tier covers a real amount of traffic, and the paid Workers plan starts at a few dollars a month. You pay Cloudflare for what you actually run.
There is no Pithy bill at any volume. The dashboard has a paid tier for acting on production from a browser, and reading it is free forever — so the part a solo builder needs most is the part that is never gated.
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.