Loading
Use the code. Ship the work. Do not repackage the Vault.
Code already installed remains in project, new Pro downloads and new client-project usage require active access.
Hyperiux Vault is built around a simple licensing idea: developers should know what they can use, where they can use it, and what they should not resell as their own. Nobody wants a launch blocked because a motion file came with a licensing clause written like a tax trap.
This page explains the licensing model in plain language. The actual license file, checkout terms, or signed agreement controls if there is ever a conflict.
| Use case | Free Core | Vault Pro |
|---|---|---|
| Personal projects | Allowed | Allowed |
| Commercial websites | Allowed | Allowed under your plan |
| Client work | Allowed | Allowed under your plan |
| SaaS and product interfaces | Allowed | Allowed under your plan |
| Modify generated source | Allowed | Allowed |
| Public attribution | Not required unless stated | Not required unless stated |
| Redistribute as a competing library | Not allowed for Pro assets | Not allowed |
| Resell as templates, themes, or asset packs | Depends on the Free Core license | Not allowed without permission |
| Share raw Pro source files | Not applicable | Not allowed |
Build with Vault. Ship with Vault. Do not turn Vault into your own component marketplace. That is the line.
Vault effects are added to your project as source files.
That means your team can inspect them, edit them, refactor them, tune the motion, change the styling, adjust the layout, and adapt the interaction behavior for your product or client project.
That is source ownership in practice.
It does not mean you own the Hyperiux Vault catalog, brand, registry, paid packs, templates, examples, or source assets as a competing product.
You can make the code fit your website. You cannot make Vault your inventory.
Important distinction. Conveniently, also the obvious one.
Hyperiux Vault has two main licensing groups.
Hyperiux Vault
├── Free Core
│ └── Free effects for personal and commercial use
└── Vault Pro
└── Paid effects, packs, templates, variants, and commercial systemsAlways check the license attached to the specific effect, pack, or plan you are using. A free scroll reveal and a paid WebGL template may not carry the same terms.
The Free Core includes effects marked as free in the Vault catalog. Free Core effects can be used in personal and commercial projects, including:
You can modify the generated source files inside your project.
You can adapt styling, animation timing, layout, responsive behavior, and implementation details. That is the point. Drop in the interaction. Keep the taste.
Some Free Core files may be released under the Mozilla Public License 2.0. If a file is marked as MPL 2.0, the MPL 2.0 terms apply to that file.
That usually means you can use, copy, modify, and distribute the software, as long as the required copyright and license notice is preserved and covered source-file changes remain available under MPL 2.0.
In plain English:
If Hyperiux wants to restrict redistribution, template resale, competing libraries, or marketplace packaging for certain free assets, those assets should not be published under standard MPL 2.0 terms.
Use a custom Free Core license for those assets instead. Legal precision is not boring. Legal precision is how people ship without sweating.
Vault Pro includes paid effects, advanced variants, templates, motion systems, WebGL configurations, implementation notes, commercial packs, and team-focused assets.
Vault Pro is licensed under Hyperiux commercial terms.
When you purchase a Pro pack or maintain an active subscription, you receive a non-exclusive right to use the licensed assets according to your selected plan.
Your plan may define:
Check your plan before shipping. The checkout page is not decoration.
Vault Pro usage depends on your license scope.
| License type | Usage scope |
|---|---|
| Single-project license | Use within one production project or web application |
| Multi-project license | Use across multiple production projects covered by your plan |
| Team license | Use by an approved team within one organization |
| Enterprise license | Custom scope based on a signed agreement |
If your license says one project, use it in one project. If your client needs it across five brands, buy the license that covers five brands.
Simple rules age well.
You can use licensed Vault effects in client projects if your license allows client work.
For Free Core effects, check the specific license attached to the file. For Vault Pro effects, check your selected plan.
In most client work, the safest model is:
Build the site. Do not resell the toolbox.
Vault can be used inside monetized products when your license allows it.
That includes:
The restriction is not about making money with your product.
You can. The restriction is about reselling Vault source assets as assets.
A paid SaaS interface using a Vault transition is fine under the right license. A marketplace pack selling that transition as your own is not.
Unless your license explicitly allows it, you may not:
This applies even if you heavily style or rename the files. Changing the jacket does not make it your motorcycle.
Templates are different from websites.
A website uses Vault to create an end experience. A template redistributes Vault as part of a product someone else can reuse. That matters.
If you want to include Vault effects inside:
you need a license that explicitly allows that use. Do not assume a normal project license covers resale packaging. It probably does not.
Public attribution is not required unless the specific license says otherwise. You do not need to place a “Built with Hyperiux Vault” badge on your client’s homepage.
The footer has suffered enough. If a file includes a license notice or copyright header that must be preserved, keep it in the source.
Private source notices are not visual clutter. They are receipts.
Some Pro plans may be licensed by seat, team, organization, or workspace.
If your plan includes seats, only authorized users should access the Pro registry, private packages, premium source files, or downloadable assets. Do not share private access tokens across teams, clients, contractors, or public repositories. Use the right license for the number of people using the assets.
A shared token in a Slack thread is not a deployment strategy. It is a future incident report.
Access to future updates, premium variants, implementation notes, and support depends on your plan. Some licenses may include:
Read the plan details before assuming update access. A license to use an asset is not always a license to receive every future asset.
Enterprise teams may need custom terms.
That can include:
If your legal, security, or procurement team needs special terms, use an enterprise agreement. Big organizations need clean paper trails. The motion can be playful. The paperwork should not be.
Hyperiux Vault is generous for builders and firms with bad actors.
If a user, team, or organization scrapes, republishes, resells, sublicenses, or repackages proprietary Vault assets into competing developer tools, public registries, marketplaces, templates, or redistributed asset libraries, Hyperiux may take action.
That may include:
We prefer building. We are also capable of reading logs.
Before using Vault in a commercial project, check:
This takes five minutes. It can save five weeks of procurement theatre.
For licensing questions, commercial use clarification, enterprise agreements, or unusual deployment environments, contact:
Useful details to include:
Use the code. Ship the work. Keep the Vault out of the marketplace bin.