agentlas
BusinessHubHub guideDocs

← Enterprise overview

ENTERPRISE SERVER · FOR COMPANY ADMINISTRATORS

Getting Agentlas Enterprise Server

The steps a company goes through, in order — from signing up to rolling Desktop out to every employee.

Server package download

Enter the licence ID and download key from your Agentlas contract email. We check the licence and return signed download links that are valid for 10 minutes.

Starts with lic_
Starts with agdk_. Shown to you once; this page does not store it.

Lost the key or never received one? Ask your Agentlas contact to issue a new download key. Talk to us →

  1. Apply and sign the contract

    Contact us or apply as a company in the Business console (choose “Create organization”). We agree on seat count, term and how you will deploy: connected to the internet or air-gapped.

  2. Licence is issued

    Agentlas issues your licence for the agreed seats and term and sends the company administrator two values, once: a licence ID (lic_…) and a download key (agdk_…). Keep the key like a password.

    • Lost the key? We rotate it: the old key stops working immediately.
    • A pilot licence can come first and be converted when you sign.

  3. Company administrator checks the licence

    The administrator enters the licence ID and download key in the panel above. No Agentlas account sign-in is needed; the key is the proof.

  4. Download the server package

    After the check you get signed links that expire after 10 minutes, the SHA-256 of each file, and the install command.

    • Verify the SHA-256 before installing. The install script also checks it and the signed release list.
    • Keep the package inside your network; do not share the links.

  5. Check system requirements

    Prepare one Linux server (VM or bare metal). Sizing below is a planning default; the package release notes are authoritative.

    System requirements (planning default)
    Operating system64-bit Linux (linux-amd64) with sudo access
    Container runtimeDocker Engine and Docker Compose v2
    Up to ~50 users4 vCPU · 16 GB RAM · 200 GB SSD
    Up to ~300 users8 vCPU · 32 GB RAM · 500 GB SSD
    Inbound (inside your network)HTTPS from employee PCs and administrators to your server address (the container listens on 8470 behind your HTTPS proxy)
    InternalYour SMTP server for agent mail, and any in-house model endpoints
    Outboundagentlas.cloud (licence lease and signed updates), plus the model providers you use with BYOK. No inbound connection from Agentlas is needed.
    BackupsBack up the data volume under /opt/agentlas-enterprise with your usual tooling

    Air-gapped option

    No outbound access: an offline licence bound to your installation ID, the server bundle downloaded on a connected PC and brought in, signed update bundles, and models reachable inside your network. Planned with you before the install.

  6. Install

    On a server with internet access, run the install command shown after the licence check. It checks the OS and Docker, asks for the download key, downloads and verifies the image, writes the configuration to /opt/agentlas-enterprise and starts the server.

    curl -fsSL https://agentlas.cloud/api/enterprise/v1/install.sh \
  | sudo AGENTLAS_LICENSE_ID=lic_… bash

# air-gapped: download the bundle and licence file on a connected PC,
# bring them in, then run
sudo bash install.sh --offline <bundle>

  7. Initial setup

    When the script finishes it prints the setup address. Open https://<your server address>/setup and complete the first run.

    • Create the first administrator account.
    • Register the licence (online activation, or upload the licence file for air-gapped installs).
    • Connect mail: your company domain and SMTP server for agent mail.
    • Models: add company API keys (BYOK). Keys stay on the server and never reach employee PCs.

  8. Roll Desktop out to employee PCs

    Employees install Agentlas Desktop for Windows and Mac from your company server and connect it with an enrollment code.

    • Self-service: employees open https://<your server address>/downloads.
    • Managed: IT deploys the installer with your MDM (for example Microsoft Intune or Jamf).
    • For each employee the admin issues a one-time enrollment code (ENR-…, valid 72 hours). Desktop enrolls with it and then signs in with its own device key.

  9. Updates

    The server checks Agentlas Cloud for signed new versions and mirrors Desktop updates. Employee Desktops update from your company server, only to versions it has mirrored and verified.

    • Air-gapped: bring in the signed update bundle and apply it from the admin console.

  10. Licence renewal and expiry

    The server renews its licence lease once a day. When the contract is renewed, the new term arrives with the next lease.

    • After the term ends: a grace period in read-only mode — reading and export work; new work and new enrollments are paused.
    • After the grace period, or if the licence is suspended: the server stops running work.
    • Export (/admin/export) stays open in every state. Agentlas never deletes your company data.

  11. Support

    Reach us by phone or email. For incidents, send the server version and the license status from /api/v1/status; share logs only after you have reviewed them.

Get Agentlas Enterprise Server — installation guide for company admins