Licensing

A license unlocks the full feature set of Britive Bridge. Without a valid license, Bridge still runs but falls back to a reduced limited mode (described below). Bridge validates signed licenses locally, and connected deployments can fetch and renew their license from the Britive platform automatically.

Each license is tenant-bound (issued for your specific Britive tenant) and cryptographically signed (so it cannot be forged or altered). It is a single text blob in the form payload.sig.

Providing a license

For production, the simplest option is automatic retrieval - Bridge fetches and renews the license from the Britive platform on its own. You can also provide a license directly, configured under server.license:

server:
  license:
    path: /etc/britive-bridge/license.txt

Which source wins (precedence)

If you provide a license in more than one place, Bridge picks one in this order, highest first:

1. Automatic retrieval from the platform (when enabled - see below). It takes precedence and keeps itself up to date.
2. BRIDGE_LICENSE environment variable
3. server.license.key in the YAML file
4. BRIDGE_LICENSE_PATH environment variable, or server.license.path in the YAML file

In short, when automatic retrieval is on it wins; otherwise BRIDGE_LICENSE > key > BRIDGE_LICENSE_PATH / path. A directly-provided license still acts as a first-boot fallback until the first successful automatic fetch.

Automatic retrieval from the platform

Instead of pasting a license into your config, Bridge can fetch it from the Britive platform and renew it automatically. This is the recommended approach for connected deployments.

To turn it on, configure your Britive tenant and set the environment variable BRITIVE_BROKER_AUTH_TOKEN (the same broker-pool token used elsewhere). When it’s present, Bridge:

• derives the license endpoint from your Britive tenant and fetches the license on startup, then checks again on a fixed daily schedule;
• installs the fetched license as the active one and keeps it current as it renews - without piling up old licenses (each refresh replaces the previous auto-retrieved one);
• falls back safely: if a fetch fails or returns a license that isn’t valid for your tenant, Bridge keeps the license it already has (the 30-day grace period covers temporary outages). It never downgrades a working deployment because the platform was briefly unreachable.

When BRITIVE_BROKER_AUTH_TOKEN is not set, automatic retrieval is off and Bridge uses only the license you provide under server.license.

The grace period

When a license reaches its expiry date, Bridge does not switch off immediately. There is a fixed 30-day grace period after expiry during which all licensed features keep working, giving you time to install a renewal. Once the grace period ends, Bridge drops into limited mode until you install a valid license.

Limited mode

Bridge enters limited mode whenever it has no license, an invalid license, or an expired license (and the grace period has passed). In limited mode Bridge stays usable but with a reduced feature set.

A valid license therefore unlocks: native protocol access, live session viewing and control, recording downloads, and multiple sessions per checkout.

Installing or replacing a license after startup

You do not have to restart Bridge to add or update a license. A license can be installed or replaced while Bridge is running from the Admin console in the web interface. This is the easiest way to apply a renewal or upgrade.

The license indicator

The web interface footer shows a small license indicator so administrators can see license health at a glance. It counts down toward expiry and changes color as the deadline approaches:

• Green - healthy, more than 60 days remaining.
• Yellow - 60 days or fewer remaining; plan a renewal.
• Red - 30 days or fewer remaining; renew promptly.
• “Unlicensed” - no license is installed and Bridge is running in limited mode.