Qrly is the self-hostable BI + AI platform Redash never became — a stagnant OSS project since the Databricks acquisition, with no AI Ask, no anomaly detection and no enterprise plumbing. Qrly ships natural-language Ask (NL→SQL), AI anomaly detection and BYO LLM (local Ollama / LM Studio or cloud Claude, Gemini, OpenAI, Azure) alongside QQL across 12+ dialects, embedded analytics with signed-JWT, OIDC SSO and flat pricing for unlimited users.
No marketing fluff. Redash is a genuinely great product — here is where the two tools diverge.
The features most teams actually evaluate when Redash starts to creak.
From real migration conversations with ops and engineering leaders.
Redash is glorious at five people and one board. By fifteen people and twelve boards the overview is quietly gone — there is no cross-board query, no priority or severity field, no Alert, and no role-based access at list level. What looks like a list of boards in the sidebar is, in practice, a list of things nobody can see into at once.
Teams paper over this with a wiki page full of board links, a weekly stand-up that re-reads every board out loud, and a handful of "rollup" boards that instantly go stale. It is a lot of work to replicate what a real tracker gives you for free.
Qrly keeps the dashboard primitive you already like, but adds the scaffolding — priority, severity, QQL queries, role-based access, dashboards, saved filters — that lets a forty-person team still understand what is going on without a manual rollup ritual.
Custom fields, calendar, reports, query budgets, voting, forms, approvals, Gantt — each one is a Power-Up with its own quality, its own pricing, its own integration quirks, and its own vendor to chase when something breaks. Every new Power-Up is also a new place for your data to leak and a new contract for procurement to review.
A modest Redash site with five active Power-Ups easily doubles the Redash bill and triples the support burden when something misbehaves on release day. Upgrading is a coordination problem across half a dozen small vendors, not one.
Qrly ships the most-used of those capabilities natively. One vendor, one contract, one upgrade path, one support line, one security review to do.
There is no self-host option, no EU data residency below Enterprise, and no on-prem AI. For regulated teams — finance, health, public sector, defence suppliers, anyone with DORA, NIS2, HIPAA or a sovereign-cloud clause in their contracts — the conversation with the DPO ends before it really starts.
The practical answer is usually one of two things: "move off Redash" or "never onboard anything remotely sensitive to Redash". Both cap how much real work the tool is allowed to absorb, which eventually caps how useful it can be.
Qrly self-hosts on any Linux box or Kubernetes cluster, keeps your data where you put it, and runs AI locally via Ollama or LM Studio. Auditors, DPOs and security committees tend to like this arrangement a lot.
Customer portals, question queues, Alerts, escalation rules, CSAT surveys and email pipelines are simply not Power-Up territory. There are attempts, but none of them are production-grade for a team answering real paying customers at volume.
In practice most growing Redash shops end up running Zendesk or Tableau Service Management alongside Redash — two tools, two bills, two data islands, two sets of logins, and no single view of work. Engineers copy-paste card links into questions and question links into cards, forever.
Qrly bundles the embed portal, Alert engine and scheduled subscription pipelines into the same product that hosts your boards. Customer questions and engineering cards live in the same database, with one audit trail and one permission model.
List prices as of 2026-04. 50-user team on Redash Premium, 3-year total cost of ownership.
Most teams are up and running on Qrly within a working week.
Qrly reads Redash's native JSON export and its REST API directly. There is no third-party ETL step, no paid migration consultant and no scripting weekend required. The importer has been exercised against Free, Standard, Premium and Enterprise Workspaces.
Yes — that is exactly the gap Qrly fills. Redash is unbeatable for personal task lists and small-team projects, and we would never argue otherwise. Once the headcount passes about 20, or you need Alerts, a embedded analytics, role-based access, multi-tenant separation or a compliance story for your DPO, Qrly takes over with the dashboard boards you already like and the enterprise plumbing Redash was never designed to carry.
Yes. Qrly reads Redash's native JSON export, or pulls directly via the Redash REST API using an API key and token. Boards become projects, lists become statuses, cards become questions — with checklists, labels, custom fields, attachments, comments, due dates and members preserved. Redash card IDs can be kept as external references so old deep-links and Slack pastes continue to resolve after the cutover.
Most Power-Ups exist to patch Redash limitations — custom fields, calendar view, reports, query budgets, voting, forms, approvals. The equivalents in Qrly are native features, not bolt-ons, so teams typically consolidate four or five Power-Ups into one built-in product. Integrations with Slack, GitHub, Tableau, email and CI all ship with Qrly directly, and the remaining long-tail Power-Ups are usually replaced by a webhook or a line of QQL.
Past roughly 20 people and a dozen boards, Redash runs out of runway: no cross-board query, no priority or severity, no Alert, no role-based access at list level, no on-prem option, no customer-facing portal. Teams either bolt Power-Ups and a second product (Zendesk, Tableau Service Management) onto Redash to paper over the gap, or they move to a tool that covers it natively. The second option is usually cheaper and definitely less fragile.
Yes. Dashboard boards with drag-and-drop, quick-add cards, checklists, labels, cover images and attachments are all first-class in Qrly, and the board view is intentionally recognisable to Redash users. The difference is what happens when you need a priority field, an Alert timer, a query across forty boards, or a customer portal — those exist natively instead of requiring a Power-Up, a second product or a spreadsheet.
€1,875 per year per tenant on the cheapest tier (The Pulse), with unlimited users & projects inside the tenant — €5,625 over three years for a single tenant. Compared to roughly €18,000 for Redash Premium on Salesforce Cloud over the same three-year period — and that is before Power-Up subscriptions, any Enterprise upgrade for OIDC or data residency, and the inevitable bolt-on embedded analytics tooling. Qrly's number does not grow when you hire the 51st person.
Self-hostable. Flat pricing. Dashboard you already love, with the plumbing Redash never built. Made in Belgium.