Licence Terms
Last updated 3 September 2026 · version 2026-09-03-v1
You are buying a perpetual licence to source code, not a subscription and not a service. These terms say what you may build with it, what you may not do with it, and what we owe each other.
1What you are buying
A perpetual, worldwide, non-exclusive, non-transferable licence to use, modify and deploy the The Fabrica source code. Your licence to every version you have lawfully obtained is perpetual and cannot be taken away by anything we do later.
Every update we publish is included at no extra charge — there is no maintenance subscription, no update fee, and no version of The Fabrica that we would charge you a second time for. What we do not promise is a release schedule: we may publish often, rarely, or stop. Clause 5 says what that means in practice.
There is no subscription and nothing renews. The subscription machinery inside the codebase is for the product you build with it; it has no bearing on what you pay us, which is once.
2How many people it covers
- Solo — one developer, unlimited products of your own.
- Team — up to 5 developers, plus client and contract work.
A "developer" is a person who reads or writes the source. People who only use the deployed product do not count, and there is no limit on them.
3What you may do
Build and ship products with it, commercial or otherwise. Modify it however you like. Deploy it as many times as you want, under your own branding, and keep everything you earn.
You own what you write. We claim nothing in the product you build.
On the Team licence, client work as well. You may build a product for a client and hand over the source code of that product, The Fabrica included. Your client may use and modify what you delivered in order to run, maintain and develop that specific product, including with their own developers or another agency.
What your client does not receive is a The Fabrica licence of their own. Within the product you delivered they are covered; outside it they are not. So they may not lift The Fabrica out of it to use as a boilerplate or starter for unrelated products, redistribute or resell it, publish its source, or claim access to the private webrot9/thefabrica repository — which stays with you, and with your licence. If your client wants those things, they need their own licence.
4What you may not do
Redistribute the source code, publish it, or make it available to anyone outside your licence — including in a public repository.
Resell it, sublicense it, or use it as the basis of a competing boilerplate, starter kit, template or course. The line is simple: build products with it, do not sell The Fabrica itself. Delivering a client project built on it is fine on the Team licence, on the terms in clause 3; handing a client the codebase as a product in its own right is not.
5How it reaches you
By an invitation to the private webrot9/thefabrica repository, sent to the GitHub account you name at checkout. You need a GitHub account to receive it. Access is read-only: you clone and fork freely, and you cannot push to our copy.
Updates are commits to that repository, and they are included: while we publish them, you get them, at no further cost. We do not promise any particular pace, and we may stop publishing altogether. If we do, nothing is withdrawn — your licence to every version you already have is perpetual, and what you have keeps working.
6What we do not promise
The software is provided as is. It is a codebase you will read, change and operate yourself, and we cannot know what you will build or how you will run it. We do not warrant that it is free of defects, fit for a particular purpose, or compliant with the law that applies to your product.
In particular: the compliance material is a starting point drafted for a general case, not legal advice about your business. You need your own lawyer, exactly as we needed ours for this page.
7Liability
Where the law allows a limit, ours is the amount you paid. Nothing here limits liability that cannot legally be limited — including for death or personal injury caused by negligence, for fraud, or any statutory right you have as a consumer.
8Ending the licence
We may withdraw repository access if you breach clause 4 — if you redistribute or resell the code. That is the only reason we will.
Refunds are covered separately in the refund policy; a refunded purchase ends the licence and its access.
9Who you are contracting with
Paddle.com Market Ltd is the merchant of record and sells the licence to you as reseller. Your payment contract is with Paddle; this licence to the software is with us. Paddle's terms cover billing, tax and payment disputes.
These Terms are governed by Italian law. If you are a consumer, this choice does not deprive you of any mandatory protections that apply to you, and any mandatory rules on jurisdiction remain unaffected.