Running Without a Platform Connection

Some systems cannot connect to Axoniq Platform, for example in air-gapped networks. They can use a license file or environment variable instead. This page explains how to get such a license and how to install it.

Requirements

A license used from a file or environment variable must allow running without a connection to Axoniq Platform. Such licenses are only available with an Enterprise plan or another agreement made with Axoniq sales; contact Axoniq to arrange one.

Regular licenses require a connection. Axoniq Framework stops when it reads one from a file or environment variable, and Axon Server rejects it.

When your workspace does not have such a license, the License file and Environment variable options in the Resource Center installation guides show that disconnected licensing is not included in your plan.

Downloading the license

You download a license per environment, from either place:

The installation guides in the Resource Center: choose License file or Environment variable as the license source and click Download Axoniq license.
The Axon Server page of the environment: open Download License and choose the version.

Choose the version that matches the software that reads it:

Version	For
V2	Axoniq Framework 5, Axon Server 2026.0 and later, and Insights. In the Download License menu: Axon Server 2026+.
V1	Axon Server 2025.2 and older. In the Download License menu: Axon Server 2025.x and older.

Version

For

Axoniq Framework 5, Axon Server 2026.0 and later, and Insights. In the Download License menu: Axon Server 2026+.

Axon Server 2025.2 and older. In the Download License menu: Axon Server 2025.x and older.

The downloaded file is named after your workspace and environment. Rename it to axoniq.license, which is the name Axoniq Framework and Axon Server look for by default.

How long it is valid

A license that allows running without a connection is valid for the term of your agreement, usually a year. The license file contains its own dates: expiry_date, and grace_date, the end of the grace period after it.

When your agreement is renewed or changed, download the new license and install it before the old one expires. Both Axoniq Framework and Axon Server pick up a replaced license file without a restart. An AXONIQ_LICENSE environment variable in Axoniq Framework is only read at startup, so restart the application after changing it. See Rotation and Expiry for what happens when a license expires.

Axoniq Framework

You do not configure axoniq.platform.credentials on an application that runs without a connection.

Through Axon Server

If your applications connect to Axon Server 2026.0 or later, let Axon Server act as their license server. Each application asks the Axon Server cluster it connects to for its license, so you only install the license on the Axon Server nodes, as described in Axon Server. The applications need no license configuration of their own, and a renewed license reaches them without touching them.

Install a V2 license on the Axon Server nodes for this to work. Use a license file or environment variable on the application only when it does not connect to Axon Server, or connects to an older version.

With a license file

Save the license as axoniq.license in the directory the application is started from. To keep it elsewhere, point to it with the JVM system property or the environment variable:

java -Daxoniq.license.file=/etc/my-application/axoniq.license -jar my-application.jar

# or
export AXONIQ_LICENSE_FILE=/etc/my-application/axoniq.license

The file must exist when the application starts.

With an environment variable

Set AXONIQ_LICENSE to the license content, base64-encoded:

# Linux
export AXONIQ_LICENSE=$(base64 -w0 axoniq.license)

# macOS
export AXONIQ_LICENSE=$(base64 -i axoniq.license)

This is convenient in containers and on Kubernetes, where the value can come from a secret. The variable is read when the application starts, so restart the application after changing it.

Axon Server

Axon Server reads axoniq.license from its license directory, which is the working directory unless you set axoniq.axonserver.enterprise.license-directory. Alternatively, set the environment variable AXONIQ_LICENSE to the path of the license file.

Every node of a cluster needs the license.

Docker

Mount the license into the container and point to it:

docker run \
    -v ./axoniq.license:/axonserver/config/axoniq.license:ro \
    -e AXONIQ_LICENSE=/axonserver/config/axoniq.license \
    docker.axoniq.io/axoniq/axonserver

Kubernetes

Store the license in a secret, mount it, and set the license directory:

kubectl create secret generic axoniq-license --from-file=axoniq.license=./axoniq.license

Mount the secret at, for example, /axonserver/license, and add to axonserver.properties:

axoniq.axonserver.enterprise.license-directory=/axonserver/license

Debian and Ubuntu packages

Place the license at /etc/axonserver/axoniq.license and add to /etc/axonserver/axonserver.properties:

axoniq.axonserver.enterprise.license-directory=/etc/axonserver

Downloaded JAR

Place axoniq.license in the directory you start Axon Server from.

The installation guides in the Resource Center show these steps with your own configuration.