Enterprise

The same FleetOps, plus what a larger organisation's security and compliance teams ask for. There is nothing extra to install: paste a license key into the FleetOps you already run and the Enterprise features turn on. It checks the key offline and never phones home.

What it adds

Image vulnerability scanning

New in 1.0

Trivy scans every image on your Docker hosts, Swarm nodes and Kubernetes clusters when it arrives and once a day. The Security page puts fixable critical vulnerabilities on running containers at the top, across the whole fleet. Off until an admin turns it on; air-gapped installs use a mirror.

Security, patch queue sample, synthetic
IMAGE                      ENVS            RUNNING  CRITICAL  FIXABLE
orders-api:2026.10.31      prod-eu, prod-us     12         3        3
nginx:1.25.3               prod-eu               4         1        1
grafana/grafana:11.3.0     ops                   1         0        0
postgres:16.4              prod-eu               2         0        0
  • New in 1.1CVE notificationsRules send new CVEs on the images you run to Slack, email, Microsoft Teams, Discord, PagerDuty or a signed webhook. One message per CVE, never a flood.
  • AvailableAudit exportStream the audit log for any date range as CSV or NDJSON, for your SIEM or your auditors.
  • AvailableTeamsGrant environment roles to a team instead of one user at a time, and see where each user's access comes from.
  • AvailableCustom rolesBuild a role from the permission list, for example restart and read logs but no terminal.
  • AvailableSingle sign-onMicrosoft Entra ID, Google, GitHub, any OIDC provider, or LDAP (Active Directory, OpenLDAP). Provider groups decide teams.
  • AvailableScheduled backupsDaily passphrase-sealed backups to S3-compatible storage or a local folder, with retention and restore.
  • PlannedAPI tokensScoped tokens for CI and automation, audited like any user.

One image, turned on by a key

Since 1.0 there is a single image, fleets/fleetops. Every install starts on the free Community plan, and a license key unlocks Enterprise in place: no reinstall, no restart, no migration.

New install

Install FleetOps

The same command for everyone. Open port 9000 and create the admin; it runs as Community until you add a key.

Linux and macOS
curl -fsSL https://fleetops.run/install.sh | sh
Windows PowerShell
irm https://fleetops.run/install.ps1 | iex
Or by hand, with Docker
docker run -d --name fleetops -p 9000:9000 \
  -v fleetops-data:/data \
  -v /var/run/docker.sock:/var/run/docker.sock \
  --group-add "$(docker run --rm -v /var/run/docker.sock:/s busybox:1.37 stat -c %g /s)" \
  fleets/fleetops

With a license

Install the key

Paste the key from your email in Admin → License; Or mount the file and pass it at start. Features turn on at once.

License from a file
docker run -d --name fleetops -p 9000:9000 \
  -v /etc/fleetops/fleetops.lic:/fleetops.lic:ro \
  -e FLEETOPS_LICENSE_FILE=/fleetops.lic \
  -v fleetops-data:/data \
  -v /var/run/docker.sock:/var/run/docker.sock \
  --group-add "$(docker run --rm -v /var/run/docker.sock:/s busybox:1.37 stat -c %g /s)" \
  fleets/fleetops

Still on fleets/fleetops-ee

Move to the one image

fleets/fleetops-ee is now a deprecated alias and a later release stops publishing it. Start fleets/fleetops on the same data; your license, users and settings carry over.

Docker
docker rm -f fleetops
# the data volume stays; start fleets/fleetops on it
docker run -d --name fleetops -p 9000:9000 \
  -v fleetops-data:/data \
  -v /var/run/docker.sock:/var/run/docker.sock \
  --group-add "$(docker run --rm -v /var/run/docker.sock:/s busybox:1.37 stat -c %g /s)" \
  fleets/fleetops

Without a license, or 14 days after one expires, teams and custom roles turn read-only but keep granting access, scheduled backups pause, people who already signed in through single sign-on keep doing so but nobody new is let in, and scanning and notifications stop. Community features and your data are never affected.

Binaries, Compose, HTTPS, Swarm and Kubernetes are on the install page. Every method installs the same build; the installer's --upgrade moves an Enterprise-image install to fleets/fleetops for you.

How the license works

No license server, no call home, no surprise lock-out.

  1. 1
    Run FleetOps. Any 1.0 or later install of fleets/fleetops already contains the Enterprise code, switched off. How
  2. 2
    Install the license. Upload it in Admin → License, or start the server with --license-file. It is a signed file, checked offline.
  3. 3
    Nodes. A license covers a number of nodes: each Docker or Podman host is one, and a Kubernetes cluster or Docker Swarm counts its nodes. At the limit, new environments are refused; a cluster that grows past it only warns admins. Users are never limited.
  4. 4
    Expiry. Enterprise features keep working for 14 days after expiry, then switch off. Community features and your data are never affected.

Source you can read

Enterprise code lives in the same repository, under ee/, and is source-available: you can read it, build it and test it. The official build includes it and is free to run anywhere, production included, with the Enterprise features off. Using those features in production needs a subscription. Everything outside ee/ is Apache-2.0, and reaches Enterprise code only through declared seams that a CI check enforces.

How the code is licensed

Running FleetOps for a larger team?

Tell us how many users and environments you have and what your compliance team needs.

Talk to us