July 2026 at Bindplane: A new pipeline editor, friendlier pricing, and a Blueprints library

The new Advanced Pipeline Editor went live for all paid plans, we launched a public Blueprints library of ready-made pipeline patterns, we reworked plan pricing and raised the Free tier to 100 GB/day, and the source and processor catalog grew with an AWS Neuron source, an AWS CloudWatch metrics source, and a full set of XML processors.

None of these are flashy on their own. Together they add up to a month focused on what engineers actually ask us for: better visibility into the pipeline they already have, a faster way to build new ones, and fewer reasons to think about the bill.

What shipped

The Advanced Pipeline Editor is the headline. If you have ever tried to reason about a configuration with dozens of sources, processors, and destinations, you know the default view runs out of room fast. The new editor gives you a canvas you can pan, zoom, and re-center, a sidebar that lists every component with search, and a filter that collapses the view down to a single component and the routes attached to it. It also lets you embed processors directly in routing nodes, so branch-specific processing lives on the branch where it runs instead of floating at the top of the config. It is now live for all paid plans, and Ryan wrote up the launch in detail in The Advanced Pipeline Editor Is Here.

Alongside that, we changed the economics. The Growth plan is now $499/month and includes 200 GB/day of combined usage across logs, metrics, and traces, with the collector count staying at 50. More importantly for people kicking the tires, the Free plan daily ingest limit went up to 100 GB/day. That is a real amount of telemetry, enough to run an actual workload through Bindplane and see what the pipeline does before any money changes hands. You can see the current plans on the pricing page.

The third launch is the Blueprints library, a public catalog of ready-made pipeline patterns. Each Blueprint bundles the processors for a specific job, parsing, filtering, normalization, enrichment, or data reduction, and you can filter the catalog by source, log type, destination, and use case. There are patterns for Windows Events, CrowdStrike, Okta, Palo Alto, syslog, Kubernetes, and more, including SIEM-oriented ones that reduce log volume before it reaches Google SecOps or ClickHouse. Paired with the refreshed Full-Pipeline Blueprints apply flow, you can go from a raw source to a cleaned, routed pipeline in a few clicks instead of wiring processors by hand.

New features and integrations

The integrations also grew in a few directions worth calling out.

• AWS Neuron source, collects metrics from AWS Trainium and Inferentia accelerators, so AI/ML workloads running on Inf2 and Trn1 instances get first-class coverage in your pipelines. Docs.
• OTTL XML processors, a full set of UI processors for parsing and reshaping XML, including a Windows Events parser, Parse Simplified XML, Slice to Map, and element-level transforms. Docs.
• Windows Events improvements, streaming mode for Winevt sources, new channel enrichment, and a better default poll interval for forwarded events. Docs.
• Drain processor, clusters high-volume logs into templates to cut noise and volume, now with storage-extension support so its state survives a restart. Docs.
• AWS CloudWatch metrics source, pull CloudWatch metrics into your pipelines along with pre-existing support for logs. Docs.

What we wrote and where we showed up

On the blog, we continued the series on monitoring AI agents with a new guide, Claude Code Monitoring at Scale: Gateways and Routing With OpenTelemetry. It picks up where the earlier laptop-collector setup left off and shows how to put a BDOT Gateway in the middle: cost metrics route to Google Cloud Monitoring, the full event stream goes to Dynatrace, and sensitive fields get redacted at the edge before anything leaves the machine. It also covers how to point Claude Cowork at the same gateway. Read the full tutorial, here.

On the speaking side, Craig led the Dynatrace Public Sector Monthly Tech Talk this month, walking through how to build open, OpenTelemetry-native pipelines for government and public-sector teams. It is a good example of the case we keep making: telemetry pipelines built on OTel run anywhere and stay yours, regardless of where the data lands.

Ryan also wrote up the Advanced Pipeline Editor launch in The Advanced Pipeline Editor Is Here: One View, Every Pipeline. The post walks through the rebuilt editor: your whole configuration as one interactive graph, click any component to isolate just the pipeline it belongs to, a searchable component sidebar, and a throughput switcher that shows what is flowing through each pipeline while you edit. If you manage configs with many sources and destinations, it is worth a read before your next big change.

What we're working toward

Next up on the calendar: Tony is speaking on supply chain security at GR Web Dev in Grand Rapids on July 27, an hour-long session at Start Garden. If you are local, come say hi.

Otherwise, the best thing you can do is take July's changes for a spin. Open a large config in the new editor, point the Free tier at a real workload now that the ceiling is higher, and let us know in the community Slack what works and what does not.