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