Licence

Everything in the catalog: CSS effects, blocks, pages and templates, along with the code produced for them by the site, the CLI (npx hoverlab add), the public API and the MCP server. All of it is licensed by TO BE SET — registered company or sole-trader name (trading as Hoverlab) under the terms below.

A licence is granted to a person, not to a project. It is perpetual — Pro is bought once, and code you shipped under it stays licensed even if you never come back.

Without paying anything, and without an account, you may:

• View, preview and copy every item in the catalog, and install any of it with the CLI or the API.
• Use it in unlimited personal projects, side projects, portfolios, experiments and learning material.
• Use it in non-commercial work: a hobby site, a student project, a charity or community site that makes no money, and internal prototypes that are never shipped.
• Modify it however you like. It is your code once it is in your project.
• Ship it with no attribution. A credit is welcome and never required.

Nothing you copy calls home, and nothing we deploy can change or break code you already have. That is a property of how the catalog is built, not a promise this document has to keep.

Pro is a one-time purchase covering one developer, for life. It adds the right to use the catalog in commercial work:

• Products and sites you sell, charge subscriptions for, or run advertising on.
• Client work — websites and applications you are paid to build, for as many clients as you like. Your client may keep using what you built for them indefinitely.
• Work for your employer, on products your employer sells.
• Internal tools and dashboards inside a business.
• Unlimited end products. There is no per-project fee and no cap on how many things you ship.

Pro also lifts the product limits described on the pricing page, and includes every item added to the catalog afterwards, at no further charge.

Studio is a one-time purchase covering ten people. Each seat carries the same rights as a Pro licence and, like Pro, never renews — it is a licence rather than a workspace, so the shared brand library and shared collections belong to Team rather than to this tier.

Seats are occupied by people, not by machines. Ten seats means ten named developers, and the same one-licence-one-developer rule below applies inside them.

Team covers one seat per person, billed monthly. Each occupied seat carries the same rights as a Pro licence, for as long as the subscription is live. Code shipped while a seat was active stays licensed after it lapses; new work does not.

An organisation may not buy one Pro licence and use it across a team. One licence, one developer — that is the whole of the seat rule.

These apply to free and paid users alike, because they are about competing with the catalog rather than about using it:

• Redistributing the catalog, or a substantial part of it, as a component library, template pack, theme, UI kit or catalog of your own — free or paid.
• Selling or giving away the code as the product itself, where what the buyer is paying for is the components rather than something you built with them.
• Publishing catalog items to a package registry, marketplace or gallery under your own name.
• Sublicensing, reselling or transferring your licence to someone else.
• Using the catalog as a training set for a machine-learning model intended to generate components.

The dividing line is straightforward. Building something with these components and selling that is exactly what Pro is for. Repackaging the components and selling those is not, at any tier.

• My side project makes a little money. Then it is commercial and needs Pro. It is a one-time $79 — less where you live, if you are somewhere we price regionally — and it covers everything you ever ship.
• I am a freelancer with several clients. One Pro licence covers you, across all of them. Your clients do not each need one.
• I want to sell a template I built using these blocks. Talk to us at TO BE SET — e.g. hello@yourdomain.com first. If the blocks are a component of something substantial you designed, that is usually fine; if the template is largely the blocks rearranged, it is the redistribution case above.
• Can I use it in an open-source project? Yes, if the project is non-commercial. Note that you cannot relicense the catalog code under your project’s licence — it stays under this one.
• I refunded my Pro purchase. The commercial grant ends with the refund. Anything you shipped before it stays licensed; keep shipping and you need to buy again.

The catalog is provided as it is, without warranty of any kind. It is tested, but you are responsible for what you ship. See section 8 of the Terms of Service for the limits on liability.

This document tries to answer the common cases plainly rather than exhaustively. If your situation is not in it, email TO BE SET — e.g. hello@yourdomain.com and describe it — we would rather give you a straight answer than have you guess.