Nuxter Commercial License

This license is between Devilos LLC ("we") and the person or company named as licensee of the license you bought, whoever paid ("you"). "The Kit" means the files in the private GitHub repository we invite you to ("the Kit repository") and their updates, wherever they are copied, but nothing else in a repository that holds them. Using the Kit in any way, including cloning or merging it, accepts this license.

1. Seats

A seat is one person with one GitHub account. Everyone who can read or change code that contains the Kit needs a seat, whether or not they can open the Kit repository. An Individual license has one seat and a Team license five, for you, your employees or your contractors. Seats on licenses you hold add up.

Seats cannot be shared. A seat can move only when its holder leaves you or stops working with the Kit for good; then remove their access and have them delete their copies. You are responsible for everyone you give access to.

Automated tools and services (hosting, CI, bots, AI coding tools) need no seat, nor do advisers reviewing your code for you in confidence, such as auditors or a prospective buyer.

2. What you may do

Build any number of end products with the Kit, commercial or not, and run, sell or license them, as long as nobody without a seat gets the Kit's source.
Change the Kit in any way, and keep private starting points built on it.
Take every update we publish; your access to the Kit repository lasts as long as your license.
Publish your own code that holds none of the Kit, and excerpts of up to 50 lines in bug reports, questions and articles.

An end product is an application whose main value is what you built on the Kit. Starter kits, templates, boilerplates, code generators, and anything that gives other developers the Kit's code or main features to build on, are not end products.

3. What you may not do

These rules also cover anything derived from the Kit, such as a build, a port or a rewrite, made by hand or with AI.

Sell, give away, sublicense or publish any of it outside an end product.
Let anyone without a seat read or copy it beyond what section 1 allows, for example through a public repository, fork, package or image, or git history that still holds it. Code a browser downloads to run your end product is fine; public source maps are not.
Train or ground an AI model on it that anyone without a seat can use.

4. Clients

A client is anyone other than you for whom you make, customise or deploy an end product, including a copy you run just for them, or who runs their own deployment of one. Customers who sign up to one product you run for many are not clients, nor is a new owner under section 6.

Each client needs its own license. You may buy it in the client's name, and its seat may go unused. People working on a client's end product need a seat on the client's license or on one they or their employer hold. A seat covers only its license holder's end products and client work.

5. Ownership

We own the Kit. You own the code you write, including your changes to the Kit, but the Kit's code in your end products stays ours, used under this license. Third-party code keeps its own license; THIRD_PARTY_NOTICES.md lists it, and ships with the Kit.

Keep this file, unchanged but under any name, in every repository that holds the Kit.

6. Transfer

You cannot transfer this license, except once to a company you control. A change in who owns the licensee is not a transfer.

If you sell an end product, or the business running it, to one new owner, the new owner may keep running it under this license, but needs its own license before anyone there reads or changes the code. A product built to hand over, or sold to more than one owner, is client work.

7. Updates

Each update comes under the license it ships with, and taking code from one, by merge, cherry-pick or copy, accepts that license. We will flag any change to this file in the release notes, and a later license never takes away rights for end products that exist when you take it. Commits from before v1.0.0 come under v1.0.0's license, whatever license file they carry.

8. When the license ends

We may end your license at once if you publish, sell, give away or share the Kit in breach of section 3, or repeat a breach you have put right. Any other breach ends it unless you put it right within 14 days of our notice. So does a chargeback, unless you pay within those 14 days. A full refund ends it at once. Notices go to the email address you bought with.

When it ends, so does your access, and you may not take later versions from anyone; doing so does not revive it. After a breach, end products then in use may keep running and be fixed, but not extended; delete every other copy. After a full refund or an unpaid chargeback, stop using the Kit, end products included, and delete every copy. Sections 3, 5 and 9 to 11 still apply.

9. No warranty

THE KIT IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. You are responsible for your end products, including their security, legal pages and compliance with the law. The Kit's legal pages are drafts, not legal advice.

10. Limitation of liability

TO THE FULLEST EXTENT THE LAW ALLOWS, WE ARE NOT LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL OR CONSEQUENTIAL DAMAGES, OR FOR LOST PROFITS, REVENUE OR DATA, ARISING FROM THE KIT. OUR TOTAL LIABILITY TO YOU IS LIMITED TO WHAT YOU PAID FOR YOUR LICENSE.

11. The whole agreement

This license and the terms of sale you accepted at checkout are the whole agreement about the Kit. On how you may use the Kit, this license wins. It is governed by the laws of the State of Wyoming, United States, and disputes go to the courts of Wyoming. If a court finds any part of it unenforceable, the rest still applies. Nothing in it takes away a consumer right you cannot give up.