> For the complete documentation index, see [llms.txt](https://docs.testvibe.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.testvibe.com/self-hosting/licensing.md).

# Licensing

A self-hosted instance is licensed with an **offline, signed license** — there is no phone-home, so it works fully air-gapped. (The cloud SaaS is never license-checked; it's billed through Stripe instead.)

## How Licensing Works

* **Offline and signed.** TestVibe issues you a signed license. The instance verifies it locally against a key built into the app — no outbound calls, ever.
* **Bound to your instance.** The license names your organisation (shown in the app) and the specific **install id** it's valid for, so it can't be reused on a different install.
* **Perpetual by default.** Licenses don't expire unless TestVibe issues a time-boxed one.

## Grace, Then Read-Only

You don't need a license to start — the instance is fully usable while you activate:

| State         | What happens                                                                                                                                                                   |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Grace**     | No valid license yet. The app runs normally and shows a warning. The grace window is a fixed number of days (default **14**) and is persisted, so restarting doesn't reset it. |
| **Read-only** | Grace expired with no license. Existing data stays fully **viewable**, but **new test runs, generation, and load tests are paused** until you activate.                        |
| **Licensed**  | A valid license is installed. Everything runs; the warning clears.                                                                                                             |

{% hint style="info" %}
Read access is **never** blocked — you can always sign in and view your projects, tests, and results. Only new chargeable work pauses in read-only.
{% endhint %}

## Activating A License

1. **Find your install id.** It's generated on first boot and printed in the web container's logs (look for a `[license]` line with the install id).
2. **Send TestVibe** that install id and your organisation name. TestVibe mints a license bound to your instance and sends it back.
3. **Install it** — set it as the license value in your environment (the string directly, or a mounted license file). The instance picks it up on its next periodic check or on restart, and the status returns to **Licensed**.

If a license ever lapses later, a fresh grace window starts before read-only kicks in again — so a renewal has a buffer, not an instant cutoff.

## Related Help

* [Install](/self-hosting/install.md)
* [Configuration](/self-hosting/configuration.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.testvibe.com/self-hosting/licensing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.