Breakneck is a laser-focused .NET backend starter kit with none of the usual complexities and abstractions like DDD or clean architecture. Just the tools you need to rapidly build and scale your SaaS backend.
Key Features:
Vertical Slice Architecture - Based on FastEndpoints for basically no boilerplate feature development. Focus on Features, not philosophical discussion of where code belongs.
Metered Endpoints - Easily track how much any given user uses your API and charge accordingly. Easily manage usage statically and dynamically.
JWT / ApiKey Auth - Completely customizable entities, stored in your database, easily configurable in every endpoint. Based on Microsoft's Identity package.
Automated Tests - Unit/Integration tests can be easily done thanks to the architecture + TestContainers. Spin up an instance of a real database and your real API to run your tests against.
Streamlined Billing - Stripe integration + webhook handling for easy payments. Create checkout sessions and react to users subscribing, unsubscribing and more.
Jobs, Mails, Logging, Etc. - EF Core set up. Run background jobs with Hangfire. Create templated Emails with .cshml files. Log every request in a structured way.
Clean & Maintainable Codebase - Minimal abstractions for easier understanding. Reduced cognitive load for developers.
Project Template - Breakneck comes with a project template. You can easily opt out of certain features like auth, billing or examples.
Tools to help you rapidly build Phoenix web applications without worrying about design or reinventing the wheel.
Elixir
HEEX
Tailwind CSS
Stripe
LiveView
Phoenix
Features:
Admin
AI
Auth
Charts
CRUD
Deployment
Emails
+7 more
Frequently Asked Questions
C#
What makes C# ideal for SaaS development?
C# excels in SaaS development due to its robust ecosystem, strong typing capabilities, and excellent library support. C# 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.
.NET
What .NET-specific architecture patterns are implemented?
.NET boilerplates leverage the framework's native architecture patterns including its routing system, middleware pipeline, and controller/handler structure. They implement .NET's conventions for separating concerns, dependency injection, and service layer patterns. The codebase follows .NET's best practices for organizing models, views/components, and business logic to ensure maintainability as your application grows.
ASP.NET Core
What ASP.NET Core-specific architecture patterns are implemented?
ASP.NET Core boilerplates leverage the framework's native architecture patterns including its routing system, middleware pipeline, and controller/handler structure. They implement ASP.NET Core's conventions for separating concerns, dependency injection, and service layer patterns. The codebase follows ASP.NET Core's best practices for organizing models, views/components, and business logic to ensure maintainability as your application grows.
FastEndpoints
What FastEndpoints-specific architecture patterns are implemented?
FastEndpoints boilerplates leverage the framework's native architecture patterns including its routing system, middleware pipeline, and controller/handler structure. They implement FastEndpoints's conventions for separating concerns, dependency injection, and service layer patterns. The codebase follows FastEndpoints's best practices for organizing models, views/components, and business logic to ensure maintainability as your application grows.
EF Core
What EF Core-specific features are leveraged in these boilerplates?
EF Core 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 EF Core'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.
C#
What C#-specific tools and libraries are included?
C# 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 C#. You'll get pre-configured toolchains that enforce best practices, automated testing pipelines, and development environments optimized for C# development workflows.
.NET
How does .NET's ORM/database layer work in these boilerplates?
.NET 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 .NET's specific features like eager loading, query scopes, and transaction handling for performance.
ASP.NET Core
How does ASP.NET Core's ORM/database layer work in these boilerplates?
ASP.NET Core 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 ASP.NET Core's specific features like eager loading, query scopes, and transaction handling for performance.
FastEndpoints
How does FastEndpoints's ORM/database layer work in these boilerplates?
FastEndpoints 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 FastEndpoints's specific features like eager loading, query scopes, and transaction handling for performance.
EF Core
How is the EF Core schema designed for SaaS applications?
EF Core boilerplates include production-tested schemas for multi-tenancy, user management, subscriptions, and billing. The design follows EF Core'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 EF Core's query engine.
Stripe
How are Stripe webhooks handled securely?
Stripe webhooks are verified using the provider's signature validation to prevent spoofing attacks. The boilerplate includes webhook endpoints with proper Stripe signature verification, event type filtering, and idempotent event processing to handle duplicate deliveries. Events are processed asynchronously with retry logic, and the implementation handles Stripe's specific webhook events like subscription updates, payment failures, and customer changes.
