Auth & sessions
Scoped roles, API keys, token rotation — a tested module you compose once and reuse on every client app.
// for agencies & fractional CTOs
Most client apps need the same building blocks: logins, payments, invoices, customer records, tenancy, deploys, and audit. microservices.sh ships them as composable, source-visible Cloudflare modules you reuse across every engagement — so your hours go to the client's actual problem, not re-deriving auth and Stripe for the tenth time.
Stack Overflow 2025: 84% of developers use or plan to use AI tools, but 46% distrust AI accuracy and 76% do not plan to use AI for deployment or monitoring. The fix is structural, not your fault.
The hidden cost
The features change per client. Auth, payments, customer records, and tenancy don't — yet they get rewritten and re-tested each time. Compose them from reusable, source-visible modules instead, and keep your hours for the work clients pay for.
Scoped roles, API keys, token rotation — a tested module you compose once and reuse on every client app.
Idempotency, retries, signature verification — the payment wiring you'd otherwise rewrite and re-test each engagement.
Per-tenant data boundaries and custom domains — composed from a module instead of hand-rolled per project.
Append-only trails and reviewable deploys — the parts an enterprise client's legal team asks about, ready out of the box.
What you ship
Most client apps are the same business primitives every time. Compose them from composable, source-visible modules you can read before wiring them together — then spend your hours on the client-specific work they actually pay for.
What you get
Auth, payments, customer records, and tenant isolation are tested modules you compose — not features you re-derive per project. Reuse the same building blocks on every engagement and spend the hours you save on the client's actual problem.
Every module is source-visible, version-pinned in microservices.lock.json, and ships tests. When a client's CTO or procurement asks 'what is this dependency doing,' you can show them — real code you can account for, line by line.
Hours go into the client-specific value they pay for — not re-deriving auth and payments you've built ten times. Faster repeat delivery at the same billable rate means more margin per engagement.
Export the full repo on the client's own Cloudflare account. No no-code trap, no platform to explain away at handover. The client owns inspectable code; you keep the reusable modules.
Every client app you compose leaves you with the same owned modules — auth, payments, tenancy, audit — pinned and reusable. Your second project starts where the first ended: assembling from inventory you own, not re-deriving it. The work compounds instead of resetting.
How it fits the engagement
pnpm create microservices-app@latest Scaffold a client app from composable modules via CLI — auth, customer, booking, payments, email — all Cloudflare-native.
Edit config and typed hooks for the client's custom work. pnpm microservices check returns readable failures before any deploy.
Use managed Cloudflare deploys where available, or hand off the repo on the client's own account. Client workspaces keep engagements separate.
We're onboarding a small number of agencies as design partners: generate a real client booking/customer/payment app, get hands-on setup support, and tell us where it breaks. No fake testimonials — we want agencies using this on real work.