Source files
Routes, components, helpers, and server code land in canonical project paths.
Production SaaS source registrybilling · auth · docs · ops · adapters
Add production SaaS features
without rebuilding them.
StackFoundry is a source-code registry for the parts every SaaS app needs: billing, auth, API keys, webhooks, docs, analytics, notifications, and operations. Pick a module, install it into your app, then review and edit the code like your own.
Install
One command. The full module lands in your repo.
A base app stays small. Registry modules add production capabilities in the same source paths your team already reviews and maintains.
Drizzle schema
Schema slices are delivered with migration guidance. Migrations are never applied silently.
Env notes
Required keys and provider setup notes are documented alongside the installed code.
Verification
Each module ships tests or a focused checklist so maintainers know what to prove.
Modules
Browse the building blocks, then open the docs.
The landing page shows the shape of the registry. The docs page explains how to install modules, review diffs, author manifests, and keep modules maintainable.
stripe-billing
v0.4.2Stripe Billing
Checkout, billing portal, subscription sync, webhook dedupe, and entitlement mapping.
drizzle-postgres
v0.3.0Drizzle Postgres
Postgres package, schema barrel, migrations, and server-only database access.
api-keys
v0.5.0API Keys
Key lifecycle, hashed storage, scopes, usage metadata, and management UI.
webhook-inbox
v0.2.0Webhook Inbox
Received webhook table, status, retry controls, signature metadata, and detail UI.
resend-email
v0.2.0Resend Email
Transactional email wiring, provider notes, templates, and delivery checks.
posthog-analytics
plannedPostHog Analytics
Event taxonomy, capture helpers, consent notes, and product analytics surfaces.
Registry modulesadapters and product systems
- audit-logoperations
- security-headerssecurity
- quota-enforcementbilling
- email-templatescomms
- public-api-orpcdeveloper platform
- enterprise-ssoauth
- backup-restoreoperations
Explore
Give users more than a wall of cards.
The registry now presents modules as searchable commands, preset comparison rows, and review prompts. These patterns borrow from product UI conventions without hiding the source-first model.
Preset Fit
Compare bundles by use case before installing.
| Preset | Best for | Includes |
|---|---|---|
next-saas | Product teams | Billing, auth surfaces, ops, legal, docs |
b2b-saas | Team products | RBAC, invites, audit, SSO, SCIM |
developer-platform | API-first apps | Keys, docs, webhooks, usage |
internal-admin | Operators | Support, health, incidents, backups |
ai-saas | AI products | Chat, model routing, quotas, metering |
What installs?
Source files, route shells, helpers, schema slices, docs, skill guidance, and verification checklists.
What stays out?
Secrets, local metadata, generated caches, and provider lock-in outside explicit provider adapter modules.
How do teams review it?
Every module is declared in a manifest with files, dependencies, env notes, schema exports, and status.
Registry
Every module is a manifest. Every manifest is a contract.
Module metadata declares source paths, dependencies, environment requirements, schema exports, and verification guidance so installs and diffs stay reviewable.
Learn the manifest modelregistry/modules/stripe-billing/module.json
{ "name": "stripe-billing", "type": "module", "category": "billing", "registryDependencies": ["drizzle-postgres"], "env": [ "STRIPE_SECRET_KEY", "STRIPE_WEBHOOK_SECRET" ], "status": "experimental"}Sponsors
StackFoundry is open source and free to use. Sponsors fund module maintenance, provider adapters, and higher-quality examples.
your logoyour logoopenopen