Skip to content

Licensing and Distribution

PlatanoGames edited this page Feb 24, 2026 · 9 revisions

Licensing & Distribution

PGX Framework uses an Open Core model with a Source-Available Proprietary license. The full source code is provided to licensees -- this is not obfuscated middleware. You receive the same code the framework authors work with.

Access is granted by invitation to the private GitHub repository. You request access, we verify your identity, and you receive full source code with commit history. This ensures a controlled, professional environment for all licensees.


License Model

PGX is Open Core -- not open source. The Core framework is free for independent developers under the Community tier, with revenue-based licensing for professional studios. Open Core means full source access for everyone, with premium support and services for those who need it.

Tier Revenue Threshold Annual Fee What You Get
Community Under EUR 50,000/year Free Full framework, all updates, community support
Growth EUR 50,000 -- EUR 100,000/year Contact us Full framework + priority support + extended license
Studio Over EUR 100,000/year Contact us Full framework + priority support + custom terms

Revenue means gross revenue from products using PGX -- not total company revenue. If your studio earns EUR 200,000/year but the PGX-based project earns EUR 30,000, you qualify for the Community tier.


Key Terms

What You Receive

  • Invitation to the private GitHub repository -- full commit history, issue tracker, and releases
  • Complete C++ source code for all plugins (not compiled libraries, not bytecode)
  • Full editor tooling source (Slate panels, Content Browser extensions, toolbar integration)
  • All documentation (architecture, usage, testing, extension guides)
  • All engine version updates as they are released

What You May Do

  • Modify freely -- Adapt any part of PGX to fit your project's needs. Add systems, remove systems, override defaults, extend base classes. The Class Override Pattern exists specifically to make this straightforward.
  • Ship products -- Use PGX in any number of commercial or non-commercial products under your license tier.
  • Build vertical extensions -- Create game-specific kits that depend on PGX (e.g., "PGX FPS Kit", "PGX RPG Kit") and sell them. Buyers must hold their own PGX license.
  • Internal tooling -- Use PGX as the foundation for your studio's internal tools and pipelines.

What You May Not Do

  • Redistribute the framework -- You may not share, upload, or distribute PGX source code or compiled binaries, whether modified or unmodified.
  • Create competing frameworks -- You may not use PGX code as the basis for a general-purpose middleware product.
  • Remove attribution -- PGX copyright notices must remain in source files.
  • Sublicense -- You cannot grant PGX access to third parties. Each studio needs its own license.

License Scope

Per-Studio License

A single PGX license covers all team members within one legal entity. There is no per-seat pricing. Whether your studio has 2 people or 50, one license covers everyone.

Multi-Project Use

Your license covers all projects within your studio. Build five games on PGX with one license. The revenue threshold applies to the cumulative gross revenue from all PGX-based products.

Engine Version Coverage

All Unreal Engine version updates are included in every license tier. When PGX adds support for a new UE release, you receive it at no additional cost.


Community Tier Details

The Community tier exists because PGX was born in an independent development context. The framework's design philosophy -- zero-configuration start, progressive disclosure, data-driven architecture -- reflects the needs of small teams who cannot afford dedicated engine programmers.

What "Free" Means

  • Full source code access -- identical to paid tiers
  • All 26 plugins, all 13 production-ready systems
  • All editor tooling (23 panels, 58 Data Asset factories, 26 SVG icons)
  • All documentation (90+ files, bilingual English/Spanish)
  • All future updates and new systems
  • Community support through official channels

What "Free" Does Not Mean

  • No priority support (community channels only)
  • No custom integration assistance
  • No architectural consulting
  • Standard license terms (no custom clauses)

Revenue Tracking

PGX operates on an honor system with annual self-reporting. We do not require financial audits for Community tier users. If your PGX-based products cross the EUR 50,000 threshold, you contact us to upgrade. It is straightforward and transparent.


Growth Tier Details

The Growth tier is designed for studios that have found product-market fit and are scaling. Your PGX-based products generate between EUR 50,000 and EUR 100,000 in annual gross revenue.

Additional Benefits

  • Priority support -- Direct communication channel with the development team
  • Extended license terms -- Broader usage rights for studio-specific needs
  • Early access -- Preview builds of upcoming systems and features
  • Migration assistance -- Help with engine version transitions

Studio Tier Details

The Studio tier serves established studios with PGX-based products generating over EUR 100,000 in annual gross revenue.

Additional Benefits

  • Everything in Growth tier
  • Custom terms -- License clauses tailored to your studio's legal requirements
  • Architectural consulting -- Direct access to framework architects for integration planning
  • Custom system development -- Commissioned development of PGX systems for your specific needs
  • Training -- On-site or remote training for your engineering team
  • SLA -- Service level agreement for response times and issue resolution

Vertical Extensions

Studios can build and sell game-specific extensions that depend on PGX. These are add-on products that provide domain-specific functionality on top of the framework's foundation.

Examples

  • An "FPS Kit" providing weapon management, ballistics, and loadout systems built on PGX's Data Registry and Construction systems
  • An "RPG Kit" providing quest management, dialogue trees, and character progression built on PGX's Save, GameFlow, and Event Handler systems
  • A "Multiplayer Kit" providing session management and state replication built on PGX's Message Bus and GameFlow systems

Requirements

  • The extension must not include PGX source code -- it depends on PGX as a separate product
  • Buyers of your extension must hold their own valid PGX license
  • Your extension's documentation must clearly state the PGX dependency
  • You retain full ownership and revenue rights for your extension

Professional Services

Beyond licensing, Platano Games offers professional services for studios that need hands-on assistance.

Integration Consulting

Architectural review of your project to determine the optimal PGX integration strategy. Which systems to adopt, which to customize, how to structure your game-specific layer on top of PGX.

Custom System Development

Commissioned development of new PGX systems or modifications to existing ones, tailored to your project's requirements. Delivered as source code following PGX conventions.

Team Training

Structured training programs covering PGX architecture, extension patterns, editor tooling, and best practices. Available remotely or on-site. Content adapted to your team's experience level.

Code Review

Review of your PGX-based code for architectural compliance, performance, and best practices. Particularly valuable during pre-production to establish patterns that scale.


Educational Use

Academic Institutions

Universities, colleges, and vocational schools can apply for educational licenses at no cost. The educational license covers:

  • Full source code access for instructors and enrolled students
  • Use in coursework, assignments, and academic projects
  • Use in student portfolios and thesis work
  • Access to documentation and guides

Restrictions on Educational Licenses

  • May not be used for commercial products (student startups must obtain a standard license)
  • Access is limited to the duration of enrollment or employment at the institution
  • The institution must apply through official channels

Student Transition

Students who graduate and wish to continue using PGX in their professional work qualify for the Community tier at no cost (assuming they meet the revenue threshold). There is no gap in access.


Why This Model?

Sustainability

Fully open source frameworks for Unreal Engine face a fundamental challenge: UE5 development requires significant expertise and continuous maintenance as the engine evolves. The Open Core model solves this -- the foundation is free and source-accessible, while revenue from professional tiers funds sustained development indefinitely.

Transparency

You always know what you are paying for and why. The revenue thresholds are public. The tier benefits are documented. There are no hidden fees, no per-seat charges, no runtime royalties, no revenue share percentages.

Alignment

The EUR 50,000 threshold means most independent projects will never pay a license fee. The framework's development is funded by studios that are generating meaningful revenue -- studios for whom PGX's value is proven, not speculative.

Developer-First

PGX provides full source code because developers deserve to understand, debug, and modify their tools. Binary-only middleware creates black boxes. Source-available middleware creates partnerships.


Long-Term Vision

PGX is designed as a career-long investment. The framework grows with the Unreal Engine ecosystem, adding new systems and supporting new engine versions. Licensees benefit from continuous improvement across several dimensions:

  • New systems -- The 14 planned L2 plugins (Input, Camera, UI, Ability, Inventory, etc.) are actively being developed
  • Engine updates -- Each new UE release gets a dedicated PGX branch within weeks of stable release
  • Quality improvements -- Static analysis, panel audits, and code quality passes are ongoing
  • Tooling evolution -- Editor panels, Content Browser integration, and developer workflows are continuously refined

The framework's architecture (star topology, data-driven configuration, message-based communication) is designed to accommodate growth without breaking changes. Systems added in year three will follow the same patterns as systems built in year one.


Frequently Asked Questions (Licensing)

Q: Does the Community tier have any functional limitations? No. The source code, plugins, editor tools, and documentation are identical across all tiers. The difference is support level and additional services.

Q: What happens if my revenue crosses EUR 50,000 mid-year? Contact us to upgrade to the Growth tier. We prorate based on the remaining calendar year.

Q: How do I get access to PGX? Request an invitation through our website. We verify your identity and grant access to the private GitHub repository. The public repository contains comprehensive documentation, architecture descriptions, and statistics to help you evaluate before requesting access.

Q: Do I need a license for each UE project? No. One license covers all projects within your studio, regardless of how many games you ship.

Q: What about contractors and freelancers? Contractors working on your PGX-based project are covered by your studio license for the duration of their engagement. They do not need a separate license.

Q: Is there a perpetual license option? The Community tier is perpetual by default. Growth and Studio tiers are annual but include a perpetual fallback -- if you do not renew, you retain access to the version available at the time of expiration, without further updates.


Contact

For licensing inquiries, educational applications, or professional services:

Website: www.platanogames.es

Platano Games -- Professional game development tools and education.


Resumen en Espanol

PGX Framework utiliza un modelo Open Core con licencia Source-Available Propietaria. El acceso se concede por invitacion al repositorio privado de GitHub. El codigo fuente completo se entrega a los licenciatarios -- no es middleware ofuscado.

Tres niveles de licencia:

Nivel Umbral de ingresos Coste anual
Community Menos de 50.000 EUR/ano Gratis
Growth 50.000 -- 100.000 EUR/ano Contactar
Studio Mas de 100.000 EUR/ano Contactar

Los ingresos se refieren a los ingresos brutos de productos que usan PGX, no a los ingresos totales de la empresa. La mayoria de proyectos independientes nunca pagaran una tarifa de licencia.

Que recibes: Codigo fuente completo de los 26 plugins, 13 sistemas production-ready, 23 paneles de editor, 90+ archivos de documentacion, y todas las actualizaciones futuras.

Que puedes hacer: Modificar libremente, enviar productos comerciales, crear extensiones verticales para vender, usar en todos los proyectos de tu estudio.

Que no puedes hacer: Redistribuir el framework, crear frameworks competidores, sublicenciar a terceros.

Uso educativo: Instituciones academicas pueden solicitar licencias educativas sin coste.

Contacto: www.platanogames.es

Clone this wiki locally