BetaFree-to-use OpAMP fleet management for Windows & LinuxDownload →
Free to Use — Windows & Linux

The Control Plane for OpenTelemetry.

Deploy, govern, and cost-optimize your entire collector fleet — neutral to any backend, audited end to end, and ready for the AI agents that will run it tomorrow. Free to use, self-hosted on your infrastructure.

Live OpAMP Simulation
LIVE SIMULATION
OpAMP Configuration Orchestration
$ fleetctl status --all
✓ Fleet is stable. All agents running policy v1.4.1.
CollectorCtrlManagement Server
Standing By
K8s
10.244.2.14
k8s-prod-us-westenv: production
v1.4.1 (In Sync)
Linux
172.16.82.11
srv-prod-api-01env: production
v1.4.1 (In Sync)
Win
192.168.12.4
win-prod-ad-02env: production
v1.4.1 (In Sync)

SSH into 50 servers to change one config

Manual config edits across hundreds of nodes are slow, error-prone, and impossible to audit.

Restarting collectors = telemetry gaps

Every collector restart tears down network sockets and drops data. Users notice.

No idea if your fleet is healthy

Collectors fail silently. By the time you notice missing data, the incident is already live.

CollectorCtrl replaces all of this

Built for Engineers Who Need Fleet Control

Managing OpenTelemetry Collectors across hundreds of servers, Kubernetes clusters, and Windows machines is painful. CollectorCtrl replaces SSH scripts and manual config edits with a centralized, policy-driven control plane — every change authenticated, authorized, and written to an audit trail.

Centralized Fleet View
Honeycomb grid and table views of all your agents in one place.
Zero-Drift Configs
Supervisor auto-reverts any unauthorized local changes.
Self-Healing Apply
Push config updates with fast supervised restarts and automatic fallback.
Remote Upgrades
Upgrade agents fleet-wide with automatic rollback.
Read the Guides

Three-Component Architecture

Simple, secure, and designed for production on your own infrastructure.

Management Server

Go binary serving the React dashboard, REST API, and OpAMP WebSocket gateway

Port 4320 / 4321
WSS / OpAMP

Supervisor Agent

Lightweight agent managing collector lifecycle, configs, and health on each node

Windows Service / systemd
Child Process

OTel Collector

Standard OpenTelemetry Collector binary — Core, Contrib, or custom build

Any distribution
CollectorCtrl Logo
CollectorCtrlOn-Prem Fleet Manager
OpAMP Control Protocol
Deployment Environment (Linux, AWS, k8s)
Supervisor AgentLifecycle & Configuration
OpenTelemetry CollectorSupports Native & Vendor distributions of OTel Collectors.
Observability BackendDatadog, Splunk, Elastic, Dynatrace
Platform Capabilities

What CollectorCtrl Does

Real features, shipping today, based on the OpAMP open standard.

Dynamic Target Policies — Visualizer
LABEL SELECTOR TARGETING
matchLabels:
Target Matches: 3 Agents Targeted
k8s-prod-west-01
env: production, app: api
Hot-Reload Active
k8s-prod-west-02
env: production, app: worker
Hot-Reload Active
srv-prod-east-01
env: production, app: db
Hot-Reload Active
srv-staging-01
env: staging, app: api
Configuration Update Status:✓ Pushed to 3 matches via OpAMP (0 restarts)
Use Cases

Who Uses CollectorCtrl

Platform & SRE Teams

Manage OTel Collectors across dev, staging, and production from one dashboard. Roll out config changes to specific environment rings. Detect unhealthy agents before they impact telemetry pipelines.

Security & Compliance

Stream every action to your SIEM via OTLP. Audit who changed what config and when. Enforce RBAC with SSO group mapping.

Multi-Cloud Observability

Run the server on-prem or in your VPC. Agents connect outbound — no inbound firewall rules needed. Works across AWS, Azure, GCP, and private data centers.

Pipeline & Cost Governance

The control plane is where the observability bill is decided. Build custom OTel Collector binaries with the integrated OCB Builder, filter and sample before data reaches expensive backends, and deploy the right version to the right machine with fleet policies.

Getting Started

Up and Running in Minutes

No cloud account required. Runs entirely on your infrastructure.

1

Install the Server

Download the Windows installer or Linux tarball. The server runs as a native service. SQLite works out of the box.

# Linuxtar -xzf collectorctrl-server_*.tar.gzsudo ./install.sh
2

Install Agents

Deploy the Supervisor on each node. The installer registers it as a Windows Service or Linux systemd unit automatically.

# supervisor.yamlendpoint: wss://server:4320/v1/opampagent: executable: /usr/local/bin/otelcol
3

Manage from the UI

Open the dashboard at port 4321. Log in, view your fleet, create policies, and push configs — no SSH needed.

# Default loginhttps://your-server:4321admin / admin

Ready to control your fleet?

Download CollectorCtrl today and replace your SSH-and-scripts workflow with a governed control plane — neutral to any backend, free to use, and self-hosted.