Download & Licensing

Yes. The complete, unobfuscated source is on GitHub — free to clone, run, and evaluate while your business earns under £100k/year, including commercial use. You only need a licence once you cross £100k/year.

Your total business revenue — not just revenue from the product you build on the template. Under £100k/year everything is free, including commercial use. At or above it, a one-time commercial licence (from £499) keeps you compliant.

Buy the tier that matches your team: Commercial (one developer, one application), Team (up to five developers and three applications), or Agency (unlimited). Nothing else changes — you keep the same code, now licensed.

One product you build and deploy on the template. Commercial covers a single application, Team covers up to three, and Agency covers unlimited applications — whether your own or built for clients.

On the free tier, yes — it is the one thing we ask in return. Keep the credit and its link visible somewhere in your application; restyle it or move it to suit your design, just don't remove or hide it. Every other piece of Blazor Blueprint branding can go. Any paid licence — Commercial, Team or Agency — lifts it entirely, which is why a fair few people buy one before they ever reach £100k.

They aren't, technically. There's no licence key, no activation step, nothing phoning home, and nothing counting your developers or deployments. The code you download is the code you run, and it never talks to us — which is rather the point of buying a template you can read end to end.

So it runs on trust. Work out honestly which side of £100k/year your business sits, buy the tier that matches your team, and upgrade when you outgrow it. We may ask you to confirm in writing where you stand; that is the extent of it.

Worth saying plainly: Blazor Blueprint is small and independent — there is no larger company underwriting it. If it saved you months of work and your business is past the threshold, buying a licence is what keeps it maintained and improving. That is the whole enforcement mechanism.

You keep every version released during that year — and can keep using it — forever, with no recurring fees and no forced renewal. What lapses after twelve months is access to newer releases and to email support, not your right to use what you already have.

Yes. If you outgrow your tier — a second developer on Commercial, or a fourth application on Team — pay the difference between what you paid and the higher tier's list price at the time you upgrade, and the bigger limits apply from then on. You don't re-buy from scratch.

No. Under an Agency licence you build an application for a client and hand it over — source included, if that's your arrangement. They may use, run, and operate it without any licence from us. What they don't get is a licence to Blazor Blueprint itself: they can't lift it back out as a starter kit or use it to build further applications. If they want to do that, they stand where you do — free under £100k/year, licensed above it.

Possibly one. Blazor Blueprint uses third-party components under their own licences, listed in THIRD-PARTY-NOTICES.md. Almost all are permissive (MIT, Apache-2.0, BSD) and cost you nothing. The exception worth knowing about is QuestPDF, used for PDF generation: it's free below its own revenue threshold (around US $1M at the time of writing), and organisations above that must buy a QuestPDF Professional or Enterprise licence directly from QuestPDF. We can't grant that one on their behalf.

Prices exclude VAT; it's added at checkout where it applies to you, based on your location and business status. Because you get immediate access to the source on purchase, completing checkout means consenting to immediate supply and waiving the 14-day change-of-mind cancellation right — so fees are non-refundable once access is granted. That doesn't touch your statutory rights if what you receive is faulty or not as described. Full detail in the terms of sale.

No — though the line is about the form you pass it on in, not about whether our code ends up in what you ship. It always does: your application is built on the template, so the template's code lives inside the thing you deliver, and that is exactly what the licence is for. What you may not do is pass it on as a template — publish, sell, or hand it over as a starter kit, boilerplate or codebase for someone else to build their own applications from — or build a competing template from it. Ship the app, not the kit. Everything else — modify, deploy, rebrand — is yours.