License

Use the code. Ship the work. Do not repackage the Vault.

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

Build with Vault. Ship with Vault. Do not turn Vault 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, 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.

License Tiers

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 systems

Always 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.

Free Core

The Free Core includes effects marked as free in the Vault catalog. 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.

MIT- Licensed Files

Some Free Core files may be released under the MIT License. If a file is marked as MIT, the MIT License terms apply to that file.

That usually means you can use, copy, modify, merge, publish, distribute, sublicense, and sell copies of the software, as long as the required copyright and license notice is preserved.

In plain English:

• You can use MIT files in personal work.
• You can use MIT files in commercial work.
• You can use MIT files in client projects.
• You can modify MIT files.
• You must preserve required license notices where the license requires it.

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 MIT 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

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:

• number of projects
• number of users or seats
• organization usage
• client usage
• update access
• support access
• redistribution limits
• template and resale restrictions
• enterprise terms

Check your plan before shipping. The checkout page is not decoration.

Project Usage

Vault Pro usage depends on your license scope.

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.

Client Work

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:

• 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 Vault asset is not extracted and resold as a standalone product
• the effect is 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 when your license allows it.

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 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.

Redistribution and Resale

Unless your license explicitly allows it, 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.

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.

If you want to include Vault effects inside:

• website templates
• theme products
• starter kits
• boilerplates
• no-code builder blocks
• marketplace assets
• downloadable design-engineering packs

you need a license that explicitly allows that use. Do not assume a normal project license covers resale packaging. It probably does not.

Attribution

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.

Seats and Team Usage

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.

Updates and Support

Access to future updates, premium variants, implementation notes, and support depends on your plan. Some licenses may include:

• lifetime use of downloaded assets
• updates while subscribed
• access to new Pro effects
• support windows
• enterprise implementation help
• private registry access
• team onboarding

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 Licensing

Enterprise teams may need custom terms.

That can include:

• custom deployment scope
• multi-brand usage
• custom seat structures
• security review
• procurement documentation
• IP warranties
• indemnity terms
• private implementation support
• locked version access
• internal distribution rules
• custom template or platform rights

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.

Compliance

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:

• terminating access tokens
• revoking Pro or Enterprise 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 or Pro
• which license applies
• whether client work is allowed
• whether SaaS/product use is allowed
• whether redistribution is restricted
• whether template or theme usage is allowed
• whether source notices must be preserved
• whether your team has the right seat or project scope

This takes five minutes. It can save five weeks of procurement theatre.

Questions

For licensing questions, commercial use clarification, enterprise agreements, or unusual deployment environments, contact:

hello@hyperiux.com

Useful details to include:

• your company name
• the effect or pack you want to use
• whether it is for your own product or client work
• number of projects
• number of users or 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.