> For the complete documentation index, see [llms.txt](https://mercure-technologies.gitbook.io/xprem/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mercure-technologies.gitbook.io/xprem/3-0-x/references/open-core-and-licensing.md). # Open core and licensing ## Open core and licensing Expo Open OTA is an open-core project maintained by Axel Marciano (Mercure Technologies). \ \ Everything you need to run over-the-air updates in production is free and MIT-licensed: publishing updates, release channels, branches, rollbacks, every storage backend and CDN integration, the dashboard, Prometheus metrics.\ This is the core of the project, and it will always remain open source. #### Enterprise features Alongside the core, we are building a commercial Enterprise Edition for advanced and organization-level needs. The following capabilities are planned or under development as paid features: * Analytics beyond the built-in Prometheus metrics * Advanced update targeting, such as regional or user-group rollouts * API key scoping per release channel * SSO / SAML authentication * Audit logs * IP whitelisting * Expo Observe Support * Automatic rollbacks * Priority support This list will evolve as the product grows, but one promise never changes: a feature released under the MIT license will never move to the commercial edition. The core only grows. #### How it works in practice Enterprise code lives in `ee/` directories of the repository, under a commercial license, while everything outside them remains MIT. Enterprise features ship in the same binary and Docker image as the core and stay dormant until a license key is activated. License keys are verified offline: your server never contacts an external service, sends no telemetry, and keeps working in air-gapped environments. #### Contributing and the open-core boundary If you plan to contribute a significant feature, please open an issue on the [GitHub repository](https://github.com/mercuretechnologies/expo-open-ota) before writing code, so we can tell you early whether your idea overlaps with planned enterprise features. The full contribution policy lives in the repository's `CONTRIBUTING.md` file. #### Interested in the Enterprise Edition? If some of these features matter to your organization, reach out at [contact@mercuretechnologies.com](mailto:expoopenota@gmail.com). Early feedback shapes what we build first. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://mercure-technologies.gitbook.io/xprem/3-0-x/references/open-core-and-licensing.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.