◎Foundation
Fleet visibility
A protocol-independent inventory model for telemetry agents, health, identity, capabilities, labels, and deployment context.
OPEN SOURCE · OPAMP-FIRST · VENDOR NEUTRAL
Operate telemetry collectors as a fleet.
FleetAMP is an open control plane for discovering, observing, configuring, and operating telemetry agents without coupling fleet management to a telemetry backend.
Apache-2.0Self-hostedGoCommunity project
fleetamp / control-plane● architecture
SourcesGit · CMDB · Identity
↓
FleetAMPAPI · Policy · State · Inventory
↓
ManagementOpAMP · future adapters
↓
AGENTOTel CollectorVM
GATEWAYOTel CollectorKubernetes
FUTUREOther agentsAdapter
One domain modelAcross VM, container and Kubernetes runtimes
Adapter isolationUpstream protocol changes stay at the boundary
Backend neutralFleet management stays independent from telemetry storage
PLATFORM PRINCIPLES
Built as a control plane, not a fork.
FleetAMP prefers composition over custom distributions. Upstream agents and protocols remain replaceable dependencies behind explicit adapters.
⇄In progress
OpAMP control plane
An isolated OpAMP adapter keeps protocol details away from FleetAMP APIs, storage, policy, and future integrations.
⌘Planned
Configuration control
Designed for validated remote configuration, desired/effective state, group targeting, and controlled rollouts.
◇Designed
Extensible integrations
Provider boundaries for Git, CSDM/CMDB enrichment, identity, additional telemetry agents, and deployment platforms.
CONTROL LOOP
From connection to desired state.
The first FleetAMP milestones focus on a small, verifiable management loop before broader integrations are added.
Connect
OpenTelemetry Supervisors connect to the FleetAMP management endpoint.
Discover
FleetAMP normalizes identity, metadata, health, capabilities, and runtime context.
Control
Desired configuration is validated, versioned, targeted, and delivered through a management adapter.
Observe
FleetAMP compares desired and effective state and surfaces fleet health and deployment results.
EXTENSIBLE BY DESIGN
Keep integrations optional.
FleetAMP keeps integration contracts in the architecture now without making external systems mandatory for the first release.
Explore integration design →ConfigurationAzure DevOps · GitHub · GitLab · Filesystem
EnrichmentCSDM / CMDB · REST · custom metadata
IdentityOIDC · scoped authorization · RBAC
ManagementOpAMP first · additional adapters later
COMMUNITY EDITION
Follow the build from the foundation up.
FleetAMP is early-stage. The docs distinguish implemented foundations from planned capabilities as the project evolves.