source registry for production SaaS systemsAPI keys · usage · billing · webhooks

Launch API SaaS plumbing
without a black-box starter.

Install API keys, usage tracking, rate limits, Stripe billing, credits, webhooks, docs, and operating checks into an existing app as editable source code. Modules are the product; recipes are the path; presets are only convenience bundles.

Start with API SaaSRead DocsDry-run InstallBuild SaaS Guide
157
Modules
13
Presets
30
Active Categories
MIT
License
Install

One command. The full module lands in your repo.

The strongest first path is API SaaS: keys, usage, quotas, credits, billing, docs, webhooks, and request visibility installed as normal source files.

01

Dry-run the recipe

Preview every API key, usage, billing, webhook, docs, env, and checklist file.

02

Install the source

Routes, components, helpers, server code, schema slices, and docs land in canonical paths.

03

Wire env and migrations

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

04

Verification

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

Modules

Lead with the modules people already need to monetize an API.

The registry is broad, but the public wedge is narrow: API keys, usage, quotas, billing, webhooks, docs, and operations that land in an existing app as source.

Featured
api-saas-starter

API SaaS Starter

ready

API keys, usage tracking, rate limits, credits, Stripe billing, webhooks, docs, and request visibility.

wedgerecipeAPI-first SaaSsource-owned
20 modules · staged install pathrecipejson
agent-ready-installs

Agent-Ready Installs

ready

One-shot prompt packs and context files for coding assistants to install SaaS paths safely.

agent-readyone-shot promptsrecipe-awarereview workflow
13 files · prompts · context JSONjson
api-keys

API Keys

v0.5.0

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

apideps: drizzle-postgresmaintenance skill
14 files · 1 schema · 1 skilljson
usage-metering

Usage Metering

ready

Usage events, metering helpers, quota visibility, and billing-ready records.

usagedeps: billing-coremaintenance skill
source-owned usage systemjson
stripe-billing

Stripe Billing

v0.4.2

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

billingdeps: billing-coreadapter optionmaintenance skill
18 files · 2 schemas · 1 skilldocsjson
webhook-inbox

Webhook Inbox

v0.2.0

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

apioperationsdeps: drizzle-postgresmaintenance skill
11 files · 1 schema · 1 skilljson
Featured
ai-chatbot-sdk

AI Chatbot SDK

v0.1.0

Vercel AI SDK chat, AI Elements primitives, gateway-ready model routing, and a source-owned chatbot shell.

aiVercel AI SDKdeps: ai-elementsmaintenance skill
2 files · 2 deps · 1 skilljson
Beta
resend-email

Resend Email

v0.2.0

Transactional email wiring, provider notes, templates, and delivery checks.

emailadapter optionmaintenance skill
Beta
posthog-analytics

PostHog Analytics

ready

Next.js provider, pageview tracking, event capture helper, and consent notes.

analyticsadapter optionmaintenance skill
Registry modulesadapters and product systems
  • audit-logoperations
  • security-headerssecurity
  • quota-enforcementbilling
  • email-templatescomms
  • public-api-orpcdeveloper platform
  • enterprise-ssoauth
  • backup-restoreoperations
Open module docs
Explore

Modules first. Recipes second. Presets last.

Modules are the product. Recipes show the install order for a workflow like API SaaS. Presets stay useful, but they should never make StackFoundry feel like a boilerplate.

Recipe Fit

Pick the painful workflow before installing a bundle.

5 active
PathBest forIncludes
api-saas-starterAPI-first SaaSKeys, usage, credits, billing, webhooks
agent-ready-installsCoding agentsPrompts, context, dry-run review
b2b-saasTeam productsRBAC, invites, audit, SSO, SCIM
internal-adminOperatorsSupport, health, incidents, backups
ai-saasAI productsChat, model routing, quotas, metering
What installs?

Source files, route shells, helpers, schema slices, prompts, docs, maintenance skills, 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 model
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"}