If you run Fiddler or have it on an agent observability shortlist, get standalone availability, deployment options and price in writing now, because CrowdStrike's announcement answers none of them. CrowdStrike announced a definitive agreement on November 3 to buy Fiddler AI, and says Fiddler "will be sold as part of the Falcon platform as Falcon Observe, generally available in Q4 FY27." That is the only go-to-market plan either company has published.
CrowdStrike gives no price, saying only that payment is predominantly cash, with a portion in stock subject to vesting. The figure in circulation is roughly $400 million, from a paywalled Wall Street Journal report that we could only read through a secondary write-up. Treat it as reported and unconfirmed.
What CrowdStrike Is Buying and What It Says It Will Do
CrowdStrike is buying the layer that records and scores what an agent did, and it plans to pair that with the security product that can stop one. Agent observability is the practice of tracing an agent's decisions, reasoning and tool calls, then scoring them for accuracy and policy compliance. The release lists pre-deployment evaluation, tracing, drift and hallucination detection, audit evidence across first-party, third-party and coding agents, and token and spend tracking.
CEO George Kurtz calls Fiddler "the flight recorder for every agent." Same-day product news fills in the other half: CrowdStrike also announced an AI Kill Switch in Falcon Guardian, available first at the gateway and "soon on the endpoint." A second same-day deal, for the AI security testing firm Dreadnode, adds pre-deployment attack testing, with financial terms undisclosed by CrowdStrike and about $95 million in the Journal's reported figures.
The timing is tight. Both the close and Falcon Observe's general availability are planned for the same fiscal quarter. CrowdStrike's 10-Q period ended July 31, and counting forward from there, Q4 FY27 should end around January 31, 2027. CrowdStrike has not published a calendar date, so confirm it with your account team.
Why Neutrality Is the Term to Pin Down
Nine months ago Fiddler sold neutrality, and the Falcon plan puts that claim in question. When it raised a $30 million Series C in January, Fiddler said it would focus on a "neutral control plane for compound AI systems." Its homepage still calls the platform "model- and cloud-agnostic," working with Azure OpenAI, Amazon Bedrock, LangGraph and "100+ other providers," and it lists Datadog, Databricks and Google Cloud among its integrations and partners.
The CrowdStrike release uses neither word. It names OpenTelemetry instrumentation with support for LangGraph, Amazon Bedrock, AWS Strands and Google ADK. The list may only be illustrative, but Azure OpenAI is missing from it, so a Microsoft-heavy shop should ask directly.
Fiddler CEO Krishna Gade's post about the deal says "the needs that brought you to Fiddler remain central to our mission" and calls security "a natural extension of this work." It does not address standalone sales, deployment or vendor neutrality.
The strongest case for the deal is real. In our August comparison of agent monitoring tools, six of the seven products could read a trace and could not stop a run. A Falcon customer who gets traces correlated with identity, cloud and runtime data next to a kill switch has one audit trail and one enforcement path, and that is hard to assemble from separate vendors. If you already standardized on Falcon and your agents run on the named frameworks, this may be good news.
The owner may change, though. If an ML platform team runs Fiddler at your company and security runs Falcon, the contract and the data could move between them. Fiddler's traces can hold prompts, outputs and tool inputs in fields such as gen_ai.llm.input.user, gen_ai.llm.output and gen_ai.tool.input, so your privacy lead will want to know who can read that record inside a security platform, and for how long.
Deployment Is the Largest Open Risk for Regulated Customers
Fiddler's in-environment deployment is the feature most likely to matter if you are regulated, and the release does not mention it. Fiddler's homepage lists SaaS, VPC and on-premises on its Enterprise plan, names AWS GovCloud separately, and claims "Zero" data leaves the customer's network. Its government page adds air-gapped deployments, and its Centor evaluation models "run inside your environment" with no external API calls.
The release keeps the model claim, promising evaluation costs down by up to 98% "without external LLM calls." That 98% is a vendor figure. The words on-premises, VPC, GovCloud and air-gapped do not appear in the release. A deal announcement may simply leave out that level of detail, but for now nothing public commits Falcon Observe to the deployment modes you may have bought Fiddler for.
Fiddler's site names Nielsen, Qualtrics, American Family Insurance and the Department of Energy among its customers, and those are the kinds of accounts for which this question is a contract term.
What the Last Round of Deals Tells You
Recent deals do not let you assume a standalone product survives. Cisco's Galileo purchase ended with the product renamed Splunk Agent Observability, on a page with no guidance for existing Galileo customers. CrowdStrike's own closest precedent, Pangea in September 2025, was announced as "part of the Falcon platform," and that release was also silent on standalone availability and existing customers.
A September buyer's guide from Decryption Digest says Lakera, Prompt Security, Aim and CalypsoAI are no longer sold as independent SKUs, though it attaches no specific citation to that claim. An October comparison on DeepInspect's blog disagrees on Lakera, saying its runtime layer, now Check Point AI Guardrails, is "available separately." Ask each vendor before you rely on either account.
Langfuse and Traceloop are the counterexamples. When ClickHouse bought Langfuse in January, Langfuse's FAQ said "Same product, same endpoints, same contracts" and "Self-hosting is a first-class path." Traceloop's post on joining ServiceNow said "We intend to honor all obligations to customers and continue to sell the Traceloop functionality." Fiddler's post contains nothing comparable yet. You can reasonably ask for it.
On price, the reported $400 million is about four times Fiddler's $100 million in total funding, and well under the $915 million Dynatrace agreed to pay for Arize in August, a deal we covered here. Fiddler has disclosed no revenue, only that it grew more than four times over 18 months, so no revenue multiple can be calculated.
What You Would Pay Today and What to Keep Portable
Fiddler's public price is low and easy to record, which makes it the baseline to protect. The Developer plan is $0.002 per trace with SaaS deployment listed, and Enterprise is "Contact sales." Falcon Observe has no published price.
Here is the same workload from our monitoring comparison: 50,000 runs a month, about 2.4 million billable data points, and ten engineers. Prices were read from each vendor's page on November 3, 2026. The units differ, so read this as an order of magnitude.
| Option | Published rate | This workload | Self-host |
|---|---|---|---|
| Fiddler Developer | $0.002 per trace | About $100/month if each run is one trace | Enterprise only (on-premises or VPC) |
| Langfuse Core | $29/month, 100k units, then $8 then $7 per 100k | About $199/month | Yes, open source |
| LangSmith Plus | $39 per seat, trace overage not listed on the page | $390/month in seats, plus traces | Enterprise only |
The portability work is small if you do it now. Fiddler rejects traces that omit application.id or fiddler.span.type, and most of its other fields use the optional gen_ai.* namespace. Its OTLP integration takes standard exporter settings. So if your agents emit OpenTelemetry through a collector you control, sending a copy to a second backend is a configuration change. Custom metrics written in Fiddler's query language and any scores from Centor models are a different matter, and you should expect to rebuild those.
What to Do Before the Close
Send your questions while Fiddler still has a reason to answer them in writing.
This Week:
- Pull your Fiddler order form and find the assignment, change-of-control, renewal and price-protection clauses. Have your procurement lead note the renewal date against the January window.
- Send your account team five questions: Will Fiddler stay available without a Falcon subscription? For how long? Will SaaS, VPC, on-premises, GovCloud and air-gapped all carry over to Falcon Observe? Is Azure OpenAI and every provider you use still supported? Does the $0.002 Developer rate or your Enterprise rate survive?
- If you are mid-evaluation and not a Falcon customer, tell your vendor shortlist this deal is a selection factor, and add one option with no security platform attached.
This Month:
- Route agent telemetry through your own OpenTelemetry collector and send it to a second backend for one production agent. Self-hosted Langfuse is the cheapest way to test this.
- Export your evaluator definitions, custom metrics and alert rules into version control, and record which depend on Centor models. Our audit logging guide lists the events you need to retain regardless of vendor.
- Have your privacy lead and CISO agree who may read prompt and output content if traces move into a security platform, and set retention before anyone else does.
Before Renewal:
- Ask for the Langfuse-style sentence in your contract: same product, same endpoints, same terms for a stated period, with a termination right if a deployment mode you use is withdrawn.
- Ask CrowdStrike for a reference from a former Pangea customer, and find out what happened to their contract and product after the deal closed.
- If you run Falcon and Falcon Guardian, price Falcon Observe against your current tracer once a price exists, and test the identity and runtime correlation on your own agents before you consolidate.
The Bottom Line
At least six agent observability vendors have agreed to sell in 2026: Galileo to Cisco's Splunk, Arize to Dynatrace, Langfuse to ClickHouse, Traceloop to ServiceNow, Helicone to Mintlify, and now Fiddler to CrowdStrike. A collector you control is the protection that works under any of those owners, because it lets you change backends without touching your agents.
CrowdStrike is buying for security. If that matches your problem, Falcon Observe may be the shorter path. If you bought Fiddler to serve an ML platform team across several clouds, get its answer on paper before the close, which could come any time up to roughly the end of January because that fiscal quarter has already started. Send the five questions this week.
Continue Reading
- Dynatrace to Acquire Arize for $915M to Expand AI Observability
- Cisco Buys Galileo: Why AI Observability Just Became Mandatory
- Best AI Agent Monitoring: Langfuse, Then a Real Kill Switch
- AI Observability Pricing: Same 10 GB, $49 or $930
- Agent Audit Logging: Platform Logs Miss the Decision You Must Prove
- NeMo Guardrails vs Guardrails AI vs Lakera: Buy the Detector