Size your deployment in 60 seconds
Wren AI self-hosted is licensed by concurrent sessions, not named users, so you can give the whole company access and only pay for simultaneous load. Tell us your team size and we'll estimate the concurrent sessions you need.
Occasional use, Ad-hoc questions and the odd dashboard, a few times a week.
Daily self-serve, Self-serve analytics through the working day. Our default guide.
Always-on, Constant querying, embedded GenBI apps, Slack/Teams bots and AI agents on the API.
sessions
Sized for 40 users, with 20% headroom.
The self-hosted Wren AI platform, licensed by concurrent sessions and deployed in your own cloud or infrastructure.
Your sizing fits inside the included 10 sessions. Estimated $3,000/mo (base price, billed annually).
Estimate for guidance only. Final pricing confirmed by Wren AI sales.
What counts as a concurrent session?
A concurrent session is a single LLM-driven request to Wren AI, answering a question or producing an analytical output (chart, summary, report or GenBI App), counted from the start of the request to the return of its output. It's the same whether the request comes from the UI, the API, Teams, Slack or an MCP endpoint, so there are no separate per-call API charges. AI-assisted authoring tools like the Modeling AI Assistant and AI Advisor don't count. As a rough guide, one concurrent session supports around five active users.
Every entry point
One session pool
Counted from request to returned output, no per-call charges
Analytical outputs
- 01Licensed by simultaneous load, not named users, add as many users as you like.
- 02API, Slack, Teams, MCP and embedded apps all draw from the same session pool.
- 03Size for how many people query at peak, not your total headcount.