> For the complete documentation index, see [llms.txt](https://docs.vergeos-demo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vergeos-demo.com/knowledge-base/getting-started/requesting-an-airgap-license.md).

# Requesting an Airgap License

{% hint style="warning" %}
**Air-gap licensing is not common and requires justification. Please see** [**Licensing and Software Updates**](/run-the-platform/system-administration/licensing-and-updates.md) **for more information.**
{% endhint %}

## Overview

{% hint style="info" %}
**Key Points**

* VergeOS requires a valid license for operation
* Air-gapped environments need a special airgap license
* The process involves generating a license request file and emailing it to Verge
  {% endhint %}

This guide walks you through the process of requesting an airgap license for VergeOS systems in environments without outbound Internet access.

## Prerequisites

* Access to the VergeOS Cloud Dashboard
* A working email client on a machine that can send external emails
* Understanding of your system's airgapped status

## Steps

1. Navigate to System Settings
   * From the System Dashboard, click **System** on the left menu
   * Click **Settings** on the left menu
2. Initiate License Request
   * In the **License** section, click the **Request License** button
3. Generate License Request File
   * A popup window titled "Request Generated" will appear
   * This window displays information about the license request file
4. Download Request File
   * Click the **Download Request File** button
   * Save the license request file to your local machine
5. Prepare Email to Verge
   * Click the **Email <license@Verge.io>** button
   * This opens your default email client with a pre-addressed email
6. Send License Request
   * Attach the downloaded license request file to the email
   * Provide additional information in the email body (e.g., company name, purpose of license)
   * Send the email to Verge's licensing team

## What Happens Next

1. Verge processes your request and generates an airgap license file
2. You receive a reply email with the airgap license file attached
3. Upload the received license file to your VergeOS system (covered in a separate guide)

{% hint style="info" %}
**Processing Time**

If you haven't received a response within 2 business days, please follow up with Verge's support team.
{% endhint %}

## Important Considerations

* Ensure the system requesting the license is the one you intend to license
* Keep the license request file secure
* For multiple systems, repeat this process for each system individually

## Troubleshooting

{% hint style="warning" %}
**Common Issues**

* Problem: Unable to generate license request file
  * Solution: Verify your access permissions in the VergeOS Cloud Dashboard
* Problem: Email client doesn't open automatically
  * Solution: Manually compose an email to <license@Verge.io> and attach the downloaded request file
    {% endhint %}

## Feedback

{% hint style="info" %}
**Need Help?**

If you encounter any issues while requesting an airgap license or have questions about this process, please don't hesitate to contact our support team.
{% endhint %}

***


---

# 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:

```
GET https://docs.vergeos-demo.com/knowledge-base/getting-started/requesting-an-airgap-license.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.