Why we built cortex as a graph, not a warehouse

Relational databases are great at answering the questions you already know how to ask. The problem is that real business data is messier than rows and columns. A customer is connected to an account, a subscription tier, a support history, a usage pattern, and a sales rep. None of those relationships sit cleanly in a table.

Why we chose a graph

When we started designing Cortex, we made the deliberate choice to model data as a graph from day one. That meant giving up some of the familiarity and tooling that comes with relational systems, and making more decisions ourselves with less prior art to lean on.

What it unlocks

Every query on Cortex can traverse relationships that were never explicitly defined by the person asking. A question about churn risk can pull in support ticket frequency, login patterns, billing changes, and account age. The graph finds the connections.