> For the complete documentation index, see [llms.txt](https://zynoxdev.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zynoxdev.gitbook.io/docs/escrow-vs-opensource.md).

# Open Source and Escrow

A transparent comparison of Zynox Development package editions

***

## ⚖️ Edition Overview

At **Zynox Development**, we offer products in two distinct tiers to fit server owners of all technical backgrounds:

1. **Escrow (Asset Protected)**: Optimized, budget-friendly edition protected by the official Cfx.re Escrow system.
2. **Open Source (Full Code Access)**: Unrestricted access to the unencrypted source code for custom development and deep framework integrations.

***

## 📊 Feature Comparison Matrix

| Feature                                               |   🔒 Escrow Edition  | 🔓 Open Source Edition |
| ----------------------------------------------------- | :------------------: | :--------------------: |
| **Full Functionality**                                |      ✅ Included      |       ✅ Included       |
| **Config Customization (`config.lua` / `config.js`)** |    ✅ 100% Unlocked   |     ✅ 100% Unlocked    |
| **Locales & Translations**                            |    ✅ 100% Unlocked   |     ✅ 100% Unlocked    |
| **HTML / CSS / Audio Customization**                  |    ✅ 100% Unlocked   |     ✅ 100% Unlocked    |
| **Client / Server Lua Source Code**                   |     🔒 Protected     |    🔓 Fully Unlocked   |
| **Cfx.re Keymaster Account Binding**                  |       Required       |      Not Required      |
| **Custom Event / Export Extensions**                  | Supported via Config |   Full Custom Coding   |
| **Free Updates & Patches**                            |      ✅ Lifetime      |       ✅ Lifetime       |
| **Community & Discord Support**                       |  ✅ Priority Support  |   ✅ Priority Support   |

***

## 💡 Which Edition Should You Choose?

### Choose **Escrow Edition** if:

* You want a plug-and-play solution that works immediately without modifying core logic.
* You only need to configure server settings, colors, sounds, times, and messages in `config.lua` or `config.js`.
* You want the most cost-effective pricing while enjoying official updates.

### Choose **Open Source Edition** if:

* Your server runs heavily customized frameworks or proprietary internal scripts.
* You have a dedicated developer who wants to refactor, add custom database tables, or integrate custom NUI components.
* You do not want any external Keymaster account binding on your server files.

***

## 🔄 Upgrading from Escrow to Open Source

If you initially purchased an Escrow version and later decide you need the Open Source edition:

1. Join the [**Zynox Development Discord Server**](https://discord.gg/zynox).
2. Open an **Upgrade Ticket** with your previous Tebex Transaction ID.
3. Our staff will provide an upgrade discount coupon covering the price difference.


---

# 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://zynoxdev.gitbook.io/docs/escrow-vs-opensource.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.