Pricing
One payment. No subscription, no seats, no per-token fee. What changes between the two is how many people may use it and whether you may build for clients.
-
Free
€0
The attack suite and the isolation module, MIT-licensed. Point them at the app you already have before deciding anything about this one.
Get the suite -
Personal
€99 one-time
- One developer, projects you own
- Private GitHub repository access
- Updates as new attack patterns land, committed for twelve months from the first release
-
Recommended
Commercial
€249 one-time
- Your whole team, and client work
- Private GitHub repository access
- Updates as new attack patterns land, committed for twelve months from the first release
- Security docs you can share with your team
Which licence you need
| Personal | Commercial |
|---|---|
| Who may use the code | |
| You: one developer | Every developer in your organisation |
| Products you own and run, paid ones included | |
| Yes, as many as you like | Yes, as many as you like |
| Sharing the code with another developer | |
| No: they need their own licence | Yes, inside your organisation |
| Client, agency or freelance work | |
| No | Yes, on as many projects as you take on |
Prices are before VAT; your country's rate is added at checkout. Paddle is the merchant of record, which means they are the legal seller: they take the payment, handle the tax and issue the invoice, so the invoice and your bank statement both name Paddle rather than me.
Paid once: no subscription, no seats, no per-token fee. Moving from personal to commercial costs €150: ask for the link with the button below, or write to us. The link goes to the email address of your Personal purchase, the upgrade goes to the same GitHub username as that purchase, and its price is the one in force when the link is requested — the one the link carries.
What you get, either way
Access to a private GitHub repository rather than a zip, so updates arrive as commits you can read before you pull them. A GitHub account is required — we cannot deliver the kit any other way.
- The Next.js 16 and TypeScript kit: chat, retrieval over a folder of your documents, and the nine guardrails across the four stages above.
- The attack suite, so every payload can be replayed against your configuration, your model and your index.
- The docs: the AI Act notes and the control-to-risk map, written to be handed to a colleague.
- One provider interface for Anthropic, OpenAI or a local Ollama model, so the guardrail layer does not change when the model does.
- Retrieval is deliberately plain keyword scoring over a folder. There is no vector store, because the coverage table declares the vector store out of scope and shipping one would mean shipping the part I say I do not cover.
Before you buy, the two documents worth reading: Terms of sale · Refund policy
Three ways to get guardrails into your app
All three are honest choices. What changes is who does the assembling, and who does the attacking.
-
Ask an assistant
- You get
- Code in a minute, written for your app. For a single filter, that may be all you need.
- Still yours to do
- Attacking it, and keeping it current as attacks change.
- Evidence it holds
- Whatever you test yourself.
- Cost
- Free, or the subscription you already pay.
-
Wire up the free tools
- You get
- Llama Guard, NeMo Guardrails and the OWASP documents. Free and real.
- Still yours to do
- The assembly: the isolation boundary, the allow-list, the audit log and the tests that tie them together.
- Evidence it holds
- Each tool's own, not your assembly's.
- Cost
- Free, plus a weekend.
-
Start from this kit
- You get
- A Next.js app, the attack suite and the docs, already assembled and argued. Guardrails: 9.
- Still yours to do
- Reviewing it like code you did not write. It is not certified, and nobody outside has audited it.
- Evidence it holds
- Recorded attacks replayed against it, each naming the guardrail that stops it — all recorded against one model.
- Cost
- €99 once, or €249 for a team and client work.
Pick the kit if you are shipping a RAG chatbot or an agent to people you do not know, and want the security layer as code inside your own product. Pick something else if you need certified code, a vector store or a support contract.
Questions you are about to ask
Is there a refund?
Yes. 14 days from purchase, no reason needed, whatever you have already cloned. I remove the repository access that purchase gave you, and that is the end of it. The first version's risk should be mine, not yours.
How do I pay, and what about VAT?
Paddle, acting as merchant of record. That is worth understanding rather than skipping: Paddle is the legal seller of the transaction, so they charge you, they handle VAT at your country's rate, and the invoice comes from them. What you buy from me is the licence to use the kit; what you buy from Paddle is the transaction. Prices here are before VAT. The terms of sale set out which side is which, and the refund policy is its own page.
What does the personal licence limit?
The number of people, not the number of projects. One developer, and as many products as you like as long as you own and operate them. It does not cover sharing the source with a second developer, working on it as a team, or building something you deliver to a client — each of those is the commercial licence.
How long do updates last?
Twelve months from the first release, committed. After that it depends on whether the product is alive, and the releases page says which: /changelog
What if you stop maintaining it?
Repository access is perpetual and the licence does not expire. If I close the repository I publish a final archive of the last state; you keep the code either way.
What support is there?
Email, from me, and nothing else. No ticket system, no response-time commitment and no SLA. At this price and with one person, promising one would be a lie.
Can I read the code before paying?
Yes. The proof page shows every attack, what it costs when it works and which guardrail stops it, with nothing to clone. The isolation module, every attack and the full licence text are published too, in the repository linked above. The one attack that is NOT proven is named on both.
Why trust this if nobody has used it yet?
Do not trust it, check it. The coverage table states how far each control goes including where it stops, the recorded attacks say which model they ran against, and the suite ships so you can point it at your own configuration.
Is it production-ready?
It is built to be deployed, not demoed: strict TypeScript, rate limits and an audit log come with the guardrails. It is not certified. Nobody outside has audited it, and the protected path has been measured against the recorded attacks, never against live traffic. The proof page lists what it does not stop. Review it like any code you did not write; from there, it is yours.
Is it a SaaS? Do you see my data?
No to both. It is source code that runs wherever you deploy it, with your own Anthropic or OpenAI key, or a local Ollama model that needs none. Your users' messages and your documents go to your server and the model provider you pick, never through me: the kit has no licence check and sends me nothing. What I do keep is what a purchase needs, and the privacy policy lists it with everything else this site stores.
Where does the AI Act come in?
If your chatbot talks to people in the EU, one obligation lands on almost everybody and one lands only on some. Article 50 asks you to make it clear that a person is talking to a machine — usually a copy change. Article 15 is the expensive one, and it applies if your system is high-risk under Annex III: accuracy, robustness and cybersecurity held to the state of the art, with explicit measures against data poisoning, model poisoning and adversarial inputs. Whether that is you is a question for a lawyer, not for a boilerplate. What the kit gives you is the technical half made auditable — every control with the test that exercises it, and a checklist mapping controls to obligations. Orientation for a technical team, not legal advice.