Overview¶

Ampora is an OpenTelemetry-first OpAMP management server with a visual collector pipeline analyzer and controlled, auditable fleet rollouts. It gives platform, observability and SRE teams one place to:

1. Understand what every collector in their fleet is currently doing — what it receives, processes and where it exports — without grepping through YAML.
2. Manage that fleet at scale — versioned configurations, dynamic groups, policy-gated rollouts, certificate rotation, package distribution.
3. Operate the OpAMP protocol as a vendor-agnostic remote-management plane for any OpAMP-capable agent, not only the OpenTelemetry Collector.

If you operate dozens, hundreds or thousands of collectors and you have ever wondered "which agents are running yesterday's broken config?" or "can we roll out this exporter change to 5 % of the fleet first?" — that is the question Ampora is built to answer.

What Ampora is not¶

To set expectations honestly:

• Not an APM or observability backend. Ampora does not store your traces, metrics or logs. It manages the agents that send them. Point your collectors at any OTLP-compatible backend (Jaeger, Tempo, Prometheus, Datadog, Honeycomb, …) — Ampora doesn't care.
• Not a vendor lock-in. YAML is the source of truth, exportable at any time. Ampora's visualizer is a derived view, never a proprietary DSL.
• Not a config templating engine. Templating, secret-injection and per-environment overrides belong upstream — in Helm, Kustomize, Argo CD, GitHub Actions, your CI. Ampora ingests rendered YAML and ships it to agents.

Where to go next¶