The use case: how LangChain deploys Hex
LangChain uses Hex's agentic notebooks and data apps as its single analytics platform, replacing a legacy BI tool. The Notebook Agent rebuilt dashboards from legacy YAML files, and teams across the company self-serve data, including customer 360 and deployed engineering dashboards.
More reported results
Figures published in Hex’s case study. They are not independently measured by usedby.
90% of the migration completed by the Notebook Agent, converting YAML files from the legacy BI platform into production-ready Hex dashboards on first pass
100% of the company has access to data via Hex
88% reduction in build time for the customer maturity matrix, from an estimated 3 days in Python to 3 hours in Hex
~30% increased customer onboarding speed
In the customer’s words
Context Studio changed how we manage agent performance. It surfaces gaps, proposes fixes, and suggests exactly where to add context. The agent improves without me auditing every conversation.Being able to copy YAML files and give them to the Hex Agent to fully rebuild the dashboards helped us complete 90% of the migration. It was the best migration I've ever done.Hex’s developer-first mentality has been awesome. Hex has great visual and design sensibility. The ability to use Hex in any way we choose is valuable because now we can connect into Hex via my favorite dev tools.It took me a week to make several changes in our legacy BI tool that were nowhere near as impactful as everything I built with Hex's agents in a week.Hex’s agent increased data access for everyone at LangChain, while giving us the confidence that users were getting accurate answers with trusted data.Hex's agent made our legacy BI migration seamless. It rebuilt dashboards automatically, reducing months of manual work to six weeks.Other AI tools used by LangChain
Other public relationships recorded on usedby.
Explore LangChain’s AI stack
Hex users in DevTools & Infrastructure
Companies in the same sector, with public evidence.
See all Hex customers
Go straight to the source
Based on Hex’s published case study. We check the public evidence; the results are reported by the vendor.
hex.tech- Source published
- Jun 25, 2026
- Last checked
- Oct 24, 2026
Open source capture What the story claims, and what we checked
What we compared with the page.
- The figure: 6 weeksChecked
The figure is on the page; its label is our wording.
- The passage quoted aboveChecked
Copied word for word from the page, near the name of LangChain.
- The numbers in our summaryChecked
Each one is printed on the page.
- The publication dateChecked
Read from the page’s own metadata, never guessed.
- LangChain uses HexChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
Within the first pass, the agent was able to recreate roughly 90% of the dashboards — including queries, charts, and structure — leaving only review and refinement to the team.