
GlassFlow is one data layer for both sides of the agent: GlassFlow Tares feeds agents correlated data, and GlassFlow Rius traces and debugs every run.
Works with the tools you already use.
Thomas Dohmke
Co-founder & CEO
Entire
products
GlassFlow Tares
Instead of your agent firing dozens of live tool calls at runtime (slow, expensive, inconsistent), GlassFlow Tares prepares and delivers exactly the data each agent needs, already correlated across every source. One clean read replaces many brittle ones: less latency, fewer tokens, more reliable decisions.
Open source, self-hostable, and built on a production streaming core.

products

GlassFlow Rius
Once agents are live, GlassFlow Rius tells you what they did, why they failed, and how quality is changing. Rius is built for any agent, running from short chat sessions to long-running agents that span across hours or days.
Live metrics on running agents (not just the completed minority), heartbeat detection that flags a frozen agent instead of hiding it, and bidirectional MCP so Claude Code, Cursor or ChatGPT Codex can query a failure and open a PR with the fix.
Every trace kept as long as you need it, not capped at 30 days
Frequently Asked Questions
Does Framer support XYZ?
GlassFlow is the data infrastructure for AI agents in production. It has two products: GlassFlow Tares, which feeds agents correlated data from every system they touch, and GlassFlow Rius, which traces and debugs what agents do once they’re running.
What’s the difference between GlassFlow Tares and GlassFlow Rius?
Is GlassFlow open source?
What makes GlassFlow different for long-running agents?



