Roadmap
What each release shipped, and what comes after. Newest first. Dates are when a release was tagged.
- Next
- Port-forwardReach a pod's port through FleetOps.Community
- API tokensScoped tokens for CI and automation, audited like any user.Enterprise
- SIEM forwardingSend the audit log to your SIEM as it happens, and keep it longer.Enterprise
- Shipped
- The cluster FleetOps runs inInstalled in Kubernetes, FleetOps registers its own cluster as the local environment through its service account. No agent or kubeconfig.Community
- A start page that leads somewhereWith no environments yet, admins see Add your first environment instead of advice about a Docker socket.Community
- Bare serversWith neither Docker nor a cluster, the server starts empty and manages remote hosts and clusters through agents.Community
- Helmfile starterA short values file with the settings most installs change, and a helmfile pinned to a chart version.Community
- Shipped
- Helm chartRun the server in your own cluster: one pod, its database on a kept volume, HTTPS for agents, an optional Ingress and NetworkPolicy.Community
- Plain manifestThe chart rendered with its defaults, for a kubectl apply without Helm.Community
- In-cluster agents trust the serverThe agent command carries FleetOps's generated certificate, so an agent in the same cluster can dial it.Community
- Shipped
- Kubernetes scans by node pullThe cluster pulls the scanned image through its nodes' registry access or your pull secrets. Nothing in the image runs.Enterprise
- Clear scan failuresAn image a scan can't pull is named, and a scan that can't be scheduled fails fast.Enterprise
- Shipped
- CVE notificationsRules send new CVEs on the images you run to Slack, email, Microsoft Teams, Discord, PagerDuty or a signed webhook.Enterprise
- No flood, no repeatsWhat is already there is recorded as known; one message per CVE, batched across a wave of scans.Enterprise
- Shipped
- Stable 1.0Semantic versioning from here: breaking changes only in a new major version.Community
- One imagefleets/fleetops runs as Community until a license key turns Enterprise on. fleets/fleetops-ee is a deprecated alias.Community
- Free in productionUnmodified official builds may run in production without a key, with the Enterprise features off.Community
- New lookA three-panel shell with a now-playing panel, a live event tape, and phone and tablet layouts.Community
- Image vulnerability scanningTrivy scans on Docker hosts, Swarm nodes and Kubernetes clusters, with a fleet-wide patch queue and air-gapped mirrors.Enterprise
- Shipped
- Docker SwarmAn agent on every node, each proving its node with the node's Swarm certificate. Live nodes, services, tasks, secrets, configs and networks, changed from the browser.Community
- Swarm stacksCompose files deployed as Swarm services, with git sync, revisions, rollback and drift.Community
- Stack scopingRoles on a swarm limited to some stacks, as Kubernetes roles are limited to namespaces.Community
- BuildsCompose build from the repository or a dockerfile_inline, on the target host. Code-only commits redeploy just the services that build it.Community
- Secrets and configsStored encrypted and copied into each container before it starts. Secrets are never shown again.Community
- Git over SSHSSH URLs with a deploy key FleetOps generates or one you paste. Host keys are checked.Community
- Shipped
- Git-backed stacksA stack takes its Compose file from a branch of an HTTPS git repository. Variables stay in FleetOps, sealed.Community
- Webhooks and pollingSync by hand, by polling, or on a push webhook from GitHub, GitLab, Gitea or Forgejo.Community
- Auto-deploy or reviewDeploy each new commit through the same plan and restore, or hold it as an update to review.Community
- Shipped
- Compose stacksWrite a Compose file and its variables in the browser and deploy it to any Docker host, local or through an agent.Community
- Plan before deployServices created, recreated with the fields that changed, or removed, and a diff of the file.Community
- Safe deploysA failed or interrupted deploy puts the stack back as it was.Community
- Revisions and rollbackEvery deploy is a revision you can roll back to.Community
- Shipped
- Backup and restoreThe whole server in one passphrase-sealed file. Restore over a running server or from the first-run screen.Community
- Single sign-onMicrosoft Entra ID, Google Workspace, GitHub and any OpenID Connect provider. Accounts are created on first sign-in and provider groups decide teams.Enterprise
- LDAP sign-inActive Directory and OpenLDAP, with the same group-to-team mapping.Enterprise
- Scheduled backupsDaily backups to S3-compatible storage or a local folder, with retention. Restore from a target in one click.Enterprise
- Shipped
- PermissionsEvery route checks one named permission. Revealing a Secret's value is its own permission.Community
- Custom rolesRoles built from the permission list.Enterprise
- TeamsGrant access to a group, and see where each user's access comes from.Enterprise
- Licenses by nodeEnterprise licenses carry a node limit. Users are never limited.Enterprise
- Shipped
- Helm install and upgradeRendered and reviewed object by object before anything is applied.Community
- Custom resourcesEvery kind the cluster serves, found by API discovery and followed live.Community
- Workload logsOne stream across a workload's pods, with previous runs.Community
- EKS, GKE and AKS kubeconfigsExec-plugin users, run by the server with a time limit.Community
- Audit exportThe first Enterprise feature, with offline license files.Enterprise
- Shipped
- Docker and PodmanContainers, images, volumes, networks and Compose projects, live from Docker events.Community
- Logs and terminalA 200,000-line log viewer and a terminal that never respawns a shell.Community
- Remote hostsA dial-out agent per host; no inbound port.Community
- KubernetesWatches, YAML edits as reviewed diffs, Helm rollback and uninstall.Community
- Roles and auditPer-environment roles, namespace scoping and an audit log, all free.Community