00Open core strategy

GenBI you can read, run, and keep.

Wren AI is open core. The context engine that answers your questions is open source, and every commercial plan runs that same engine, in our cloud or yours.

  • Engine open source on GitHub
  • Your MDL lives in your git
  • Cloud, VPC, or air-gapped
Wren AI platformCommercial · Teams & enterprise
GenBI Appsagentic modecontext prepgovernance
Context engineMDL · text-to-SQL · MCP · CLI
Open source · Individuals
Your data sources · 20+ connectors · no migration
Read it
Run it
Keep it

One engine / open core, commercial platform

GitHub stars
16K+
Release cadence
Weekly
Discord members
1,700+
Community growth
5× YoY
01Why it matters

Cloud-locked platforms ask for trust. Open core earns it.

Every chatbot asks you to trust a closed platform. Six questions show the difference between asking for trust and earning it.

Cloud-locked AI analytics
Open-core Wren AIOpen core
Can you read the code?
Closed. You see outputs, not logic.
Open source on GitHub, end to end.
Where do your definitions live?
Inside the vendor's platform.
MDL files in your own git repo.
What happens if you leave?
Export data, rebuild everything.
Keep the engine and your models.
Where can it run?
The vendor's cloud only.
Cloud, your VPC, or air-gapped.
How do you evaluate?
Book a demo, wait for sales.
Run it locally today, free.
Who improves it?
One vendor's roadmap.
A core team shipping weekly, plus 1,700+ community members.
The evidence

12 platforms, 22 buyer factors, one guide.

We scored open-core Wren AI against cloud-locked AI analytics platforms across 22 buyer-grade factors. The full tally is free to download and circulate with your team.

02The open core

LLMs don't know your data. The open core does.

The open-source engine sits between agents and your data, enforcing shared definitions and metric logic at query time. Built for individual developers and used through the CLI, it's the layer you can read on GitHub.

  • Grounded text-to-SQL, no schema-guessing
  • MDL: metrics and definitions as code, in your git
  • CLI & MCP server for your own agents, no UI required
  • 20+ data sources, 60+ AI agents, any LLM
Native Wren AI connectors for 20+ data sources, warehouses, and tools

Connect once / 20+ data sources, queried in place

03The boundary

What's open, what's commercial. Published, not fine print.

Everything commercial stacks on the open core, and the boundary between them is published. The bottom layer is the one you have to trust, which is why it is the one you can read.

Enterprise operationsCommercial · Teams & enterprise
Access control: users & groupsRow & column-level securityAdvanced security & auditSupport & SLAsCloud · VPC · air-gapped
Platform & experienceCommercial · Teams & enterprise
GenBI UIDashboardsEmbedded & APIs
Scenario AI harnessesCommercial · Teams & enterprise
GenBI AppsAgentic modeContext preparation
Context engineMDL semantic modeling · Text-to-SQL pipeline · MCP server · CLI · 20+ connectors · LLM-agnostic
Open source · Individuals · Free forever

For individual developers, used through the CLI and MCP server (no UI). The part you have to trust is the part you can read, and this engine runs without us.

Your data · queried in place · never moved

The engine stays open because the engine is what earns your trust.

04Three ways to run it

Start where your constraints are.

Every path runs the same context engine. Models you build on one carry to the next, so you can move without rebuilding.

Path 01 / Open source

Wren AI OSS

For individual developers building their own agents. The engine and CLI, no UI.

  • Free for individual developers
  • Context engine, MDL, MCP server, and CLI (no UI)
  • Community support on Discord
Recommended
Path 02 / Cloud

Wren AI Cloud

For teams: the full GenBI platform, managed by us. Connect a database and ask your first question today.

  • Starts free, no infrastructure
  • GenBI Apps, agentic mode, and dashboards
  • Upgrade as your team grows
Path 03 / Self-hosted

Enterprise Plus

For enterprises: the full platform inside your network, air-gap ready, with unlimited users.

  • Runs in your VPC or on-premise
  • Access control, row & column-level security
  • Licensed by concurrent sessions, not seats
FAQ / Open core

The questions skeptics should ask.

The context engine, the part that turns a question into governed SQL, is open source on GitHub for individual developers, used through the CLI. The commercial platform is built on that same engine and adds the advanced AI for specific scenarios (GenBI Apps, agentic mode, context preparation) plus the UI, access control, row- and column-level security, and support. One engine, two layers: open source built for individual developers, the commercial platform built for teams and enterprises.

Open source: the context engine for individual developers, used through the CLI and MCP server (no UI), with MDL modeling, a core text-to-SQL pipeline, and 20+ connectors. Commercial: the advanced AI harnesses (GenBI Apps, agentic mode, AI-assisted context preparation), the UI and dashboards, embedded APIs, access control with user and group management, row- and column-level security, advanced security, and support, delivered as Wren AI Cloud or self-hosted Enterprise Plus.

Your MDL files already live in your git repo, your data never left your warehouse, and the open-source engine keeps running without a license. You lose the commercial platform (GenBI Apps, agentic mode, the managed experience), not your context or your data.

Yes, that's the designed path. The engine and MDL are the same across OSS, Cloud, and Enterprise Plus, so the models you build on open source carry over. Many teams prove value on OSS or the free Cloud tier before rolling out company-wide.

Judge the cadence, not the promise: weekly public releases, a public roadmap, 16K+ GitHub stars, and 1,700+ Discord members growing 5× year over year. The engine is the foundation of every commercial plan, so keeping it healthy is the business.
Next step / due diligence

Read the code. Star the repo.

If open core is the model you want more of in your data stack, a star is how you say so. Run the engine locally today, and talk to us when you want the platform on top.