> For the complete documentation index, see [llms.txt](https://onza.gitbook.io/onza/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://onza.gitbook.io/onza/onza-nexus/license-levels-and-pricing.md).

# License Levels & Pricing

ONZA NEXUS offers a range of **Standard** and **Institutional** software-access licenses.

Each license is activated through a **one-time License Activation Fee** and has a maximum term of **12 months**.

### 📋 Standard Licenses

| **License**            | **Activation Fee** | **Term**  | **Maximum Contractual Gross Credit Ceiling** |
| ---------------------- | ------------------ | --------- | -------------------------------------------- |
| **Nexus Access**       | $125               | 12 months | $187.50                                      |
| **Nexus Core**         | $650               | 12 months | $975                                         |
| **Nexus Advanced**     | $1,300             | 12 months | $1,950                                       |
| **Nexus Professional** | $3,500             | 12 months | $5,250                                       |
| **Nexus Enterprise**   | $5,000             | 12 months | $7,500                                       |

### 🏢 Institutional Licenses

| **License**                 | **Activation Fee** | **Term**  | **Maximum Contractual Gross Credit Ceiling** |
| --------------------------- | ------------------ | --------- | -------------------------------------------- |
| **Nexus Institutional I**   | $10,000            | 12 months | $15,000                                      |
| **Nexus Institutional II**  | $25,000            | 12 months | $37,500                                      |
| **Nexus Institutional III** | $50,000            | 12 months | $75,000                                      |

Institutional licenses are subject to **enhanced admission and verification requirements** before activation.

### 📈 Maximum Contractual Gross Credit Ceiling

Each ONZA NEXUS license has a maximum contractual gross credit ceiling equal to **1.5× the License Activation Fee**.

The ceiling **includes the activation value itself**. It is not an additional amount added on top of the activation value.

For example:

**$1,000 activation value → maximum contractual gross credit ceiling of $1,500**

The **1.5× ceiling is a contractual maximum only**. It is **not a target, expected outcome, promised result, or guaranteed amount**.

Actual credits depend on system performance, are **variable**, may be **zero**, and the maximum ceiling may never be reached.

### ⏳ License Duration

Each license operates for a maximum of **12 months**.

> A license reaches the end of its active cycle when either:
>
> * The **12-month term is completed**, or
> * The **maximum contractual gross credit ceiling is reached**
>
> **whichever occurs 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://onza.gitbook.io/onza/onza-nexus/license-levels-and-pricing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.