If you cancel Pro or Pro+, Pro code you installed while subscribed stays in those projects and you can keep using it there. New Pro downloads and new client-project usage need an active plan.
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.
The Short Version
| Use case | Free Core | Vault Pro |
|---|---|---|
| License | MPL 2.0 (open source) | Hyperiux Pro License (proprietary) |
| Account to install | Free Hyperiux account required | Active Pro or Pro+ subscription required |
| Personal projects | Allowed | Allowed |
| Commercial websites | Allowed | Allowed |
| Client work | Allowed | Allowed |
| SaaS and product interfaces | Allowed | Allowed |
| Modify generated source | Allowed | Allowed |
| Public attribution | Not required | Not required |
| Redistribute or resell the source | Allowed under MPL 2.0 terms | Not allowed |
| Build a competing component library | Allowed under MPL 2.0 terms | Not allowed |
| Seats | Not applicable | One person per subscription |
Build with Vault. Ship with Vault. Do not turn Vault Pro into your own component marketplace. That is the line.
Source Ownership, Not Catalog Ownership
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, Pro effects, templates, or examples 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.
License Tiers
Hyperiux Vault has two licensing groups for effects, plus MIT tooling.
Hyperiux Vault├── Free Core│ └── Free effects, open source under MPL 2.0├── Vault Pro│ └── Pro effects under the proprietary Hyperiux Pro License└── Tooling └── hyperiux CLI and hyperiux-mcp-server, under MITFree effects are open source. Pro effects are not. A free scroll reveal and a Pro WebGL scene do not carry the same terms.
Free Core
The Free Core includes effects marked as free in the Vault catalog. Installing them needs a free Hyperiux account. Free Core effects can be used in personal and commercial projects, including:
- portfolio sites
- marketing websites
- client websites
- SaaS interfaces
- product pages
- campaign pages
- internal tools
- case studies
- editorial projects
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.
MPL 2.0 Licensed Files
Free Core effects are open source under the Mozilla Public License 2.0 (MPL 2.0).
That means you can use, copy, modify, and distribute them, as long as the license notice is preserved and changes to those source files stay available under MPL 2.0 when you distribute them.
In plain English:
- You can use free effects in personal work.
- You can use free effects in commercial work.
- You can use free effects in client projects.
- You can modify free effects.
- No attribution is required.
- Keep the license notice in the effect’s source files.
- If you distribute modified versions of those files, share those changes under MPL 2.0.
Vault Pro
Vault Pro includes the Pro effects in the catalog, available on the Pro and Pro+ plans.
Pro effects are licensed under the proprietary Hyperiux Pro License. They are not MPL 2.0 and they are not open source.
While you have an active Pro or Pro+ subscription, you can use Pro effects in:
- personal projects
- commercial projects
- client projects
You cannot:
- redistribute, resell, or share Pro source
- build a competing component library from Pro source
Check your plan before shipping. The checkout page is not decoration.
Client Work
You can use Vault effects in client projects. Free Core effects are covered by MPL 2.0. Vault Pro effects are covered while your Pro or Pro+ plan is active.
In most client work, the safest model is:
- the effect is used inside the client project
- the generated source is shipped as part of that project
- the client can run and maintain the project
- the raw Pro source is not extracted and resold as a standalone product
- Pro effects are not added to a public template, marketplace pack, or competing library
Build the site. Do not resell the toolbox.
SaaS and Product Platforms
Vault can be used inside monetized products.
That includes:
- SaaS dashboards
- subscription platforms
- product websites
- enterprise tools
- authenticated web apps
- internal portals
- commercial marketing systems
The restriction is not about making money with your product.
You can. The restriction is about reselling Pro source as source.
A paid SaaS interface using a Pro transition is fine. A marketplace pack selling that transition as your own is not.
Redistribution and Resale
Under the Hyperiux Pro License, you may not:
- redistribute Vault Pro source files
- sublicense Vault Pro assets to third parties
- resell Vault Pro effects as raw assets
- upload Vault Pro source to public repositories
- include Vault Pro assets in public boilerplates
- include Vault Pro assets in starter kits for resale
- package Vault Pro assets inside website builder templates
- upload Vault Pro assets to marketplaces or competing libraries
- offer Vault Pro assets as downloadable source outside the licensed project context
This applies even if you heavily style or rename the files. Changing the jacket does not make it your motorcycle.
Free Core effects follow MPL 2.0 instead: you can redistribute them, as long as you keep the license notice and share changes to those files under MPL 2.0.
Templates, Themes, and Starters
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.
Vault Pro effects cannot be included inside:
- website templates
- theme products
- starter kits
- boilerplates
- no-code builder blocks
- marketplace assets
- downloadable design-engineering packs
That is redistributing Pro source, and the Hyperiux Pro License does not allow it. Free Core effects can go into these under MPL 2.0 terms.
Attribution
No attribution is required. You do not need to place a “Built with Hyperiux Vault” badge on your client’s homepage.
The footer has suffered enough. Free Core files are covered by MPL 2.0; keep any license notice in the source.
Private source notices are not visual clutter. They are receipts.
Seats and Team Usage
Each Pro or Pro+ subscription covers one person: one seat.
Only the subscriber should access Pro source through the site, CLI, or MCP server. Do not share private access tokens across teams, clients, contractors, or public repositories. Teams and agencies that need more seats can contact us at hello@hyperiux.com.
A shared token in a Slack thread is not a deployment strategy. It is a future incident report.
Cancelling Pro or Pro+
If you cancel your Pro or Pro+ plan:
- Pro code you installed while subscribed stays in those projects, and you can keep using it there.
- New Pro downloads need an active plan.
- Using Pro effects in new client projects needs an active plan.
- Free Core (MPL 2.0) effects are unaffected.
CLI and MCP Server
The Hyperiux CLI (hyperiux) and the MCP server (hyperiux-mcp-server) are licensed under MIT. That covers the tooling, not the effects it installs. Each effect keeps its own license: MPL 2.0 for Free Core, the Hyperiux Pro License for Vault Pro.
Compliance
Hyperiux Vault is generous with builders and firm 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:
- terminating access tokens
- revoking Pro or Pro+ access
- blocking registry pulls through the CLI
- removing access to premium assets
- requesting takedown
- pursuing legal enforcement where necessary
We prefer building. We are also capable of reading logs.
Before You Ship
Before using Vault in a commercial project, check:
- which effect you are using
- whether it is Free Core (MPL 2.0) or Pro (Hyperiux Pro License)
- whether your Pro or Pro+ plan is active for new Pro installs
- whether Pro source would end up redistributed
- whether template or theme usage involves Pro effects
- whether MPL 2.0 license notices are preserved
- whether everyone using Pro effects has their own seat
This takes five minutes. It can save five weeks of procurement theatre.
Questions
For licensing questions, commercial use clarification, extra seats for teams and agencies, or unusual deployment environments, contact:
hello@hyperiux.comhello@hyperiux.comUseful details to include:
- your company name
- the effect you want to use
- whether it is for your own product or client work
- number of people who need seats
- whether the work will be redistributed as a template, starter, or asset pack
- any legal or procurement requirements
Use the code. Ship the work. Keep the Vault out of the marketplace bin.