The modern full-stack Next.js & GraphQL boilerplate
Bedrock combines all the best tools the JS ecosystem has to offer into one solid foundation for your SaaS product. It features user authentication, subscription payments, team management, GraphQL API, transactional emails, and more.
Built with developer experience in mind, Bedrock allows you to:
Get started quickly without reading thousands of pages of documentation
Build type-safe applications from database to client
Leverage code generation to move faster
Scale infinitely with serverless architecture
Bedrock handles over 40 common setup tasks so you can focus on building your product's unique features rather than wasting weeks on boilerplate.
The ultimate, modern, open-source Next.js template with pre-configured authentication and database integration
JavaScript
TypeScript
shadcn/ui
Tailwind CSS
Prisma
Stripe
Next.js
React
Features:
AI
Analytics
Auth
Blog
Community
Contact
ContentLayer
+6 more
Frequently Asked Questions
JavaScript
What makes JavaScript ideal for SaaS development?
JavaScript excels in SaaS development due to its robust ecosystem, strong typing capabilities, and excellent library support. JavaScript boilerplates leverage language-specific features to provide type-safe database queries, efficient API routing, and optimized runtime performance. The language's maturity means you get battle-tested packages for authentication, payment processing, and background jobs that integrate seamlessly.
TypeScript
What makes TypeScript ideal for SaaS development?
TypeScript excels in SaaS development due to its robust ecosystem, strong typing capabilities, and excellent library support. TypeScript boilerplates leverage language-specific features to provide type-safe database queries, efficient API routing, and optimized runtime performance. The language's maturity means you get battle-tested packages for authentication, payment processing, and background jobs that integrate seamlessly.
GraphQL
What GraphQL-specific architecture patterns are implemented?
GraphQL boilerplates leverage the framework's native architecture patterns including its routing system, middleware pipeline, and controller/handler structure. They implement GraphQL's conventions for separating concerns, dependency injection, and service layer patterns. The codebase follows GraphQL's best practices for organizing models, views/components, and business logic to ensure maintainability as your application grows.
Next.js
What Next.js-specific architecture patterns are implemented?
Next.js boilerplates leverage the framework's native architecture patterns including its routing system, middleware pipeline, and controller/handler structure. They implement Next.js's conventions for separating concerns, dependency injection, and service layer patterns. The codebase follows Next.js's best practices for organizing models, views/components, and business logic to ensure maintainability as your application grows.
React
What React-specific architecture patterns are implemented?
React boilerplates leverage the framework's native architecture patterns including its routing system, middleware pipeline, and controller/handler structure. They implement React's conventions for separating concerns, dependency injection, and service layer patterns. The codebase follows React's best practices for organizing models, views/components, and business logic to ensure maintainability as your application grows.
React
What React-specific component architecture is used?
React boilerplates follow the framework's component composition patterns with reusable, atomic design components. They implement React's best practices for component structure, props handling, event management, and lifecycle methods. The component library includes authentication flows, dashboards, data tables, forms with validation, and navigation—all built with React's native features like hooks (React), composition API (Vue), or directives (Angular).
Prisma
What Prisma-specific features are leveraged in these boilerplates?
Prisma boilerplates utilize the database's native capabilities including its transaction model (ACID for SQL, eventual consistency for NoSQL), indexing strategies (B-tree, GiST, full-text search), and advanced features like JSON columns, array types, window functions, or document queries. The schema design takes advantage of Prisma's strengths—whether that's PostgreSQL's JSONB, MySQL's full-text search, MongoDB's aggregation pipeline, or Redis's data structures.
Stripe
What Stripe API features are implemented?
Stripe boilerplates implement the provider's complete API suite including checkout sessions, subscription lifecycle management, customer portal, webhook event handling, and invoice generation. They use Stripe's latest API version with proper error handling, idempotency keys, and retry logic. The integration includes Stripe-specific features like payment intents, setup intents, subscription schedules, and tax calculation APIs.
JavaScript
What JavaScript-specific tools and libraries are included?
JavaScript boilerplates include the language's most popular and production-proven tools. This typically includes testing frameworks, linters, formatters, build tools, and package managers specific to JavaScript. You'll get pre-configured toolchains that enforce best practices, automated testing pipelines, and development environments optimized for JavaScript development workflows.
TypeScript
What TypeScript-specific tools and libraries are included?
TypeScript boilerplates include the language's most popular and production-proven tools. This typically includes testing frameworks, linters, formatters, build tools, and package managers specific to TypeScript. You'll get pre-configured toolchains that enforce best practices, automated testing pipelines, and development environments optimized for TypeScript development workflows.
GraphQL
How does GraphQL's ORM/database layer work in these boilerplates?
GraphQL boilerplates use the framework's native ORM or query builder (Prisma, Eloquent, Active Record, SQLAlchemy, etc.) with pre-configured models for users, subscriptions, teams, and common SaaS entities. They include optimized queries, relationships, migrations, seeders, and database connection pooling. The implementation leverages GraphQL's specific features like eager loading, query scopes, and transaction handling for performance.
Next.js
How does Next.js's ORM/database layer work in these boilerplates?
Next.js boilerplates use the framework's native ORM or query builder (Prisma, Eloquent, Active Record, SQLAlchemy, etc.) with pre-configured models for users, subscriptions, teams, and common SaaS entities. They include optimized queries, relationships, migrations, seeders, and database connection pooling. The implementation leverages Next.js's specific features like eager loading, query scopes, and transaction handling for performance.
React
How does React's ORM/database layer work in these boilerplates?
React boilerplates use the framework's native ORM or query builder (Prisma, Eloquent, Active Record, SQLAlchemy, etc.) with pre-configured models for users, subscriptions, teams, and common SaaS entities. They include optimized queries, relationships, migrations, seeders, and database connection pooling. The implementation leverages React's specific features like eager loading, query scopes, and transaction handling for performance.
React
How is state management handled in React boilerplates?
React boilerplates use the framework's recommended state management approach—whether that's React Context + hooks, Redux Toolkit, Zustand, Pinia (Vue), NgRx (Angular), or Svelte stores. They include pre-configured state slices for authentication, user data, subscriptions, and UI state with proper TypeScript typing. The implementation follows React's patterns for global state, local component state, and server state synchronization.
Prisma
How is the Prisma schema designed for SaaS applications?
Prisma boilerplates include production-tested schemas for multi-tenancy, user management, subscriptions, and billing. The design follows Prisma's best practices for data modeling—whether that's normalized tables with foreign keys (SQL), embedded documents vs. references (MongoDB), or partition key strategies (DynamoDB). Schemas include proper constraints, default values, and relationship management optimized for Prisma's query engine.
