Skip to Content
WebF Licensing Guide

WebF Licensing Guide

This document provides a comprehensive overview of WebF’s licensing structure, including the GPL-3.0 license for the Community version and the exceptions that apply to open-source packages.

Overview

WebF uses a dual licensing model:

  1. Community Version - Licensed under GPL-3.0 (Free)
  2. Commercial License - Proprietary license for commercial use (Paid)

GPL-3.0 License (Community Version)

The WebF core packages are licensed under the GNU General Public License version 3.0 (GPL-3.0). This is a copyleft license that requires:

  • Your application’s source code must be made available
  • Your application must also be licensed under GPL-3.0
  • Users must have the right to modify and redistribute your application
  • You cannot distribute through app stores (Apple App Store, Google Play Store) due to their incompatible terms

What the GPL-3.0 Covers

The GPL-3.0 license applies to:

  • End-user applications built with WebF
  • Proprietary software that uses WebF
  • Closed-source products that depend on WebF

If you’re building any of the above, you must either:

  • Open-source your application under GPL-3.0, OR
  • Purchase a Commercial License

GPL-3.0 Exception for Open-Source Packages

WebF provides an important exception to the GPL-3.0 license for open-source packages published to public package registries.

What Qualifies for the Exception?

The GPL-3.0 exception applies to:

✅ Open-source npm packages that:

  • Are published to npmjs.com or other public registries
  • Provide utilities, components, or frameworks for WebF
  • Are licensed under any OSI-approved open-source license (MIT, Apache-2.0, BSD, etc.)
  • Have their source code publicly available

✅ Open-source Flutter packages that:

  • Are published to pub.dev or other public registries
  • Wrap or extend WebF functionality
  • Are licensed under any OSI-approved open-source license
  • Have their source code publicly available

✅ Open-source libraries that:

  • Depend on WebF as a runtime or build dependency
  • Are publicly accessible and freely available
  • Do NOT constitute end-user applications

Examples of Packages That Qualify

Here are practical examples of packages that would qualify for the GPL-3.0 exception:

npm Packages:

{
  "name": "@myorg/webf-react-components",
  "license": "MIT",
  "dependencies": {
    "webf": "^0.x.x"
  }
}
  • React component library for WebF (MIT licensed) ✅
  • Utility functions for WebF DOM manipulation (Apache-2.0 licensed) ✅
  • State management library optimized for WebF (BSD licensed) ✅

Flutter Packages:

name: webf_extensions
version: 1.0.0
license: MIT
dependencies:
  webf: ^0.x.x
  • Flutter widgets that bridge to WebF (MIT licensed) ✅
  • Helper package for WebF integration (Apache-2.0 licensed) ✅
  • WebF plugin system library (BSD licensed) ✅

What Does NOT Qualify for the Exception?

The exception does NOT apply to:

❌ Closed-source applications - Even if they use your open-source package ❌ Proprietary software - Even if distributed through npm/pub.dev ❌ End-user products - Apps that end users directly install and use ❌ Private packages - Packages not publicly available on registries ❌ Internal company libraries - Packages used only within your organization

Important Clarification

If you publish an open-source package under MIT license that depends on WebF, developers using your package must still comply with WebF’s licensing:

  • If they build open-source applications → They can use GPL-3.0
  • If they build proprietary applications → They need a Commercial License

Your package being MIT-licensed does NOT grant Commercial License rights to WebF itself.

Commercial License

For proprietary, closed-source applications, or app store distribution, you need a Commercial License. Commercial licenses:

  • Remove all GPL-3.0 restrictions
  • Allow proprietary, closed-source development
  • Enable distribution through Apple App Store and Google Play Store
  • Provide legal protection and compliance

Commercial License Tiers

  1. Individual/Startup - $99/year (companies with less than 10 employees, less than $1M revenue)
  2. Small Enterprise - $999/year (companies with less than 50 employees, less than $5M revenue)
  3. AI App Builder - $15/app/year (volume discounts available)
  4. Enterprise - Custom pricing (larger organizations)

See the Pricing page for full details.

Licensing Scenarios

Scenario 1: Building a Mobile App for App Stores

Situation: You want to build a mobile app with WebF and distribute it on the Apple App Store.

License Required: Commercial License

Reason: GPL-3.0 is incompatible with Apple App Store terms. You need a Commercial License to distribute on app stores.

Scenario 2: Publishing an Open-Source React Component Library

Situation: You want to create a React component library for WebF and publish it as an MIT-licensed npm package.

License Required: None (Exception applies)

Reason: Open-source packages published to public registries qualify for the GPL-3.0 exception. You can use any open-source license.

Scenario 3: Building an Open-Source Application

Situation: You’re building a free, open-source application with WebF and want to share it on GitHub.

License Required: GPL-3.0 (Free)

Reason: As long as your application is licensed under GPL-3.0 and the source code is available, you can use the Community Version. However, you cannot distribute through app stores.

Scenario 4: Internal Company Tool

Situation: You’re building an internal tool for your company that won’t be distributed externally.

License Required: Depends on your distribution

  • If the tool is never distributed outside your organization → GPL-3.0 may be acceptable
  • If the tool will be used by clients or external users → Commercial License required

Recommendation: Contact sales@openwebf.com to clarify your specific use case.

Scenario 5: Using an MIT-licensed WebF Package in Your App

Situation: Someone published an MIT-licensed npm package that depends on WebF. You want to use it in your proprietary app.

License Required: Commercial License (for WebF, not the package)

Reason: While the npm package is MIT-licensed, your application still uses WebF, which is GPL-3.0. For proprietary apps, you need a Commercial License for WebF itself.

Frequently Asked Questions

Can I contribute to WebF’s development?

Yes! WebF welcomes contributions. By contributing, you agree to license your contributions under GPL-3.0 for the community version, with the understanding that WebF may also use them in commercial versions.

What if I started with GPL-3.0 and want to go commercial?

You can upgrade at any time by purchasing a Commercial License. Contact our sales team to make the transition.

Do I need a separate license for each app?

Yes, each commercial license covers one distinct end-user product. If you have multiple products, you’ll need a license for each.

Who is the AI App Builder plan for?

The AI App Builder plan ($15/app/year with volume discounts) is designed for companies that provide AI-backed app building tools, not for products targeting end users. Examples include platforms like FlutterFlow where users create apps through AI-assisted interfaces.

If you are developing apps using AI and shipping them directly to end-users, this plan is not for you—please choose the Individual/Startup, Small Enterprise, or Enterprise plan instead.

What about apps with in-app mini-apps (like WeChat)?

The Individual/Startup, Small Enterprise, and Enterprise plans do not limit in-app mini-apps. You only need to purchase one license for your main “root” app.

You can let others build mini-apps within your self-contained ecosystem, and it is fully permitted to include AI-generated mini-apps inside your main app.

The AI App Builder plan is only required if you intend to distribute multiple standalone apps to the Apple App Store or Google Play Store.

Can I fork WebF and create my own version?

Under GPL-3.0, you can fork WebF, but your fork must also be GPL-3.0 licensed and you cannot distribute it commercially without following GPL-3.0 terms.

How do I know if my package qualifies for the exception?

Ask yourself:

  1. Is it published to a public package registry (npm, pub.dev)?
  2. Is the source code publicly available?
  3. Is it licensed under an OSI-approved open-source license?
  4. Is it a library/package and NOT an end-user application?

If all answers are YES, it qualifies for the exception.

What protections exist against vendor lock-in and abandonment?

Unlike typical GPL dual-licensing models, our Commercial License includes strong contractual protections:

Price Protection: Your license fees are locked for the entire term including renewals (Section 4(c), 3.5.4(e)). We cannot arbitrarily increase prices on existing customers.

Business Discontinuation: If OpenWebF goes bankrupt, ceases operations, or makes an assignment for creditors, you automatically receive a perpetual, royalty-free license with full source code access (Section 11.4).

Development Abandonment: If we fail to release any updates for 6 consecutive months without notice, you automatically receive the same perpetual license with source code (Section 11.5).

These protections ensure you’re never “stuck” - you always have an exit path with full access to the software and source code. See our Software Agreement for complete details.

Where can I get more help?

For licensing questions or commercial license inquiries:

License Texts

GPL-3.0 License

The full text of the GPL-3.0 license is available at: https://www.gnu.org/licenses/gpl-3.0.html 

Commercial License Terms

Commercial license terms are provided upon purchase. See our Software Agreement for full terms and conditions.

Last updated: December 2024

Last updated on:
Terms of Service