License & Usage
We want you to build amazing things with Felyra. Our license is designed to be simple, fair, and permissive so you can focus on creating, not worrying about legalities.
This policy applies to all code snippets, components, templates, and assets ("Items") you access on Felyra.
The Short Version
You have a non-exclusive, worldwide license to use Felyra's resources in your personal and commercial projects. You can modify them as much as you like. You generally cannot repackage our code and sell it as a competing product.
What You Can & Cannot Do
✓ What is Allowed
- Personal Projects: Build your portfolio, hobby sites, or passion projects.
- Client Work: Build websites and applications for your clients. You can charge them for your services.
- Commercial Projects: Build SaaS applications, e-commerce stores, or internal tools that you charge users for.
- Modifications: Change the code, combine it, and adapt it to fit your unique design system.
- Unlimited Use: Use the same components across multiple different projects.
✕ What is Not Allowed
- No Reselling: You cannot sell, rent, or sublicense our code as a standalone asset (e.g., selling a "Felyra UI Kit" or a template pack based on our code).
- No Competing Services: You cannot use our components to build a website builder, theme generator, or a competing component library.
- No Public Redistribution: You cannot publish our source code in public repositories (like GitHub) where the primary value of the repository is our code.
- No Account Sharing: Licenses are per-user. You cannot share your login details with other developers or your entire team.
Common Scenarios
Can I use this for a client's website?
Yes. You can use Felyra to build a website for a client. The ownership of the final website belongs to the client, but the license to the underlying Felyra components remains with you (or can be transferred as part of the project usage, provided the client doesn't resell the code itself).
Can I build a SaaS and sell subscriptions?
Yes. You can build a SaaS (Software as a Service) using Felyra components. You are selling access to your application/service, not the code itself, which is perfectly fine.
Can I use this in an open-source project?
Generally, no. If you are building an open-source project where the source code is publicly available, you cannot include Felyra's premium components directly in the repo, as this would allow anyone to download them for free.
Team Usage
Licenses are individual. If you work in a team, each developer who needs access to the Felyra library or tools needs their own account/license.
(We plan to introduce Team Plans in the future to make this easier.)
Updates & Changes
We may update this license from time to time to clarify usage or address new types of products. Any changes will be posted here. Continued use of the library implies acceptance of the new terms.
Still Unsure?
If your use case isn't covered here, just send us an email. We're happy to clarify.
support@felyra.studio