Skip to content

FlyEnv Licensing Guide

The FlyEnv licensing model provides a paid software license for users who need continued access to premium features while helping fund ongoing development. Our goal is not to block core local development, but to make the long-term maintenance of an independent developer tool sustainable.

Activating a license gives you licensed access beyond the evaluation limits below. Community code contributions and original educational content may also qualify for a manually reviewed license.

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. A paid license removes evaluation limits for premium tools and helps keep FlyEnv maintained across macOS, Windows, and Linux.

2. How to Get Licensed

We offer one paid purchase path and two manually reviewed community paths:

Option A: Purchase a Personal License

  • License price: $10 USD for a FlyEnv Personal License.
  • License scope: One active device, with device transfer supported through license management.
  • Premium access: Removes the evaluation limits listed above for the licensed device.
  • Payment processor: Paddle may process checkout, taxes, receipts, invoices, and payment-related support.

After purchasing, keep your Paddle order ID and submit it with your license request in the app. To purchase a license, go to the License page.

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:

Video & Creative Content:

Tech Communities & Engineering Blogs:

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 community contribution records here: Community records

Additional Guidelines:

  • Please submit your license request shortly after publishing your content.
  • Since FlyEnv evolves rapidly with frequent new features and improvements, promotional content published more than 3 months ago may no longer be eligible.
  • Please only submit original content created by yourself. Reposting or submitting someone else’s content is not eligible.
  • Each article, video, or piece of promotional content is eligible for one license only.

3. Request & Activation Process

Once you have completed any of the steps above, follow these instructions to activate your license:

  1. Provide Proof: In the "Message" field of the application, include:
  • License purchasers: Your Paddle order ID or receipt email.
  • Contributors: The link to your GitHub Pull Request.
  • Promoters: The link to your post, video, or shared content.
  1. Submit: Click the "Request License" button.
  2. 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":
  1. Locate your old device's UUID and click "Unbind".
  2. Click "Bind This Device" to activate FlyEnv on your new machine.

Note: GitHub authorization is required to apply for and manage licenses.