Features
Built for the way OTel actually works
Upstream OpenTelemetry with a control plane around it. No middleware or proprietary agent in between.
Build or import it
Drag components onto the canvas, or write the YAML by hand. Both stay in sync, so you can work whichever way you prefer.
AI assistance
Describe what you want in words, not YAML, and the agent builds it against your real config. Then it checks its own work, looping on schema errors until the config is valid. Nothing broken reaches you.
Remote fleet control
Push validated configs to collectors anywhere, over a live connection Telflo maintains. Run the supervisor on hosts and VMs, or Bridge Fleet on Kubernetes, where it works the way clusters already do.
Testing
Run a change against sample or uploaded telemetry on the real collector, and check the processed output is what you expect.
Validation
It validates against the real OTel schema and type-checks references. Broken configs never leave the editor.
Rollbacks
Something breaks? Restore the previous config across the fleet in one click.
Staged rollouts
Pin a new version to a few collectors first, confirm they are healthy, then promote it to the whole fleet.
Versioning
Every change is versioned and audited, so every fleet keeps a full config history.
Get started
Ready to run a real control plane?
Start building your first OpenTelemetry pipeline in the editor. No install, no credit card. Bring the collector config you already run.