Back to products
Trufflow

Trufflow

Map how software gets used across teams Analytics • SaaS • Business Intelligence 44 234 Mintlify Knowledge infrastructure for AI agents Notes • Text Editors • GitHub Justin Torre We have been using the editor every day and it's an absolute game changer!!! I love this product and I think it's one of the leading editor experiences I have tried. Also, the ability to publish customer facing docs is just amazing.

Overview

What it is

Trufflow helps you map how internal software gets used across teams. Track usage, adoption, and dependencies to understand how apps support work across teams and where they deliver the most impact.

Intent

I need it when

Connect infrastructure cost data to engineering workflows without building custom data pipelines

Trufflow is a hosted service requiring no agents, sidecars, or traffic interception; it reads from existing OTel pipelines and AWS CUR exports, integrating cost data into Datadog, Grafana, or Prometheus without additional instrumentation

Identify which service components or operations are driving the highest infrastructure costs

Trufflow enriches individual traces with cost attributes at the span level, showing cost-per-request and cost breakdown by operation (e.g., batch.process consuming 63% of request cost), making cost visible in existing observability tools without context switching

Validate that infrastructure cost optimizations actually reduced costs at deploy time

Trufflow correlates OTel spans with AWS CUR exports to attribute cost impact to specific deploys, eliminating the 2-3 day wait for monthly billing data and enabling engineers to confirm optimization results immediately rather than relying on spreadsheets and best guesses

Detect cost regressions that performance monitoring misses

Trufflow surfaces cost increases that occur even when latency and error rates remain flat, providing cost as a native signal in the observability workflow to catch invisible cost regressions

Drop

Not a fit when

  • You do not run Kubernetes on AWS (EKS); product is currently EKS-only with GKE and AKS on roadmap
  • You do not use OpenTelemetry-compatible observability tools (Datadog, Grafana, Prometheus) or equivalent
  • You have no significant monthly cloud spend or cost optimization is not an active engineering concern
  • You cannot provide read-only access to AWS CUR exports and OTel collector pipeline
  • You need real-time cost attribution; Trufflow requires AWS billing data which has inherent delays
Commercials

Pricing

Pricing not specified