| Category | The AI Analytics Engine — you write down what data means, and it generates the stack under it | Agentic analytics on a context graph the platform discovers and keeps learning |
|---|
| Who it is built for | The whole organization, not one central team — ops, finance and product; spreadsheet users through ML engineers | Business teams — finance, marketing, sales, operations — asking without a BI project first |
|---|
| Primary interface | The agent you already use, over MCP — plus Credible Workspaces, dashboards, notebooks and reports for the people who want a UI. Every one of them reads the same model, and the model lives in your repository | Chat — in Genloop, in Slack, and from MCP clients including Claude Code and ChatGPT |
|---|
| Modeling language | Malloy — a modern programming language for data: imports, inheritance, public and private members, and queries that compose into new sources | None to author. The context graph is discovered from schema and documents, then refined by use |
|---|
| What is open | Open core. Malloy is open source, and we build and maintain Malloy Publisher — the open-source server for Malloy models, and where our agent skills and MCP retrieval tools are open source too, runnable in any agent with no Credible account. Your model is code in your repository, and Credible is in the Apache Ossie ecosystem for semantic interchange | Vendor-owned, and model-agnostic — it can run air-gapped, with no external LLM calls |
|---|
| How the model gets built | Model first: you write down what data means, and the engine derives the pipelines, storage and serving from it. Open-source MCP tools and agent skills help you capture that meaning from where it already lives, running in your coding agent | Auto-discovered, then corrected in a Review Center where the data team approves what it learned |
|---|
| Governance | One annotation on the source, in the same file as the logic it governs — no grant objects to declare, no rule to re-attach on every surface that exposes the data, no attribute table kept in step by hand. A row filter or an authorize gate over attributes the server resolves from verified identity, and everything reading that source inherits it: dashboards, notebooks and agents alike | Role-based access enforced per conversation, with a review loop over what it learns; SOC 2 Type II and ISO 27001 |
|---|
| Materialization and caching | One annotation on the source, in the same file as the logic it materializes — no derived-table block, no rollup definitions, no refresh triggers, no orchestration run to schedule. Optional per source: query your own warehouse directly, or hold a source hot in Credible’s own storage, which is how you get fast serving without buying or banging your head against a warehouse to get it | Reads in place and stores no copy, so performance stays with the source system |
|---|
| How an agent finds the right data | Search. Typed targets — source, dimension, measure, view, even a dimensional value — are matched against an index of the model and come back ranked, so an agent asks for what it needs instead of picking a model and touring it | The context graph, plus routing along investigation paths that have been run and verified before |
|---|
| Where the model can be used | One model served to every surface — agents over MCP, plus APIs, an SDK, embedded dashboards, notebooks and HTML data apps. Results carry an interactive UI resource (MCP Apps, the official extension), so a client that supports it renders a real chart or table instead of the model re-narrating rows | Chat, Slack, embedded analytics and MCP, with one shared context so a correction made in one place holds in the others |
|---|
| Scale and portability | Globally distributed, high-availability serving that scales horizontally — workers scale out under load rather than being sized in advance. Warehouse-agnostic on open-source Malloy, and the model is portable because the language is | Reads existing sources without migration; deployable in cloud, VPC, on-premises or air-gapped |
|---|
| What you pay for | Usage, not seats — unlimited users on every plan, so adding people never changes the bill. Three meters, pooled per organization and starting free: tokens, compute time and storage. Your agent’s own LLM tokens are never billed to you, and a query that runs on your own warehouse is not metered for the compute — only for the result it hands back | Credit tiers — a free monthly grant, then paid plans that each include a pool of credits |
|---|