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

# GUID

GUID-based licensing is used for deployments that run VIESUS across multiple machines — servers, Docker containers, VMs, or cloud instances where the activation hardware would change. For a single fixed machine, see [Activation Key](/licensing/activation-key.md).

A GUID license is granted by Viesus AG when your deployment scenario warrants it. Discuss your scenario with <info@viesus.com> when arranging your license.

***

## How it works

Viesus AG delivers a customer-specific VIESUS library package with an expiry date embedded inside it. You provide a GUID — a unique identifier string — at runtime to unlock the library. The GUID has no machine binding; the same GUID works on any number of systems simultaneously.

```powershell
Example GUID: 4e8f35ab-7f72-4b1e-a1fd-2b5e9c58e9d3
```

Your GUID is delivered with your software package. Packages are downloaded from [transfer.viesus.com](https://transfer.viesus.com) or sent by email. Contact <info@viesus.com> to request a trial or purchase.

***

## Key properties

| Property        | Detail                                                                              |
| --------------- | ----------------------------------------------------------------------------------- |
| Machine binding | None — runs on any machine, VM, container, or cloud instance                        |
| Billing         | Volume-based: contracted by image count; enforcement is license-agreement dependent |
| Expiry          | Embedded in the delivered library; typically annual                                 |
| Grace period    | 1–2 months of continued operation after expiry to allow renewal                     |
| Renewal         | Same GUID — install the new package; GUID does not change                           |
| Trial           | Available on request from <info@viesus.com>                                         |

***

## Volume and expiry

On-premise licenses are contracted by image volume. The library tracks processed images against the contracted volume. When the limit is reached or the expiry date passes, images pass through without enhancement. The 1–2 month grace period ensures continuous operation during renewal. Viesus AG delivers a new library package with an updated expiry and volume; install it and processing resumes immediately.

***

## Passing the GUID

The GUID is supplied at runtime by each VIESUS interface:

**CLI:**

```bash
viesus -g "4e8f35ab-7f72-4b1e-a1fd-2b5e9c58e9d3" -l images.lst -s -p config.json
```

**Node.js:**

```js
const viesusObj = new viesus.MyViesusObject('4e8f35ab-7f72-4b1e-a1fd-2b5e9c58e9d3');
```

**C/C++ SDK:**

```c
HIsEnhance obj = IsEnhanceCreateFromGUID(IS_RGB, IS_PixelInterleaved, guidBytes);
```

**PDF Enhancer** — pass in `settings.json`:

```json
{
  "guid": "4e8f35ab-7f72-4b1e-a1fd-2b5e9c58e9d3"
}
```


---

# 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.viesus.com/licensing/guid.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.
