📜 FlyEnv Licensing Guide
The FlyEnv licensing model is designed to sustain the project’s growth while honoring the creator's dedication. Our goal is not to impose restrictions, but to foster a culture of respect for independent development and intellectual property.
Activating a license is a way to acknowledge the work behind FlyEnv. By doing so, you support the project's longevity and contribute to a spirit of mutual trust within the global developer community.
1. Evaluation Version Limitations
FlyEnv remains functional without a license, but the following limits apply to the evaluation version:
- Site Management: Limited to a maximum of 3 local sites.
- AI Assistant: Access to AI-powered features is restricted to a 3-day trial.
- Screenshot Utility: The built-in screenshot tool is limited to a 3-day trial.
- Image Optimizer: The image compression utility is limited to a 3-day trial.
- Future Updates: New premium features may be subject to similar trial periods or limits.
Core runtimes and environment management features will always remain accessible. The license is less about "unlocking software" and more about investing in the tool's future. We believe developer tools should be accessible, so we avoid rigid paywalls. Whether you contribute through a donation, code, or by spreading the word, you are helping us build a faster, leaner development ecosystem.
2. How to Get Licensed
We offer several flexible, community-centric ways to obtain a permanent license:
Option A: Support the Project (Donation)
- Pay What You Want: There is no mandatory minimum for donations.
- Contribution-Based: We recognize that economic situations vary—especially for students—so please choose an amount that feels fair to you.
Option B: Contribute to the Codebase
- Submit a PR: Help improve FlyEnv by submitting a Pull Request on GitHub.
- Every Bit Helps: Whether it’s a major feature or a simple documentation fix, all meaningful contributions qualify for a license.
Option C: Spread the Word (Promotion)
Share your FlyEnv experience on any platform in any language. We value authentic and objective feedback from our users.
Recommended platforms for sharing:
Social Media & Networking:
- X (Twitter): https://x.com
- Threads: https://www.threads.net
- Facebook: https://www.facebook.com
- Instagram: https://www.instagram.com
- LinkedIn: https://www.linkedin.com
Video & Creative Content:
- YouTube: https://www.youtube.com
- TikTok / Reels: https://www.tiktok.com
Tech Communities & Engineering Blogs:
- Reddit (r/webdev, r/programming): https://www.reddit.com
- Product Hunt: https://www.producthunt.com
- Hacker News: https://news.ycombinator.com
- V2EX: https://www.v2ex.com
- Dev.to: https://dev.to
- Medium: https://medium.com
- Hashnode: https://hashnode.com
- Your Personal Technical Blog
Submission Note: Once you’ve shared FlyEnv, simply paste the link to your post, video, or article in the "Message" field within the app's license request section.
You can see examples of how others have supported the project here: Sponsors
3. Request & Activation Process
Once you have completed any of the steps above, follow these instructions to activate your license:
- Provide Proof: In the "Message" field of the application, include:
- Donors: Your name, donation link, or transaction/order ID.
- Contributors: The link to your GitHub Pull Request.
- Promoters: The link to your post, video, or shared content.
- Submit: Click the "Request License" button.
- Review: Most requests are processed within 24 hours.
4. License Management & Device Binding
All FlyEnv licenses are permanent and follow a "one license per machine" policy:
- Device Binding: Each license is tied to a specific hardware UUID.
- Hardware Migration: If you get a new computer, you can transfer your license. Log in via your GitHub account and go to "My Licenses":
- Locate your old device's UUID and click "Unbind".
- Click "Bind This Device" to activate FlyEnv on your new machine.
Note: GitHub authorization is required to apply for and manage licenses.