The Ultimate .NET SaaS Starter Kit
Built for Speed and Scale
From idea to MVP in record time.
Breakneck handles auth, billing and architecture, so you can focus on what makes your SaaS unique.
By C# devs, for C# devs
Trusted by 50+ developers
Everything you need, nothing you don't.
Breakneck is a laser-focused .NET backend starter kit.
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.
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.
Streamlines 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.
"I built Breakneck to help indie hackers and makers build their startup with a robust backend.
AspNetCore with C#, and generally all statically typed languages, are massively underrated as side project technologies.
I want to show that .NET does not have to be corporate (or corporate priced) and shines in terms of
productivity, ecosystem and developer experience.
The .NET ecosystem is way too focused on clean / onion architecture.
Ditch all the layers, abstractions, domain events and focus on what's actually happening."
Simple, Transparent Pricing
Lifetime access
For unlimited projects
- One-time purchase
- All current and future features included
- Lifetime repository access for one user
- Lifetime access to discord server for support
- Unlimited usage of code & unlimited projects
Frequently
asked questions
You will get access to the code base in the github repository.
From there you can either clone the repo or start with the project template and build your business.
No. At the moment it is just the API. Just the backend.
No. Breakneck is very direct and has basically no abstractions.
It's a starting point for 'programming', not for 'configuring'.
It's not my goal to create a 'StorageService' or 'Emailer' abstraction and then have you configure your SendGrid or SMTP or Bento account.
You can write your code in whatever way you want and swap out any tool I chose easily.
Yes. This is just the backend api. You would need to pick a frontend technology and make requests to this API.
Yes. C# in a way has become incredibly beginner friendly. It's way more approachable than it's image suggests.
All http frameworks are converging on this kind of 'endpoint->request->response as a function' syntax.
Check out youtube or this Repo to see if you like the style.
Yes. This is just the backend api. It exposes standard OpenAPI specification.
You would need to generate clients from that on your chosen frontend technology.
Other products are basically entire application frameworks and heavily focused on ddd, clean architecture, onion architecture or similar.
Their audience is .net shops who develop custom solutions for enterprise clients.
Breakneck is focused on individual developers, who want to ship products.
It focuses on the backend API. Not on the frontend.
I feel products in those frameworks are very focused on the landing page features, not the actual application features.
No, this works for enterprise projects at all levels. It's easy to get started and easy to extend.
For more info check this talk.
If you're building something thats almost static, basically a landing page with 1-2 small features it is overkill and you should stick to one language.
If you want to impress potential employers with a github project, pick something that is more focused on DDD, Clean Architecture etc.
This approach works to ship products, but the enterprise world will do what the enterprise world does.
If you want to swap out most of the technologies I chose. There is not much left, if you basically change everything.
You need basic c# and .net skills. This is basically just a collection and wiring up of a bunch of really popular, industry standard tools, libraries and custom code.
All chosen technologies have a lot of documentation and resources available for all skill levels.
You can check the documentation.
You can check this project on github to get a feel for the style.
You can check my YouTube to get a vibe check.
Yes, skills carry over. FastEndpoints is fantastic and basically MinimalApis+. Everything that works with Minimal Apis works with FastEndpoints.
Some things are syntactically different. Methods in constructors instead of attributes. Basically its a bunch of controllers with just one route.
You can. Simply remove the DI configuration + usages with your tool of choice.
There is no lock in. There is no 'Storage' abstractions, so if you simply delete the azure package, the static analysis will tell you where to go.
This is intentional. This is an opinionated project and not a 'use my framework to configure everything to your liking' solution.
Get in touch. Via contact form or hit me up at Mirco@Benthien.dev. We will find a solution.