Licensing Information

At Vuetify Store, we offer three types of licenses designed for different needs. This guide will help you choose the right license for your use case.Quick Guide: Which License Do I Need?

Quick Guide: Which License Do I Need?

Are you working on private personal projects without profit intent?

Personal License

Are you developing a commercial product or service?

Commercial License

Does your company develop multiple applications or products?

Unlimited License


License Types

1. Personal License

Most affordable • Single project • Non-commercial use only • Private project

Ideal for:

  • Personal and learning projects (private)
  • Personal portfolios and websites
  • Private prototypes and demos without profit intent
  • Personal experiments and practice

Allows:

  • Use the product in ONE private non-commercial project
  • Modify and customize according to your needs
  • Maintain the project indefinitely
  • Display the project in your personal portfolio

Does NOT allow:

  • Use in revenue-generating projects
  • Use in open source or public code projects
  • Making public the source code that includes our product
  • Use in multiple projects
  • Transfer the license to another person or company
  • Resell or redistribute the product

Important: The code of your project that uses our product must remain private. If you plan to make your project open source, you need a different license.


2. Commercial License

Single project • Commercial use allowed

Ideal for:

  • A specific web or mobile application that you sell or monetize
  • An e-commerce website
  • A SaaS platform (single product)
  • Company internal applications (single project)
  • Freelance projects for clients (one client, one project)
  • Open source projects with commercial purposes

Allows:

  • Use the product in ONE commercial project
  • Generate revenue with your project
  • Charge end users for access or services
  • Use in client projects (limited to that specific project)
  • Make your project code public if necessary

Does NOT allow:

  • Use in multiple projects or applications
  • Transfer the license to other projects
  • Resell or redistribute the product as a template or tool

Practical example: If you're an agency developing websites for clients, you'll need a Commercial License for each website where you use our product.


3. Unlimited License

Unlimited use • Multiple projects • Commercial and personal

Ideal for:

  • Development teams in companies
  • Agencies developing for multiple clients
  • Freelance developers with multiple active projects
  • Companies with multiple internal applications
  • Startups with multiple products in development
  • Developers maintaining multiple open source projects

Allows:

  • Use the product in ALL your projects
  • Commercial and personal projects without limit
  • Corporate internal applications (as many as you need)
  • Projects for multiple clients
  • Open source projects (public or private)
  • Future new projects without additional purchases

Does NOT allow:

  • Transfer the license to another company or organization
  • Resell the product as a standalone template or tool

Practical example: A company with 5 different internal applications for their corporate staff would only need ONE Unlimited License instead of 5 separate Commercial Licenses.


Glossary of Terms

Project

A project is a specific application, website, platform, or system that you develop. Each URL, mobile application, or independent system counts as a separate project.

Examples of separate projects:

  • Corporate website → Project 1
  • Company mobile application → Project 2
  • Employee internal dashboard → Project 3
  • CRM system → Project 4

Private Project

A project whose source code is not publicly accessible. The project can be in production and used by others, but the code that includes our product is not available in public repositories nor is it open source.

Examples:

  • Private repository on GitHub/GitLab
  • Publicly deployed application but with private code
  • Personal website without public repository
  • Local prototype on your computer

Open Source Project / Public Code

A project whose source code is publicly available under an open source license, allowing others to view, use, modify, and distribute the code.

Examples:

  • Public repository on GitHub
  • Library published on npm
  • Project under MIT, Apache, GPL licenses, etc.
  • Contributions to public community projects

Important: Open source projects require a Commercial or Unlimited License.

Commercial Project

A project where there is money exchange or revenue generation directly or indirectly.

Examples of commercial projects:

  • SaaS application with monthly subscriptions
  • E-commerce selling products
  • Platform with paid memberships
  • Company website (even if informational)
  • Internal application of a corporation for its employees
  • Website developed for a client as a freelancer
  • Application with monetized advertising
  • Marketplace charging commissions

Non-Commercial Project

A personal, educational, or learning project that does NOT generate revenue in any way and remains private.

Examples of non-commercial projects (qualifying for Personal License):

  • Your personal portfolio (private code)
  • Personal blog without monetization or advertising (private code)
  • Learning or practice project (private)
  • Personal experiment without public code distribution

DO NOT qualify for Personal License:

  • Open source projects (require Commercial or Unlimited License)
  • Publicly shared tools
  • Any project with public source code

Internal / Corporate Applications

Software developed and used exclusively by employees of an organization, not available to the public. Although not directly "sold," these applications are considered commercial use because the company operates for profit.

Examples:

  • Internal inventory management system
  • Human resources dashboard
  • Custom CRM for sales team
  • Employee portal with internal documentation

End User

The person who uses your application or website. If you charge these users (through subscriptions, purchases, memberships, etc.), your project is commercial.

Restrictions Applicable to All Licenses

Never allowed:
  • Resell our digital products as your own
  • Redistribute the product to third parties
  • Share downloaded files with other users
  • Use the product to create derivative products that compete with us
  • Claim authorship of the original product

Have Questions?

If after reading this guide you still have questions about which license you need, contact us with this information:

  1. Project description: What are you building?
  2. Code visibility: Will it be private, open source, or publicly accessible?
  3. Business model: How does it generate revenue (if applicable)?
  4. Number of projects: How many applications/sites will use the product?
  5. Organizational context: Personal, freelance, company, agency?

We're here to help you choose the right license for your specific case.

Specific Use Cases

Frequent Question: I work at a company and we develop internal applications

Situation: "I develop applications for my company's internal staff. We don't sell the software, it's only used by our employees."

Answer:

  • One internal application → Commercial License
  • Multiple internal applications → Unlimited License (more economical)

Even though you don't sell the software to the public, corporate use is considered commercial.

Frequent Question: I'm a freelancer and I develop for clients

Situation: "I develop websites for different clients as a freelancer."

Answer:

  • Single client/project → Commercial License
  • Multiple clients/projects → Unlimited License (recommended)

Each client project requires its own commercial license, or you can get an Unlimited license to cover all your work.

Frequent Question: I want to develop an open source project

Situation: "I'm creating an open source library/tool that I want to share publicly."

Answer:
Open source projects CANNOT use the Personal License. You need:

  • One open source project → Commercial License
  • Multiple open source projects → Unlimited License

This applies even if your open source project doesn't generate revenue, because the code is public.

Frequent Question: I have a personal project that I might monetize later

Situation: "It's personal now, but I plan to charge for it in the future."

Answer:
If you plan to monetize, start directly with a Commercial License. If you change plans in the future, you'll need to upgrade your licenses

Frequent Question: My personal project is in a private repository

Situation: "It's my learning project, the code is on GitHub but the repo is private."

Answer:
Perfect, the Personal License is ideal for this case. As long as the repository remains private and you don't generate revenue, you can use the Personal License.