Skip to content

Enterprise licensing (License Server)

AutoC enterprise deployments use a License Server for license enforcement. With enterprise licensing, you can connect and run custom LLM models (not limited to the WhyEngineer catalog).

Setup order: configure the server first, then the clients.

License Server deployment architecture

Server setup

Install License Server on a dedicated host, import the .lic, and start the service. MAC binding applies to this server, not to client machines.

1. Download

Current release: v0.1.2

PlatformLatest
Windows x64license-server-0.1.2-windows-x64.zip
Linux x64license-server-0.1.2-linux-x64.tar.gz

Extract license-server (or license-server.exe). The daemon listens on 0.0.0.0:9847 by default.

2. Request a license (.lic)

When requesting an enterprise license from sales or support (email under Contact us), provide:

  1. Company / project name
  2. Concurrency limit (concurrent autoc clients)
  3. Validity period (start and end dates)
  4. All physical NIC MAC addresses on the machine running license server (must be from one host)

Collect MAC addresses

On the server running license server, collect all physical NIC MACs from that machine (do not combine MACs from different computers):

Windows (PowerShell):

powershell
getmac /v /fo list

Linux:

bash
ip link show | grep -E '^[0-9]+:|link/ether'

You can also copy local MACs from the Licenses tab in license-server gui. Use physical NIC MACs (e.g. AA:BB:CC:DD:EE:FF).

How to apply

Send the details above to the email listed under Contact us.

3. Import the license

On the server, import the vendor .lic (a matching .lic.key must sit beside it). Import checks the signature, validity window, and that every MAC listed in the file is present on this host.

No GUI required — works on VMs, RDP sessions, and machines without OpenGL:

powershell
# Windows (.lic.key must sit beside the .lic)
.\license-server.exe import .\customer.lic
bash
# Linux
chmod +x license-server
./license-server import ./customer.lic

Import multiple files: license-server import a.lic b.lic.

GUI import

powershell
# Windows
.\license-server.exe gui
bash
# Linux
./license-server gui

GUI

Import vendor .lic files through the UI.

Storage location

OSPath
Windows%LOCALAPPDATA%\license-server\licenses\
Linux~/.local/share/license-server/licenses/

Override with LICENSE_SERVER_DATA_DIR if needed.

4. Configure OAuth / SSO (optional)

If your enterprise LLM gateway uses IdP login, an administrator configures OIDC on the license server. Client sign-in steps are under Client setup below.

Run license-server gui and open the OAuth / SSO tab:

OAuth / SSO configuration

  • Provider id — default autoc-license-server
  • Issuer URL — IdP issuer; click Load from well-known to fetch authorization / token endpoints
  • Client id, Scopes (space- or comma-separated, e.g. openid profile offline_access); optional Client secret
  • Click Save OAuth config

Register this fixed callback in your IdP: http://127.0.0.1:59847/callback.

After saving OAuth, connected clients must restart autoc to receive the new config.

5. Start the service

powershell
# Windows
.\license-server.exe server
bash
# Linux
./license-server server

Built-in mTLS; port 9847. Restarting clears in-memory sessions.


Client setup

After the server is running, configure each machine that will use AutoC. Not installed yet? See Download and install.

1. Set the server address

  1. On the welcome screen click Global settings, or open Settings from the workspace sidebar (Ctrl+,).
  2. Select Account on the left, then License server.
  3. Enter Server address as host:port, for example 192.168.1.10:9847.
  4. Click Save & Connect.

When the status shows Connected and Enterprise unlocked, you can add custom models.

License server in Settings

TIP

The address is stored on this machine only. Another computer needs the same step. If connect fails, confirm license-server server is running and TCP 9847 is allowed through the firewall.

2. Configure models

After a successful connection, Custom models appears on the same page.

Option A: API key

  1. Choose the API style (OpenAI-compatible or Anthropic-compatible).
  2. Fill in Base URL, the gateway API key, and Model ids (comma-separated).
  3. Click Save in the settings header.
  4. Switch to the new model in chat.

Option B: OAuth / SSO

Requires OIDC on the server (see Server setup → Configure OAuth / SSO above).

  1. Confirm the license server is connected.
  2. In custom models, enable Use OAuth / SSO, fill in Base URL and model ids, then save.
  3. Under OAuth / SSO, click Log in and complete IdP login in the browser.
  4. Pick the model in chat.

IT can pre-deploy gateway and model settings; users only connect the server and sign in.


FAQ

Q: “License server address is not configured”
A: Open Settings → Account → License server, set the address, then Save & Connect.

Q: License server is configured but sign-in is still WhyEngineer-only, or OAuth is unavailable
A: Ensure license-server server is running, then fully quit and restart AutoC.

Q: Connection failed or concurrency limit reached
A: Ensure server is running, firewall allows TCP 9847, and max_seats in the license is not exceeded.

Q: Import fails (MAC mismatch)
A: Every MAC in the .lic must be present on the server running license server. Use license-server gui on that host to copy local MACs, or collect them with getmac / ip link, then request a license that includes them. Do not mix NIC MACs from multiple machines in one request.

Q: license-server gui fails with OpenGL / egui_glow and the window never opens
A: Some VMs, RDP sessions, or machines without GPU drivers lack OpenGL. Use license-server import path\to\file.lic (.lic.key must sit beside the .lic), then run license-server server.

Q: License server hardware or NIC change
A: Request a new .lic for the new MAC and import on the new server.

Contact us

For enterprise license requests, deployment questions, or technical support, email:

AUTOSAR BSW / ASW AI configuration assistant