---
title: "License — quario"
description: "What a quario license grants: free evaluation, one license per production deployment, unlimited users, agents and renders, and where OEM begins."
url: "https://getquario.com/license"
---

# Quario License Agreement

DRAFT This page is a working draft, not a final legal document. Don't rely on it for compliance or procurement review.

What a quario license grants, what it doesn't, and where the line between deploying the engine and distributing it falls.

LAST UPDATED  ·  October 2026

> **In short:** Quario is commercial software with visible source. You may evaluate it and develop with it free, for as long as you like. The Software marks output that no license key covers. Each production deployment needs one license key. A key covers one year of releases, and those releases stay licensed for good. This summary is not the license. The full terms below govern.

Version 1.1, October 2026

This agreement is between you and Webstronauts, trading as Quario, established in the Netherlands (“we”, “us”). It governs the Software defined below.

Quario is commercial software. Its packages ship with readable source code, but it is not open source. This agreement grants no rights beyond those it states.

## 1. Definitions

- The **Software** is any software we publish under the Quario name, including the `quario` and `@quario/*` packages, except where a product states its own terms. Each release states the edition of this agreement that governs it. A license key bought under this edition licenses every release it covers under this edition, including releases that shipped with an earlier edition.
- **You** means the individual who exercises rights under this agreement. Where that individual acts for a company or other organization, **you** also means that organization. In that case the organization is the licensee, and the rights and limits in this agreement apply to it as a whole.
- An **Application** is software you create that incorporates the Software and adds substantial functionality beyond it. A service you operate that embeds the Software and renders reports for your End Users is an Application, even if it does little more than render.
- A **Deployment** is one production service, application, bot, worker or MCP server that runs the Software under your control. All replicas of it together are one Deployment. A service that only passes render requests to another service does not run the Software, so it is not a Deployment. A service that a host or contractor operates on your behalf stays under your control. Development, staging, CI and test environments are not Deployments. We never count the people, agents or renders that a Deployment serves.
- A **License Key** is the signed key that evidences the license of one Deployment. You buy it from us or from an authorized reseller.
- **End Users** are people who interact with the Software only through an Application that runs in a Deployment. They run it, view the reports it produces, or supply parameters, input or report definitions to it. End Users do not buy a license. Their rights come from section 5.

## 2. Acceptance

This file is our standing offer. Anyone who exercises the rights in section 3 accepts them, subject to their conditions. All other rights start when you buy a License Key. Where a person buys for an organization, that person states that they have the authority to accept this agreement on the organization’s behalf. The acceptance then covers the whole organization. If you do not accept this agreement, do not use the Software.

## 3. Evaluation and development

You may download, install and use the Software free of charge in any environment that is not a Deployment. That includes evaluation, prototypes, proofs of concept, and the development, staging, CI and test environments of an Application. This right covers the full feature set, needs no key, and has no time limit. The Software marks output that no License Key covers, as section 6 describes.

This right does not let you use the Software in live business operations, or expose it in services that third parties use. Each Deployment needs a License Key under section 4.

## 4. Deployment licenses

Each Deployment needs its own License Key, from the first day it runs in production. With that key in place:

- You may set the key in that Deployment and in the development, staging, CI and test copies of that Deployment. The key then removes the marking there too.
- One key never covers two Deployments at the same time.
- You may move a key to a new Deployment after the old Deployment no longer runs the Software in production.
- Contractors who work for you may use your keys for that work. They may not use your keys for work they do for other clients.

## 5. Use and pass-through

With a License Key under section 4 in place, you may operate the Application in its Deployment **royalty-free**. We charge no fees for servers, replicas, requests, renders, agents or End Users. You may embed your License Key in the Application.

We grant you the right to pass through to each End User a limited, non-exclusive, non-transferable right to use the Software only as embedded in the Application that runs in your Deployment. You must not let End Users extract the Software from the Application or use it to develop software of their own.

Calling applications that only request renders from your Deployment do not need to incorporate the Software. People who use those applications only as End Users get the pass-through rights above.

You may not:

- Distribute the Software on its own, or as part of a product whose primary purpose is to give report-engine, report-design or document-generation capability to third-party developers.
- Expose the Software’s APIs to third parties as a development tool or service that replaces their own License Keys. A service you operate that embeds the Software and renders for your own End Users is not such a tool.
- Fork, mirror, repackage, rename or wrap the Software, or republish it on any package registry or code-hosting platform, other than as embedded in an Application.

**OEM distribution.** An Application that your customers install, embed or resell, and that runs the Software outside your control, is OEM distribution. A License Key does not cover OEM distribution, for any number of copies. Contact us for separate terms. When you render documents for your customers from a product that you host yourself, that product is a Deployment, not OEM distribution.

While this agreement is in force, you may not create any tool, library, product or service that competes with the Software or with any other Quario product, directly or indirectly. This restriction ends when this agreement terminates. You may not remove or change copyright or license notices in the Software.

## 6. License Keys and output marking

The Software accepts a License Key as evidence of a Deployment’s license under section 4. Key checks run offline.

Each License Key states an end date. A key covers every release of the Software dated on or before that end date. Without a valid key, or with a key that does not cover the installed release, the Software runs with its full feature set but marks its output as unlicensed. A key that is void under section 7 licenses nothing, even where the installed release still accepts it. Use of a key that you have no right to use is a material breach of this agreement.

A later release may refuse a key that we revoked. We revoke a key when we refund its payment, or when a chargeback or similar process reverses its payment. We also revoke a key that someone publishes for reuse by others. In that case, we give the licensee a free replacement key with the same end date. When you embed a key in your Application under section 5, that embedding alone does not publish the key for reuse.

You may not remove, disable or bypass the key check or the output marking, or distribute anything that does.

## 7. Term, updates and refunds

**No subscription.** You pay once for each License Key. The key covers every release dated up to one year after you bought it, and you get support until that end date. We give support through our issue tracker and by email, with commercially reasonable effort. We do not guarantee response times.

**Perpetual license.** Your license to the releases that a key covers is **perpetual**. The Deployment may keep using those releases, and the Application may keep running them, forever, at no further cost. Releases dated after the key’s end date need a new key.

**Renewal.** Renewal is a new purchase of a new key. It never occurs automatically, and we never charge you without a new order.

**Refunds and reversals.** If we refund a payment, or a chargeback or similar process reverses a payment, each key that the payment bought is void. A partial refund states the keys that it voids. A void key gives you no rights, including no perpetual license. You keep the rights of section 3, and this agreement continues. Use of a void key in a Deployment is a material breach of this agreement. Keys that the refund or reversal does not void stay valid. If a payment dispute is decided in our favour, we restore the license with a reissued key.

## 8. Source availability

The Software’s packages ship with readable source code, so you can review and debug what you run. Readable source does not grant extra rights. This agreement governs all use of the source. You may publish the Software, modified or not, only as part of an Application under section 5.

## 9. Ownership, trademarks and feedback

We license the Software. We keep all intellectual property rights in it. The report definitions, data and output that you create with the Software are yours. “Quario” and the Quario logo are our trademarks. This agreement grants no rights to use them, except to identify the Software. If you send us feedback or suggestions, we may use them without obligation.

## 10. Warranty and liability

We provide the Software as is. To the fullest extent the law allows, we disclaim all warranties and conditions, express or implied, including merchantability, fitness for a particular purpose, and non-infringement.

To the fullest extent the law allows, we are not liable for indirect or consequential damages, loss of profits, loss of data, or business interruption. Our total aggregate liability under this agreement is limited to the greater of EUR 100 and the fees you paid us in the twelve months before the event that gave rise to the claim. These limitations do not apply where the damage results from the intent or deliberate recklessness (opzet of bewuste roekeloosheid) of us or our management, or where mandatory law does not permit them.

## 11. Termination and survival

If you materially breach this agreement, we may terminate it by notice. If you can remedy the breach, we first give you 30 days from that notice to remedy it. Termination then occurs only if the breach continues. On termination, the licenses that this agreement grants end. The perpetual license to the releases that a key covers survives termination only if the end date of that key passed before the breach. Section 5 survives with it, as far as you need section 5 to use that license. Sections 8 through 12 survive any termination.

## 12. General

Dutch law governs this agreement. The competent court for our registered office decides disputes. You may not assign this agreement without our consent, except to a successor of your whole business. We may assign it to a successor of ours. If a provision is unenforceable, the remainder stays in force. If we do not enforce a provision, we do not waive it. This agreement, together with your order for License Keys, is the entire agreement about the Software, unless we agree otherwise in writing.

---

**Purchasing and contact:** <contact@getquario.com> · <https://getquario.com>

Copyright © 2026 Webstronauts. All rights reserved.

```json
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://getquario.com/"},{"@type":"ListItem","position":2,"name":"License","item":"https://getquario.com/license"}]}
```