# Telflo > Telflo is the vendor-neutral control plane for OpenTelemetry Collectors: a visual editor, validation against real collector binaries, pipeline testing, versioning, and remote fleet management for OTel Collector configurations, with AI assistance and a CLI and MCP server for coding agents. Telflo (https://telflo.com) helps platform and observability teams build, test, and roll out OpenTelemetry Collector configurations from one place. A configuration is built visually or imported from YAML, validated against the exact collector distribution and version it will run on, tested by running sample telemetry through a sandbox collector, versioned, and deployed to fleets of collectors over OpAMP. Telemetry never passes through Telflo: it flows from your collectors straight to the backends you choose. Ways to use Telflo: - Web app: https://telflo.com/register. Free for the first 15 collectors with every feature included; larger fleets are priced per collector, never per gigabyte. - CLI: the telflo command pushes, validates, tests, and deploys configurations from a terminal or CI pipeline (https://docs.telflo.com/docs/cli). - MCP server: Claude Code, Cursor, claude.ai, and other MCP clients can validate, test, publish, and deploy configurations as tool calls (https://docs.telflo.com/docs/mcp). - Playground: https://telflo.com/playground explores the product on sample data with no account. ## Product - [Home](https://telflo.com/): Telflo is the vendor-neutral control plane for OpenTelemetry Collectors. Build, test, and roll out real OTel Collector configs from one place, with AI assistance. Route your data to any backend you choose. - [Features](https://telflo.com/features): Everything Telflo does: build or import collector configs, AI assistance, remote fleet control, testing, validation, version history, and rollback. - [Use cases](https://telflo.com/use-cases): How teams use Telflo: cut observability costs by up to 50%, test every pipeline change before it ships, consolidate backends, mask PII at the collector, avoid vendor lock-in, and stop hand-editing YAML. - [For agents](https://telflo.com/agents): Your OpenTelemetry fleet, from your Claude console. The agent builds, tests, and deploys what it collects, and Telflo checks every change on the collector version it runs. - [Flows](https://telflo.com/flows): A library of pre-built OpenTelemetry Collector pipelines: the components, the order, and the reasoning. Open one in Telflo, adapt it, test it, and push it to your fleet. - [Pricing](https://telflo.com/pricing): Telflo is free for your first 15 collectors, every feature included. Bigger fleets get a per-collector price sized to them. Data volume never changes your bill. - [Changelog](https://telflo.com/changelog): See what's new in Telflo: features, improvements, and fixes. - [Blog](https://telflo.com/blog): Posts about OpenTelemetry, observability, and building Telflo. - [For partners](https://telflo.com/partners): Telflo is an independent control plane for OpenTelemetry Collectors. If your platform ingests OTel data, Telflo helps your customers build, test, and roll out the pipelines that deliver it to you. - [Playground](https://telflo.com/playground): Explore the full Telflo product with sample data: visual pipeline editor, behavioral testing, and remote fleet management. No account needed. - [Public editor](https://telflo.com/public-editor): Public visual editor for OpenTelemetry Collector configurations. - [Book a demo](https://telflo.com/demo): See how Telflo cuts OpenTelemetry config time from hours to minutes. Book a 30-minute walkthrough with the team. - [Create account](https://telflo.com/register): Create your Telflo account. ## Documentation - [Telflo documentation](https://docs.telflo.com/): Product docs: getting started, building configurations, testing, fleet management, the AI assistant, the CLI, the MCP server, and organization settings. - [Documentation index for LLMs](https://docs.telflo.com/llms.txt): Every documentation page with a one-line summary. - [Quickstart](https://docs.telflo.com/docs/getting-started/quickstart): Build an OpenTelemetry Collector configuration and deploy it to a running collector in a fleet. - [CLI](https://docs.telflo.com/docs/cli): Push, validate, test, and deploy collector configurations from your terminal, your CI pipeline, or an AI coding agent. - [MCP server](https://docs.telflo.com/docs/mcp): Connect an MCP client to Telflo so an agent can validate, test, publish, and deploy collector configurations as tool calls. ## Flows Prebuilt, validated OpenTelemetry Collector configurations, each solving one problem. Every page explains the components, their order, and the operational gotchas. - [Replace vendor agents on your VM fleet](https://telflo.com/flows/host-fleet-monitoring): Scrapes CPU, memory, load, disk, filesystem, and network metrics plus system and application logs on every VM. - [Redact PII before telemetry leaves the network](https://telflo.com/flows/pii-redaction-gateway): Masks emails, card numbers, SSNs, bearer tokens, AWS keys, and IPs in log bodies and span attributes at a central gateway, before telemetry leaves your network. - [Survive backend outages with a persistent queue](https://telflo.com/flows/outage-proof-pipeline): Replaces the default in-memory exporter queue with a disk-backed queue that survives collector restarts, sized in items instead of opaque requests. - [Ship OTel data to ClickHouse](https://telflo.com/flows/otel-to-clickstack): The ClickStack (HyperDX) ingestion collector as upstream ships it: parses JSON log bodies into attributes, infers severity from level fields or the body text, and routes browser session-replay events to their own ClickHouse table. - [Run a cluster gateway for Kubernetes](https://telflo.com/flows/k8s-production-gateway): Cluster-level gateway that receives OTLP from apps and node agents, tails pod logs, stamps deployment.environment, deletes a PII attribute, and ships everything to your OTLP/HTTP backend with a debug tap on logs. - [Collect per-node telemetry with a DaemonSet](https://telflo.com/flows/k8s-node-agent): Per-node DaemonSet that scrapes kubelet and host metrics, tails pod logs with the container parser and file_storage checkpoints, enriches everything with k8sattributes, and forwards to the in-cluster gateway. - [Generate RED metrics from spans](https://telflo.com/flows/span-metrics): Generates RED metrics from spans with the spanmetrics connector: explicit latency buckets, HTTP dimensions, exemplars, and a 10k cardinality cap, after normalizing span names so route explosions don't inflate the metric space. - [Dual-ship to two backends during a migration](https://telflo.com/flows/dual-backend-migration): Fans every trace, metric, and log out to both the legacy agent and the new OTLP/HTTP backend so the two can be compared side by side during a migration. - [Move from Datadog to Elastic without a monitoring gap](https://telflo.com/flows/datadog-to-elastic-migration-bridge): Accepts traffic from the Datadog Agents you already run and dual-ships every trace, metric, and log to both Datadog and Elastic, so the two can be compared on identical data before you cut over. - [Move from Datadog to ClickStack without a monitoring gap](https://telflo.com/flows/datadog-to-clickstack-migration-bridge): Accepts traffic from the Datadog Agents you already run and dual-ships every trace, metric, and log to both Datadog and ClickStack, so the two can be compared on identical data before you cut over. - [Fail over to S3 when ClickHouse backs up](https://telflo.com/flows/clickhouse-failover-gateway-s3-overflow): A ClickHouse gateway that fails each signal over to an S3 overflow bucket when inserts back up and fails back on its own once ClickHouse recovers, so an ingest stall never becomes data loss. - [Ship OTel data to Gigapipe](https://telflo.com/flows/ship-otel-data-to-gigapipe): Ships logs, metrics, and traces over plain OTLP to Gigapipe, an open-source backend that stores them in ClickHouse and answers Loki, Prometheus, and Tempo queries. - [Monitor Supabase](https://telflo.com/flows/monitor-supabase): Scrapes the Supabase Metrics API and receives the OTLP log drain, tags both with the project ref, and ships them to any OTLP/HTTP backend. ## Blog - [Monitoring Supabase with the OpenTelemetry Collector](https://telflo.com/blog/monitoring-supabase-with-the-opentelemetry-collector) (2026-10-17): Scrape the Supabase Metrics API and catch the OTLP log drain with one collector. Every receiver, processor, and pipeline explained, with a ready flow. - [Run Your Collector Fleet From an Agent](https://telflo.com/blog/an-mcp-server-for-your-collector-fleet) (2026-10-12): AI agents can read telemetry almost anywhere now; nearly every observability vendor ships an MCP server for it. But managing your OpenTelemetry collectors is still a very manual process today, with no agentic operations. The Telflo MCP server and CLI give an agent that side too: edit collector YAML, validate it on a real binary, test it on sample data, and deploy it to your fleet. - [LogQL, PromQL and TraceQL on ClickHouse](https://telflo.com/blog/grafana-on-clickhouse-with-gigapipe) (2026-09-28): Grafana is the visualization layer most teams already run, and ClickHouse keeps coming up as the telemetry store. Gigapipe connects the two: it stores logs, metrics and traces in ClickHouse and serves the Loki, Prometheus and Tempo APIs, so Grafana reads from it through its built-in datasources. We built a ready-made collector config for getting data in. - [Why We Built Flows](https://telflo.com/blog/why-we-built-flows) (2026-09-07): Writing the collector config is still the hardest part of adopting OpenTelemetry. Flows is our curated library of prebuilt, validated collector pipelines: about a dozen so far, one per use case, with more on the way. - [Why Observability Keeps Ending Up on ClickHouse](https://telflo.com/blog/why-observability-keeps-ending-up-on-clickhouse) (2026-08-11): Netflix, OpenAI, Anthropic, and Uber all store their telemetry in the same database, and so does nearly every observability product launched in the last five years. The reasons are mechanical. Here's how ClickHouse actually works, what it does to the bill, and when it's still the wrong call. - [Span Metrics Without the Cardinality Explosion](https://telflo.com/blog/span-metrics-without-the-cardinality-explosion) (2026-06-25): Turn the spans you already emit into RED metrics with the spanmetrics connector, and avoid the one mistake that quietly multiplies your time series into a five-figure metrics bill. - [Open Telemetry Fleet Management or "The Art of Managing Chaos"](https://telflo.com/blog/fleet-management-effectively-managing-chaos) (2026-06-06): Open Telemetry Fleet Management - [Drop it at the edge: cutting your observability bill with OpenTelemetry](https://telflo.com/blog/cutting-observability-costs-at-the-edge-with-ottl) (2026-06-01): The cheapest place to cut your observability bill is the Collector, not the backend. A practical guide to dropping noise with OpenTelemetry, then flipping to full fidelity when an incident hits. - [Monitoring Kubernetes with the OpenTelemetry Collector](https://telflo.com/blog/monitoring-kubernetes-with-the-opentelemetry-collector) (2026-05-02): The agent + gateway collector pattern for Kubernetes. Every receiver, processor, and pipeline explained, with two ready templates. - [Welcome to the Telflo blog](https://telflo.com/blog/welcome-to-the-telflo-blog) (2026-04-29): OpenTelemetry deep dives, collector config patterns, and what's new in Telflo. Starting with a clean OTLP-to-multiple-backends setup. ## Optional - [Terms of Service](https://telflo.com/terms-of-service): Telflo terms of service and conditions of use. - [Privacy Policy](https://telflo.com/privacy-policy): Telflo privacy policy and data practices. - [Cookie Policy](https://telflo.com/cookie-policy): Telflo cookie policy and tracking practices. - [Sub-processors](https://telflo.com/subprocessors): Third-party sub-processors Telflo uses to process customer data.