Boilerlykit packages the Next.js SaaS wiring we kept rebuilding
We are a small team that ships Next.js applications. After shipping the same auth, billing, multi-tenant, and AI wiring across client projects more times than we could count, we started packaging those patterns as production-ready templates under the SaaSForge brand. Boilerlykit is the storefront - four templates for the four shapes of product we see most often, sold once, delivered as a private GitHub repository you own forever.
Our mission
Most SaaS boilerplates either undersell what's included (you pay $99 for a landing page with a login form) or oversell it (you pay $499 for a "full stack" that breaks the first time a Stripe webhook retries). We aim for the honest middle: small, scoped templates that do one shape of product well and do not pretend to do the others.
What we believe: buying a template is buying a weekend back, not a year of support contracts. You pay once, you own the repo, you keep the updates we publish for that template, and you do not rent your foundation. If a template fits you, it should save you a month. If it does not fit you, it should be cheap and small enough that moving on is painless.
What we ship: four templates under the SaaSForge brand, each scoped to a specific buyer - Starter for the polished Next.js 16 shell, AI for streaming chat and RAG, Core for multi-tenant B2B with Stripe and RBAC, and Agency for multilingual marketing sites on Directus. Compare them on the home page or read our honest 2026 buyer's guide.
How we sell: checkout is powered by Polar as Merchant of Record, which means Polar handles EU VAT, invoices, and refunds under their buyer terms. For you as a buyer, that translates to a proper invoice, tax handled correctly for your jurisdiction, and a compliance surface we do not have to improvise. On delivery, you get an invite to a private GitHub repository containing the full source - components, API routes, SQL migrations, MDX docs. No obfuscated bundles. No DRM.
What you own: a perpetual license for the tier you bought, with lifetime access to the updates we publish for that template. You can build a commercial product on top of it, rebrand it, and deploy it for your customers. You cannot resell the template source itself as a competing product - the usual dev-template terms. Full details live on the license page.
How we build templates
Four steps between a recurring problem we hit on real client work and a template you can clone on a Saturday and ship on a Sunday.
- 01
Notice the same wiring twice
Every template starts as a pattern we re-implemented on a second or third client project - auth flows, Stripe webhooks, multi-tenant boundaries, RAG pipelines. When we hit it the second time, we write it down. When we hit it the third time, it becomes a template candidate.
- 02
Spec before code
A 1-2 page spec listing what ships, what is intentionally out of scope, what the upgrade path looks like, and which existing Boilerlykit template it complements. If we cannot name the buyer in one sentence, we do not build it.
- 03
Build it like a real product
TypeScript strict, SQL migrations, docs alongside code, honest error paths, tests on the parts that bite in production. The template must pass the same code review we would apply to paid client work - because people are paying for it.
- 04
Document the pre-purchase questions
Every template ships with MDX docs that answer what it is, what it is not, how to install, how to rebrand, how to deploy, and where to look when something is surprising. Buyers should be able to judge fit before checkout, not after.
What we refuse to do
These are not aspirations - they are decisions we have already made and would walk away from a sale to keep.
No subscription to access the code
One-time purchase. You pay once, you own the repo, you keep the updates. Subscription pricing on template code is the business model of a SaaS, not a dev tool.
No obfuscation, no minified delivery
The GitHub repo you get is exactly the repo we work in - readable TypeScript, commented SQL, MDX docs. If you cannot read it, you cannot extend it, and we failed.
No fake feature lists
If a feature is not wired end-to-end, it is not on the feature list. “SSO-ready” means the hooks exist and are documented; it does not mean we dropped a Passport strategy into a file and walked away.
No lock-in to tools you did not pick
Templates opinionate where opinions save time (Next.js, Tailwind, TypeScript) and stay neutral where opinions cost time (specific analytics, specific email providers, specific hosts). Swap anything you do not want.
No AI slop in the codebase
We use AI tools ourselves for research, boilerplate, and review. Every line that ships is read by a human who understands why it is there. The repo does not contain hallucinated imports or commented-out AI apology paragraphs.
No hidden expiry on your access
Your private repo access does not expire. If we ever wind down the business, we have contingency plans documented in the buyer terms so you keep what you paid for.
Four templates. One decision. Pick yours.
Browse the four SaaSForge templates, read the comparison guide, or read the stack page if you are still doing technical due diligence. We priced launch tiers low on purpose - none of the templates should cost more than a weekend of your time.