Hex

Hex began as a better notebook. SQL and Python cells in one document, dataframes flowing between them, the output publishable as an app without exporting anything anywhere. The AI layer arrived in stages. Magic handled prompt-to-SQL and error explanation first. The Notebook Agent, which landed in late 2025, does the multi-step version: you give it a question and it runs the full loop of query, execute, chart and write-up, inside a project it can already read.

What separates it from a dozen text-to-SQL startups is the semantic model integration. Hex reads and syncs metric definitions from dbt MetricFlow, Cube and Snowflake Semantic Views, so when someone asks about revenue the agent applies the definition the data team already wrote rather than inferring a join across three tables and quietly getting it wrong. Context Studio sits above that for observing, testing and deploying the agent setups you expose to business users. That governed path is why data leads take Hex seriously in rooms where they dismiss chat-with-your-data demos out of hand.

The cost model needs watching. Professional runs $36 per editor per month, Team $75, and every paid seat carries a monthly credit grant that agent runs draw down, with top-ups sold separately. Add warehouse compute and a mid-size analytics team is spending real money. Hex is also deliberately not a data platform: no ingestion, no transformation scheduling, no catalog. Fine for a mature stack. Wrong first purchase for a team that has not built one.