OCL License

Oxiverse Community License (OCL) v1.2

Copyright © 2026 Likhith Sai Seemala Source-Available • Non-Commercial Community Use • Paid API (Free Tier) • Paid Closed-Source Self-Hosting Commercial License Available • Full-Source Self-Hosting Free (OCL or OSI-Approved OSS) • Privacy-by-Design Required

Note on terminology. OCL is a source-available license, not an OSI-approved open source license: it permits commercial self-hosting only on the paid closed-source path or the free full-source path (Section 2A(b)). When this document refers to the "free full-source path," it means releasing the ENTIRE stack under OCL or an OSI-approved open source license — not that OCL itself is OSI-approved open source.

Definition of "Oxiverse Software." "Oxiverse Software" (or "the Software") means the Oxiverse codebase and all Oxiverse services — current and future — that Licensor releases under this License, including but not limited to RAVANA, IntentForge, and any successor or additional services. New Oxiverse services are automatically covered by OCL; no separate agreement is needed for each.

1. Grant of License

Subject to the terms of this License, Likhith Sai Seemala ("Licensor") grants you a worldwide, non-exclusive, non-transferable, non-sublicensable license to:

  • (a) use, copy, modify, and run the Software;
  • (b) create derivative works of the Software;
  • (c) share the Software and derivative works, for Non-Commercial Purposes only.

Derivative works created under this License must also be distributed under OCL v1.x and may not be relicensed under more permissive terms.

For the avoidance of doubt, this Section 1 distinguishes between two scenarios:

  • (i) Core Modifications. Modifying, forking, extending, or creating derivative works of the Software's source code (including its cognitive architecture, components, and any part of the codebase) constitutes a derivative work and must remain under OCL v1.x. Such modifications may not be relicensed, sublicensed, or distributed under different terms.

  • (ii) Service Consumption. Independently developed applications, products, or services that merely consume, interact with, or depend on the Software through its hosted services, APIs, or platform interfaces—without copying, modifying, or incorporating the Software's source code—are not considered derivative works of the Software, and are not subject to OCL's licensing restrictions. You may license, distribute, and monetize your independent product under any terms you choose—including a proprietary or closed-source license, an OSI-approved open source license (e.g., MIT, Apache 2.0, GPL), or OCL v1.x. No Commercial License from Licensor is required (see Section 2A(a)).

2. Non-Commercial Use Definition

"Non-Commercial Purpose" means use that is:

  • Personal, non-monetized experimentation
  • Educational or academic instruction
  • Academic or non-profit research
  • Internal evaluation within a non-revenue-generating organization
  • Open research or community learning projects

Non-Commercial Purpose expressly excludes:

  • Selling, licensing, or monetizing the Software or derivatives
  • Offering the Software as a hosted service (SaaS, API-as-a-Service, etc.) except as expressly permitted in Section 2A(a) (public API use, paid subscription, no separate license needed) and Section 2A(b-i) (closed-source self-hosting under a paid Commercial License) or Section 2A(b-ii) (full-OSS self-hosting)
  • Integrating the Software into a paid product, platform, or commercial offering except as permitted in Sections 2A(a) and 2A(b)
  • Using the Software for commercial consulting, client work, or agency deliverables
  • Any activity that generates revenue, directly or indirectly, using the Software except as permitted in Sections 2A(a) and 2A(b)

2A. Commercial Use Clarifications

The following principles resolve ambiguity between "Non-Commercial Purpose" and "Commercial Purpose":

  • (a) Hosted Services & API Use — paid subscription; no separate OCL Commercial License required for independent products. Oxiverse operates a hosted search interface (free for personal and research use) and programmatic API access offered under a paid subscription (pricing published on our website; a free tier may be offered at Licensor's discretion). Independently developed applications, products, or services that consume Oxiverse's hosted APIs, platform interfaces, or services (Section 1(ii)) may do so for any purpose—commercial or non-commercial—without a separate OCL Commercial License from Licensor. You pay the applicable API subscription; beyond that, no commercial-licensing gate applies. Revenue generated by such an independent product belongs to that product and is not "revenue generated through Oxiverse services" for the purposes of this License. Such commercialization expressly includes direct and indirect monetization of the independent product—advertising, affiliate or referral links, sponsorships, and the like—without a Commercial License. Your independent product may be relicensed under any terms you choose (Section 1(ii)). Nothing in this subsection grants any right to the Software's source code; it concerns only consumption of the hosted service/API. The hosted service/API itself is a separate paid offering and is not licensed under OCL. For enhanced commercial use of the hosted services — such as white-label rights, redistribution of the hosted service, SLA, or custom integration — a separate paid Commercial License is available (Section 2A(d)).

  • (b) Self-Hosted Commercial Use — PAID Commercial License for closed-source; FREE if fully open-sourced. Running, deploying, or operating the Oxiverse Software (the codebase comprising all Oxiverse services, including RAVANA and IntentForge) on your own infrastructure for a commercial purpose is governed by two paths:

    • (b-i) Closed-Source Self-Hosting (PAID). You may self-host the Software commercially in closed-source / proprietary form only under a paid Commercial License obtained from Licensor (Section 3). This is the commercial license Oxiverse sells. It permits you to operate the Oxiverse Software (any Oxiverse service) commercially without releasing your deployment's source.
    • (b-ii) Full-Source Self-Hosting (FREE). You may self-host the Software commercially without a paid Commercial License if you release the ENTIRE stack of that deployment under OCL v1.x or an OSI-approved open source license (e.g., MIT, Apache 2.0, GPL) — with no proprietary, closed-source, premium-only, or open-core components (see Section 3A). This path is free and does not require a paid license. "ENTIRE stack" is precisely defined in Section 3A.
    • Self-hosting for Non-Commercial Purposes (Section 2) remains freely permitted regardless of (b-i)/(b-ii).

  • (c) Funds vs. Revenue. "Funds" received by a project—including donations, grants, sponsorships, crowdfunding, and institutional or organizational funding—are treated as Non-Commercial, provided they are not consideration paid by users for access to the Oxiverse Software or its services. "Commercial Purpose" is not limited to direct charges: it includes both direct and indirect revenue generated by offering the Oxiverse Software or its services to end users, such as (i) access or subscription fees for a self-hosted or hosted Oxiverse instance; (ii) reselling Oxiverse as a service; (iii) advertising or sponsored placements served through or on the Oxiverse service; (iv) affiliate or referral links monetized via the Oxiverse service; or (v) any other monetization derived from end users of the Oxiverse Software or services. This definition applies to use of the Oxiverse Software itself and does not reach independent API/service-consumer products under Section 2A(a), which may commercialize—including via advertising or affiliate links—without a Commercial License. A self-hosted deployment that complies with Section 2A(b-ii) and Section 3A (full-OSS) may generate revenue freely.

  • (d) Commercial Licenses for Self-Hosting & Hosted-Service Use — AVAILABLE (paid). Oxiverse sells paid Commercial Licenses for commercial use of its Software and services. The primary commercial license is the closed-source self-hosting license (Section 2A(b-i)): it grants the right to operate the Oxiverse Software (any Oxiverse service) commercially on your own infrastructure in closed/proprietary form. Paid Commercial Licenses may also cover enhanced hosted-service use — white-label rights, redistribution of the hosted service, SLA, priority support, and custom feature development/integration. A Commercial License governs your use of Oxiverse's offerings and your independent product; for the closed-source self-hosting license, it expressly permits operating the Software without open-sourcing your deployment. To inquire, contact [email protected].

  • (d-i) Open-Source Projects — optional FREE written confirmation of compliance. Open-source projects that wish to self-host commercially under the full-OSS terms of Section 2A(b-ii), or use the API (Section 2A(a)), may request a FREE written confirmation that their intended use complies with this License. To obtain it, the project must have contacted Oxiverse ([email protected]) and met the applicable conditions (notably, for self-hosting, demonstrating the ENTIRE stack is open-sourced under OCL with no open-washing per Section 3A). This confirmation confers no rights beyond those already granted by OCL and grants no proprietary, closed-source, or self-hosting-exempt permissions. It is documentation of compliance, not a license — the open-source self-hosting path is already free without it.

3. Commercial Use — What Requires Permission and What Does Not

  • No separate OCL Commercial License is required to use Oxiverse's API or hosted services for any purpose, including commercial purposes (Section 2A(a)) — you simply pay the applicable subscription (a free tier is available for personal and research use). Your independent product is not a derivative work of the Software.
  • Self-hosted commercial deployment is permitted under either: (i) a paid Commercial License that allows closed-source operation (Section 2A(b-i)); or (ii) the free full-OSS path where the entire stack is open-sourced under OCL with no open-washing (Section 2A(b-ii) & 3A). Self-hosting for Non-Commercial Purposes needs no license (Section 2).
  • Closed-source self-hosting requires a paid Commercial License. A closed-source/proprietary self-hosting deployment is permitted only under a paid Commercial License obtained from Licensor (Section 2A(b-i), Section 2A(d)). The full-OSS self-hosting path (Section 2A(b-ii) & 3A) is the free alternative.
  • Licensor DOES issue paid Commercial Licenses, including the closed-source self-hosting license (Section 2A(b-i)) and enhanced hosted-service licenses (white-label, redistribution of the hosted service, SLA, support, custom development) — these are available to any party on request (Section 2A(d)). The only self-hosting path that is free is the full-OSS one (Section 2A(b-ii) & 3A); a closed-source self-hosting license is a paid product, not a free grant.

To confirm compliance for an open-source project, contact: [email protected].

3A. Open-Washing Prohibition

"Open-washing" means presenting a deployment as "open source" or "OSS" while withholding material parts of the software that constitute or are required to operate the service. Open-washing includes, without limitation:

Definition — "ENTIRE stack." For the full-source self-hosting path (Section 2A(b-ii)) and this open-washing prohibition, "ENTIRE stack" means all software components authored by, derived from, or incorporating the Oxiverse Software that are necessary to operate the Oxiverse-based service — including all Oxiverse services (such as RAVANA and IntentForge), your modifications, extensions, and any glue code required to make the service function.

Safe Harbor — components that are NOT part of the "ENTIRE stack" (do not need to be open-sourced). The following are explicitly outside the scope of the ENTIRE stack and may remain in their normal proprietary or separately-licensed form:

  • Deployment scripts, CI/CD pipelines, and configuration files that merely deploy or configure the service without modifying its runtime behavior;
  • Authentication / authorization proxies that sit in front of Oxiverse and do not modify its source code;
  • Monitoring, logging, and alerting systems that are not tightly coupled to Oxiverse's internal state;
  • Custom business logic that calls Oxiverse APIs but does not embed Oxiverse code (such use is an independent API-consumer product under Section 2A(a));
  • Any code that would continue to function if Oxiverse were replaced by a different service;
  • Standard off-the-shelf infrastructure (operating systems; databases/datastores such as PostgreSQL, Redis; web servers/reverse proxies such as Nginx; hosting/infra such as AWS, Cloudflare; external APIs such as OpenAI, Stripe, S3); general-purpose libraries/frameworks merely used; and general-purpose configuration-management or IaC tools (e.g., Ansible, Terraform) reused across multiple projects.

Examples — what IS part of the "ENTIRE stack" and MUST be open-sourced under the free path. For clarity:

  • Orchestration scripts, deployment automation, and infrastructure-as-code specifically tailored to operate this Oxiverse deployment;
  • Authentication / authorization middleware that directly interfaces with Oxiverse to control access;
  • Custom API gateways or proxies that transform, route, or augment Oxiverse's core functionality;
  • Monitoring agents or logging pipelines tightly coupled to Oxiverse's internal state;
  • Any code that would need to be modified or replaced if Oxiverse were upgraded to a new version.

It does NOT require you to open-source independent third-party components that are not derived from the Software (see the Safe Harbor list above). You may deploy the Oxiverse-based service alongside such components in their normal proprietary or separately-licensed form.

  • (a) Open-Core: publishing some components as open source while keeping other components required to run or meaningfully use the service under proprietary or closed terms;
  • (b) Source-Available-but-Restricted: releasing code that cannot be freely used, modified, and redistributed under OCL or an OSI-approved open source license (such as MIT, Apache 2.0, or GPL);
  • (c) Premium/Closed Tiers: offering a "community" open edition alongside a proprietary paid edition that contains functionality necessary to operate the service;
  • (d) Hidden Proprietary Dependencies: requiring proprietary binaries, keys, services, or APIs that are not themselves available under OCL to operate the deployment.

Any deployment offered under the self-hosted commercial permission of Section 2A(b) MUST be genuinely, completely open: the complete corresponding source of the ENTIRE stack — including all modifications to the Oxiverse Software, all Oxiverse services, and every component that constitutes the service you operate — must be available under OCL or an OSI-approved open source license. Failure to do so is open-washing, constitutes a material breach of this License, and automatically terminates the commercial permission (and this License) under Section 9 — except that, in the case of a good-faith dispute over what constitutes the ENTIRE stack, Licensor will first provide written notice and the Licensee has thirty (30) days from receipt to remedy the disputed scope; this cure period applies only to scope disputes and does not apply to deliberate open-washing, privacy breaches, or other material breaches.

4. Redistribution & Source Availability

If you distribute the Software or derivative works (even for Non-Commercial Purposes):

  • (a) You must include this License in full, unmodified, with all copyright notices intact;
  • (b) You must make the complete corresponding source code available under the same OCL v1.x terms;
  • (c) You may not sublicense, relicense, or distribute under different terms.

If you operate the Software commercially under Section 2A(b), the ENTIRE stack you operate must remain available as complete corresponding source under OCL or an OSI-approved open source license (see Section 3A).

5. Privacy-by-Design Requirement

All derivative works, modifications, or redistributions of the Software must uphold privacy-by-design as a non-negotiable baseline:

  • (a) No Unauthorized Data Collection: You may not add tracking, telemetry, analytics, or user data collection mechanisms without explicit, informed, opt-in user consent.
  • (b) Data Minimization: No telemetry, analytics, or user data may be collected except for crash logs and diagnostic data. Such logs must be stored locally by default. If the user chooses to transmit logs to a third-party service (including Oxiverse-operated services, or a self-hosted alternative), they must obtain explicit, informed, opt-in consent from the end-user. The Software must provide a clear mechanism to disable all log transmission entirely.
  • (c) User Control: Users must retain the ability to view, export, and delete any data generated or stored by the Software.
  • (d) Enhancements Encouraged: You are free—and encouraged—to enhance privacy protections beyond this baseline (e.g., end-to-end encryption, local-first architecture, zero-knowledge proofs).
  • (e) Transparency & Mandatory Privacy Policy: Any entity distributing the Software or derivative works (commercial or non-commercial) must publish a human-readable privacy policy that: (i) discloses use of Oxiverse services; (ii) states that no user data is stored except crash logs, which may be transmitted (if the user opts in) to Oxiverse-operated services or a user-selected third-party alternative, and that transmission can be entirely disabled; (iii) is prominently linked in the Software and all distribution channels.

Violation of this Privacy Requirement constitutes a material breach of this License and triggers automatic termination under Section 9.

6. Contributions

Any contribution submitted to Licensor for inclusion in the Software shall be under the terms and conditions of this License. Contributions become part of the Software licensed under OCL v1.x and may not be relicensed by any party outside the terms of this License. By submitting a contribution, you represent that:

  • (a) You have the right to license it under OCL v1.x;
  • (b) You grant Licensor a perpetual, worldwide, non-exclusive license to use, modify, and distribute your contribution under this License.

Compensation: Contributions are voluntary. Oxiverse does not pay contributors for code, documentation, or other submissions. By submitting a contribution you agree it is provided without expectation of payment.

Contributor Monetization: Contributors may monetize their own use of the Software exactly like any other party, via either path in Section 2A(b):

  • (i) Buy a paid closed-source Commercial License (Section 2A(b-i)) — contributors are eligible for an extra contributor discount; contact [email protected]; or
  • (ii) Self-host commercially for FREE by releasing the ENTIRE stack under OCL or an OSI-approved open source license with no open-washing (Section 2A(b-ii) & 3A). Contributors are not granted a free closed-source self-hosting license; the discount applies only to the paid license.

Oxiverse's use of contributions. Oxiverse may use, modify, and distribute your contribution in its own offerings without additional compensation. Oxiverse does not, however, place externally-contributed code into any deployment that remains closed-source / proprietary. Accordingly, contributed code is included in Oxiverse's offerings only where the Oxiverse service incorporating it is released under OCL or an OSI-approved open source license (Section 2A(b-ii) & 3A). Oxiverse operates its proprietary hosted service/API and sells paid Commercial Licenses under its own rights as Licensor using Oxiverse-authored code; those offerings are outside the scope of this restriction (see Section 2A(a): the hosted service/API is a separate paid offering and is not licensed under OCL).

Contributor Rights. In addition to the rights above, every contributor receives the following benefits with respect to their own contribution:

  • (i) Royalty-free reuse of your own contribution. You retain the right to use, modify, and redistribute your contributed code in any context (your own projects, other products, commercial or non-commercial) without royalty or further permission from Oxiverse. This right covers your contribution only and does not grant any right to the rest of the Oxiverse Software or to other contributors' work.
  • (ii) Credit in distributions. Oxiverse will credit you in releases and public distributions that include your contribution, subject to a privacy opt-out (a contributor may request omission of their name by contacting [email protected]). Credit obligations apply only to distributions that contain the contribution.
  • (iii) Additional licensing of your contribution. You may license your own contribution under other terms (including an OSI-approved open source license such as MIT, Apache 2.0, or GPL) separately and elsewhere. Any such separate licensing is additional only: your grant of OCL rights to Oxiverse in subsection (b) is perpetual and irrevocable and is not withdrawn by any other license you grant.
  • (iv) Royalty-free commercial reuse of your own contribution. Contributors retain royalty-free rights to use their own contribution in their own separate commercial works without a paid Commercial License, provided the work does not incorporate other Oxiverse services beyond that contribution. For commercial self-hosting of the full Oxiverse stack (including other contributors' code) in closed-source form, contributors remain eligible for the paid closed-source Commercial License at the contributor discount in subsection (i) above — there is no free closed-source self-hosting grant.

All Oxiverse services and the core Oxiverse Software — including its cognitive architecture (RAVANA, RLMv2, ConceptGraph, and successor components) — remain under OCL v1.x and may not be relicensed, sublicensed, or closed-sourced by any party, including contributors. Only derivative works and original extensions created on top of the core may be commercialized under proprietary terms, subject to a valid paid Commercial License (Section 2A(b-i) & 2A(d)).

7. Patent Grant

Subject to the terms of this License, Licensor grants Licensee a non-exclusive, worldwide, royalty-free license under any patent claims licensable by Licensor that are necessarily infringed by the Software alone, solely for Non-Commercial Purposes and for the permitted commercial uses in Sections 2A(a) and 2A(b). This patent grant terminates automatically upon any commercial use outside the permissions of this License (i.e., without a paid Commercial License where one is required, or in violation of the open-washing prohibition).

8. No Warranty

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT. IN NO EVENT SHALL THE LICENSOR BE LIABLE FOR ANY CLAIM, DAMAGES, OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF, OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

9. Termination

This License automatically terminates if you violate any of its terms. Upon termination:

  • (a) All rights granted to you cease immediately;

  • (b) You must cease all use, distribution, and development of the Software;

  • (c) Licensor reserves the right to pursue legal remedies for unauthorized commercial use or privacy violations.

  • (d) Good-faith scope dispute cure period. Notwithstanding the automatic-termination language above, where the dispute concerns only the scope of the "ENTIRE stack" under Section 3A (and not deliberate open-washing, privacy breaches, or other material breach), Licensor will first provide written notice identifying the disputed components, and the Licensee has thirty (30) days from receipt to remedy the disputed scope by bringing the deployment into compliance. Termination does not take effect for that dispute during the cure period. This subsection does not limit Licensor's right to terminate immediately for deliberate open-washing or privacy violations.

A violation of Section 3A (open-washing) or Section 2A(b) (closed-source self-hosting) is a material breach that triggers immediate termination.

10. License Versions

Licensor may publish updated versions of this License (for example, v1.2, v1.3). A project is governed by the specific version it adopted at the time of first use, and that version — and only that version — defines its rights and obligations. Existing projects may continue indefinitely under the version they adopted; they are never required to upgrade. New projects should use the latest published version, and any project may voluntarily adopt a newer version by clearly indicating that it does so.

Each version is self-contained. Amendments in a later version — including any clarifications to the open-washing prohibition (Section 3A) or the closed-source self-hosting requirement (Section 2A(b-i)) — do not retroactively alter the obligations of a project that lawfully adopted an earlier version, unless that project chooses to adopt the later version.

11. Governing Law & Jurisdiction

This License shall be governed by and construed in accordance with the laws of the Republic of India, without regard to its conflict of law principles. Any disputes arising under or in connection with this License shall be subject to the exclusive jurisdiction of the courts located in Visakhapatnam, Andhra Pradesh, India.

Quick FAQ

Q: Can I use OCL software for my student project or portfolio? Yes. That's a Non-Commercial Purpose. Just keep the license intact, share source, and uphold privacy-by-design.

Q: Can I add analytics to a modified version? Not without explicit, opt-in user consent. It must also comply with the Privacy Requirement, including minimization, transparency, and user control.

Q: What if I enhance privacy (for example, end-to-end encryption)? Encouraged. You can go beyond the baseline. Just document your changes and keep the license.

Q: What's the difference between "modifying the core" and "building on top of services"? Modifying the core means changing the actual Oxiverse source code (forking, patching, extending components). Those changes must stay OCL. Building on top of services means creating your own independent application that uses Oxiverse's APIs or platform—your app is separate and can be relicensed however you choose.

Q: If I build a commercial app that uses the Oxiverse API, does my app need a Commercial License or OCL? No. The Oxiverse API is a paid subscription service (with a free tier for personal/research use); you pay the subscription to use it. Building an independent product on top of the API does NOT require a separate OCL Commercial License, and your app is not a derivative work of the Oxiverse Software (Section 1(ii)). You may license your product under any terms you choose—including proprietary/closed-source, OSI open source (MIT, Apache 2.0, GPL), or OCL v1.x (Section 2A(a)).

Q: Does receiving donations, grants, or sponsorships make my Oxiverse-based project "commercial"? No. Funds such as donations, grants, sponsorships, and crowdfunding are treated as Non-Commercial, provided they are not payment from users for access to the Oxiverse Software or its services (Section 2A(c)). "Commercial" is broader than selling access: it also covers indirect monetization of the Oxiverse service—such as ads, sponsored placements, or affiliate links served through it—not just direct fees.

Q: Can I SELF-HOST an Oxiverse service (e.g. RAVANA or IntentForge) and sell access to it? Two ways: (1) Closed-source — buy a paid Commercial License from Oxiverse (Section 2A(b-i)); this is the commercial license we sell and it lets you operate the Oxiverse Software (any Oxiverse service) commercially without open-sourcing. (2) Full-source — release the ENTIRE stack under OCL or an OSI-approved open source license (no open-core, no open-washing) for free (Section 2A(b-ii) & 3A). If you don't want to pay and don't want to open-source, use the paid Oxiverse API subscription from your own independent app instead (Section 2A(a)).

Q: If I buy a Commercial License from Oxiverse, does that let me self-host any Oxiverse service (e.g. RAVANA, IntentForge) closed-source? Yes. A paid Commercial License from Oxiverse is exactly what grants the right to self-host the Oxiverse Software (any Oxiverse service) commercially in closed-source / proprietary form (Section 2A(b-i)). That is the commercial license Oxiverse sells. It covers use of the Software on your own infrastructure; it also covers enhanced hosted-service use (white-label, redistribution, SLA, support) where applicable. A full-source self-hosting deployment under Section 2A(b-ii) needs no paid license.

Q: What counts as "open-washing" and why is it prohibited? Open-washing is pretending to be open source while hiding parts. Examples: open-core (some parts open, key parts closed), source-available-but-restricted, premium closed tiers with needed functionality, or hidden proprietary dependencies. Any self-hosted commercial deployment under the FREE full-source path (Section 2A(b-ii)) must release the COMPLETE stack under OCL or an OSI-approved open source license. Open-washing is a material breach and terminates the license (Section 3A). Note: a paid closed-source self-hosting license (Section 2A(b-i)) is permitted and is not open-washing.

Q: I run an open-source project and want to generate revenue through Oxiverse — what do I need? If you only consume the API: pay the subscription (a free tier covers personal/research use); no separate OCL commercial license is required (Section 2A(a)). If you self-host commercially: you can either (i) buy a paid Commercial License for closed-source operation (Section 2A(b-i)), or (ii) release the ENTIRE stack under OCL or an OSI-approved open source license (no open-washing) for free (Section 2A(b-ii) & 3A). For enhanced hosted-service commercial use (white-label, redistribution, SLA), a paid Commercial License is also available from [email protected] (Section 2A(d)); open-source projects may also request a FREE written confirmation of compliance.

Q: If I fork Oxiverse and add features, what license applies to my fork? OCL v1.x. Modifications to the core codebase must remain under OCL (see Section 1(i)). You cannot relicense a fork under different terms.

Q: If I contribute code to Oxiverse, can I later relicense my contribution? No. Contributions become part of the Software and are licensed under OCL v1.x (see Section 6). They may not be relicensed by you or others outside the terms of this License. Oxiverse may use your contribution in its offerings only under the conditions in Section 6 — it does not place contributed code into a closed-source deployment.

Q: How do I get a Commercial License? Oxiverse sells paid Commercial Licenses. The primary one is the closed-source self-hosting license (Section 2A(b-i)) — it lets you self-host the Oxiverse Software (any Oxiverse service) commercially without open-sourcing (this is the paid product). Paid licenses also cover enhanced hosted-service use (white-label, redistribution, SLA, custom integration) — email [email protected] (Section 2A(d)). The alternative to paying: release the ENTIRE stack under OCL or an OSI-approved open source license (Section 2A(b-ii) & 3A), which is free. There is no free closed-source self-hosting license.

For licensing inquiries: [email protected]