Starter stack
B2B SaaS
An enterprise-aware SaaS stack for organizations, SSO, relational data, billing, durable work, and managed deployment.
Recommendation
A B2B product team with customer organizations and near-term enterprise identity requirements
Assumptions
This stack is useful only while these product and operating assumptions remain true.
- The application owns its canonical tenant, membership, authorization, data-isolation, and billing domain.
- Enterprise SSO or directory provisioning is a real customer requirement rather than speculative roadmap scope.
- PostgreSQL is the system of record for domain data.
- Durable asynchronous workflows are material to customer onboarding or operations.
What is in this stack
Each layer has a clear job. Replaceable tools can be swapped when your constraints change.
Next.js
Customer and administrative product surface · Core choice
WorkOS
SSO, directory, and organization identity integration · Replaceable
PostgreSQL
Tenant, membership, domain, and operational data · Replaceable
Stripe
Payment and account billing primitives · Replaceable
Inngest
Event-driven onboarding and operational workflows · Replaceable
Vercel
Managed Next.js deployment and runtime · Replaceable
Why these tools fit together
Next.js provides the product surface; WorkOS supplies enterprise identity integrations; PostgreSQL remains the application system of record; Stripe owns payment primitives; Inngest handles durable event-driven work; Vercel hosts the web application. The application must map these systems through stable tenant and user identifiers.12345679101112151618
When to replace a layer
Change a tool when the underlying constraint changes, not because another logo is more popular.
Enterprise identity
A broad enterprise platform is unnecessary or its organization model conflicts with the product domain.
Direction: Use a focused SSO layer or application identity route.
Payments
Seller-of-record, tax, or regional commercial responsibility must be outsourced.
Direction: Evaluate a Merchant of Record route.
Durable work
Workflow duration, determinism, throughput, or self-hosting requirements exceed Inngest's fit.
Direction: Evaluate another Background Jobs or workflow route.
Official resources
Use the Stack to decide, then verify implementation and commercial details with each primary source.
Sources
Primary evidence used for the Stack fit and dependency boundaries.
- 1Next.js documentation
Vercel · Accessed Official
- 2WorkOS documentation
WorkOS · Accessed Official
- 3PostgreSQL documentation
PostgreSQL Global Development Group · Accessed Official
- 4Stripe documentation
Stripe · Accessed Official
- 5Inngest documentation
Inngest · Accessed Official
- 6Vercel documentation
Vercel · Accessed Official
- 7Next.js documentation
Vercel · Accessed Official
- 8Next.js license
Vercel · Accessed Official
- 9WorkOS Single Sign-On
WorkOS · Accessed Official
- 10WorkOS Directory Sync
WorkOS · Accessed Official
- 11WorkOS pricing
WorkOS · Accessed Official
- 12What is PostgreSQL
PostgreSQL Global Development Group · Accessed Official
- 13PostgreSQL license
PostgreSQL Global Development Group · Accessed Official
- 14Stripe pricing
Stripe · Accessed Official
- 15How Stripe Connect works
Stripe · Accessed Official
- 16Serving Inngest functions
Inngest · Accessed Official
- 17Inngest pricing
Inngest · Accessed Official
- 18Vercel documentation
Vercel · Accessed Official
- 19Vercel pricing model
Vercel · Accessed Official