Kubit vs Hex
Side-by-side trajectory, velocity, and editorial themes.
Kubit pivots from query builder to agentic analytics with the Lumos AI chat.
Kubit is a product-analytics platform that has spent the last quarter shifting from a manual report-builder model toward an agentic one. The headline move is Lumos Agentic AI Chat, which lets users describe reports in natural language instead of clicking through a builder. Alongside it, an AI Readiness framework continually scores how well a customer's metadata is prepared for that workflow.
Every directional release this quarter either ships agentic capability or removes blockers in front of it. AI Readiness keeps expanding its assessment surface (virtual events, breakdown fields) so customers can see exactly what gaps would limit Lumos. Enterprise-readiness work like granular Slack permissions and partial caching is clearing the path for production rollout rather than chasing new categories.
Expect Lumos to extend past chat into scheduled agent runs and proactive insights surfaced on dashboards, with a Slack or Teams entry point built on the new fine-grained permission model.
Hex bets the product on prompt-as-authoring: data apps are now one sentence away.
Hex is in the most aggressive AI-agent build-out of any analytics tool we track. The last month has stacked: repo connections as agent context, Generative Data Apps, prompt-to-dashboard, context suggestions, user memory, projects-as-context, and a CLI for programmatic context control. Around it, the surface has been extended with Hex-in-Claude, Hex-in-Cursor, a ClickHouse partnership, and Google Sheets export.
Hex is reorganizing itself around an agent that the user steers with prompts and grounds with context. Each release adds either more context channels (repos, projects, semantic models, memory, guides) or more places the agent can act (apps, dashboards, third-party clients). The product surface is being recast: notebooks remain, but the primary entry point is becoming the prompt. Expect Hex to keep stacking context sources and to start moving from authoring assist into autonomous, scheduled, agent-driven workflows.
Next plausible moves: agent-authored scheduled jobs or alerts, deeper integrations with semantic layer tools (dbt-style metric stores) as context sources, and more co-pilot embeddings in third-party editors. A pricing tier tied to agent usage is increasingly hard to delay.
See more alternatives to Kubit →
See more alternatives to Hex →