# Open Core License

*Last updated: May 20, 2025*

GLIK AI follows an **open core licensing model**. This means that select components of the GLIK platform are made available under open source licenses, while other features remain proprietary and are licensed separately for enterprise and commercial use.

This page outlines what is open, what is not, and where to access the relevant licensing terms.

***

### 1. **Legal Entity**

The GLIK AI platform is developed, maintained, and licensed by:

**Rivalz Technologies Ltd.**\
Skeleton Bay Lot, Fish Bay\
Tortola, VG1110\
British Virgin Islands

***

### 2. **Official GitHub Organization**

The source code for open core components is available on the official GitHub profile:

**GitHub Organization:** [github.com/rivalz-glik](https://github.com/rivalz-glik)\
**Repository List:** [github.com/orgs/rivalz-glik/repositories](https://github.com/orgs/rivalz-glik/repositories)

Each open source repository includes a `LICENSE` file in its root directory specifying the applicable license.

***

### 3. **Open Source Components**

The following components of GLIK are expected to be open sourced (subject to phased rollout):

| Component                   | Description                                                | License Type               |
| --------------------------- | ---------------------------------------------------------- | -------------------------- |
| **GLIK Open Core Runtime**  | CLI-based orchestration engine                             | MIT or AGPL (TBD per repo) |
| **DSL Interpreter**         | Parser for GLIK's domain-specific workflow format          | MIT                        |
| **Plugin Registry Format**  | Open plugin schema for third-party integration             | MIT                        |
| **Developer SDKs**          | SDKs for building agent templates and memory-enabled tools | MIT                        |
| **Documentation Templates** | Examples and template agents for open deployments          | Creative Commons or MIT    |

> For each component, refer to the specific repository’s `LICENSE` file for terms and conditions.

***

### 4. **Proprietary / Commercial Components**

The following components are **not** open source and are governed by separate license agreements:

* **GLIK Cloud (Managed SaaS)**
* **Visual App Studio Interface**
* **Enterprise Memory Services (GLIK Knowledge)**
* **Admin Console, Billing, and Team Management**
* **Custom Analytics, Usage Quotas, and Credit Systems**
* **Partner Integration Plugins (unless otherwise stated)**

Use of these features requires a commercial agreement with Rivalz Technologies Ltd. or a valid enterprise license key.

***

### 5. **Community Contributions**

We welcome open source contributions under the terms of our repository contribution guidelines. By submitting a pull request, you agree to license your contribution under the terms specified in the applicable repository.

For contributor inquiries or partnership requests, contact:\
[**opensource@rivalz.ai**](mailto:opensource@rivalz.ai)

***

### 6. **Questions & Licensing Support**

To request an enterprise license, evaluate usage eligibility, or inquire about GLIK open core alignment with your use case, please contact:

[**legal@rivalz.ai**](mailto:legal@rivalz.ai)\
Rivalz Technologies Ltd.\
Skeleton Bay Lot, Fish Bay\
Tortola, VG1110\
British Virgin Islands


---

# Agent Instructions: 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:

```
GET https://docs.glik.ai/legal/open-core-license.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.