v0.1 public previewfor Next.js, Drizzle, Vercel

Copy the code.
Own the code.

StackFoundry is a public source registry for production SaaS modules. Install billing, API keys, database wiring, webhooks, analytics, and operations surfaces as editable code with schemas, env notes, tests, docs, and maintenance guidance.

$pnpm dlx stackfoundry add stripe-billing
View the registryBrowse modules
160+
Modules
9
Presets
12
Categories
MIT
License
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.

01

Source files

Routes, components, helpers, and server code land in canonical project paths.

02

Drizzle schema

Schema slices are delivered with migration guidance. Migrations are never applied silently.

03

Env notes

Required keys and provider setup notes are documented alongside the installed code.

04

Verification

Each module ships tests or a focused checklist so maintainers know what to prove.

Modules

Source modules, not opaque boilerplate.

Each module owns one capability. Provider modules stay adapters around shared domain interfaces, so base scaffolds stay small.

stripe-billingbilling
installable

Stripe Billing

Checkout, billing portal, subscription sync, webhook dedupe, and entitlement mapping.

Installs
  • schema/billing.ts
  • api/webhooks/stripe
  • (console)/billing
drizzle-postgresdatabase
installable

Drizzle Postgres

Postgres package, schema barrel, migrations, and server-only database access.

Installs
  • packages/db
  • apps/web/src/lib/db.ts
  • drizzle.config.ts
api-keysdeveloper platform
installable

API Keys

Key lifecycle, hashed storage, scopes, usage metadata, and management UI.

Installs
  • schema/api-keys.ts
  • lib/api-keys.ts
  • (console)/api-keys
webhook-inboxoperations
installable

Webhook Inbox

Received webhook table, status, retry controls, signature metadata, and detail UI.

Installs
  • schema/webhooks.ts
  • api/webhooks/*
  • (console)/webhooks
Next modulesplanned adapters 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.

5 active
PresetBest forIncludes
next-saasProduct teamsBilling, auth surfaces, ops, legal, docs
b2b-saasTeam productsRBAC, invites, audit, SSO, SCIM
developer-platformAPI-first appsKeys, docs, webhooks, usage
internal-adminOperatorsSupport, health, incidents, backups
ai-saasAI productsChat, 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.

registry/modules/stripe-billing/module.json
{
  "name": "stripe-billing",
  "type": "module",
  "category": "billing",
  "registryDependencies": ["drizzle-postgres"],
  "env": [
    "STRIPE_SECRET_KEY",
    "STRIPE_WEBHOOK_SECRET"
  ],
  "status": "experimental"
}