BI + AI in one self-hosted platform — natural-language Ask (NL→SQL) and BYO LLM (local Ollama / LM Studio or Anthropic, Gemini, OpenAI, Azure) included by default. Looker is Google-Cloud-only with no on-prem AI and no embedded analytics out of the box — Qrly runs on your infrastructure with embedded signed-JWT included.
No marketing fluff. Looker's developer experience is genuinely excellent and has set the bar for the whole category — here is where each tool is actually stronger when the dust settles and you look past the hero shots.
The features most teams actually evaluate when switching from Looker. Columns list the product as shipped — not as promised on a public roadmap.
From real migration conversations with engineering leaders and support directors. We are not arguing Looker is a bad product — it is a beautifully made one, and for pure internal data teams it is hard to beat on day-to-day feel. We are arguing it is missing specific things that a serious operations and customer-support stack needs, and those gaps are not easy to paper over with integrations.
Regulated industries, government agencies, defense contractors, healthcare providers and organisations under EU-only compliance all need a self-host option. Looker has deliberately chosen not to offer one — there is no on-prem build, no private-cloud edition, no data-processing agreement that moves the data inside your own perimeter. That is a product philosophy choice, not an oversight, and it is internally consistent with Looker's engineering focus.
It is also, for a growing slice of the market, a hard stop. Qrly runs on your Linux server, in your VPC, or on your Kubernetes cluster. The data never leaves your infrastructure unless you decide it should, and the same binary runs in air-gapped environments.
Looker is built for internal data teams tracking their own work, and that focus is one of the reasons it is so good at what it does. It has a "Customer Requests" inbox, which lets sales and success forward feature feedback to engineers — but it is not a ticketing system. There is no end-user portal where customers log in to raise and track their own questions, no branded support site, no guest access model for external reporters.
Teams that also support external customers end up running a second tool — Zendesk, Intercom, Freshdesk — paying twice, syncing twice and answering the same question in two places. Qrly bundles both sides into one workspace with the same question model, the same Alert engine and a single audit trail.
If your work has contractual response times — first-reply in four hours, resolution in 24, premium customers in two — Looker has no enforcement mechanism. No Alert clocks on the ticket. No breach alerts to a manager channel. No auto-escalation when a timer runs red. Teams that need this end up building it on top, usually in a second system.
Qrly ships Alert policies per customer, per priority and per tenant, with automatic escalation to backup assignees when the clock is about to breach. Breach events are first-class and reportable. It is not an add-on or a premium tier; it is in the core license.
Looker Business at roughly €14 per user per month feels fair at 20 users. At 200 users, the bill is around €33,600 per year — before any Enterprise upgrade, before any add-on, before annual price increases. Growth itself becomes a line item that finance starts to question, and the discussion around who really needs a seat begins to compete with the discussion about what work they are doing.
Qrly's license is flat, tied to company revenue tier rather than headcount. The 201st user costs nothing. Neither does the 2,001st. Your tracking tool stops punishing you for hiring and starts behaving like infrastructure.
List prices as of 2026-04. 50-user team, 3-year total cost of ownership.
Looker's API is clean, documented and complete, which makes migration mostly a mapping exercise rather than a data-wrangling one. Most teams are fully cut over inside a working week, including a parallel-run period where both systems stay online for cautious users.
Qrly reads Looker's GraphQL API directly — no third-party ETL, no paid connector.
Looker's UX is genuinely best-in-class — fast, keyboard-first, beautifully polished. We are not pretending otherwise. Qrly is not trying to out-polish Looker on pure aesthetics. Qrly is keyboard-driven, productive in under five minutes, and fast enough that users do not complain. The real question is whether that polish is enough to offset missing embedded analytics, missing Alert, no self-host and per-seat pricing. For a growing number of teams, it is not.
Yes. Looker's GraphQL API is stable and complete. Qrly's importer reads issues, projects, comments, labels, cycles, attachments and state history and maps them into Qrly projects, questions and releases. Looker issue identifiers are preserved as external references so existing deep links and integrations keep resolving.
Yes. Qrly runs on a single Linux box, inside a private cloud, or on Kubernetes. There is no user minimum and no infrastructure team required — a single-container deployment is the default. Looker is SaaS-only, by design: there is no on-prem build, no private-cloud edition, no air-gapped distribution. For regulated industries, government, defense and EU-only compliance, that single difference is the entire conversation and usually ends it before features are discussed.
Looker Cycles are lightweight caps and are central to the product's rhythm. Qrly models recurring iterations as releases when teams want them, and stays out of the way when they do not. Non-data teams — operations, support, legal, customer success — rarely run cycles and should not be forced into them. Roadmaps exist in both tools; in Qrly they are included in the base license, in Looker they live in the Business tier.
Looker's filter UI is excellent for current state — status is X, assignee is Y, in project Z. What it does not do is query history. QQL adds WAS, CHANGED, BEFORE and AFTER so you can ask questions like "questions that were In Review but are now Closed" or "issues that changed priority during the last cycle" without writing a custom report. For anyone who has ever had to justify what changed and when during an audit, historical operators are the difference between a two-minute query and a two-hour spreadsheet exercise.
€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, including embedded analytics, Alert, OIDC, SSO, on-prem AI and self-hosting. Looker Business at roughly €14 per user per month works out to approximately €25,200 over the same three-year period for 50 users, and continues to scale lookerly with every additional seat. At 200 users the gap widens to roughly seven times, and Looker still does not include embedded analytics or Alert.
Self-hostable. Flat pricing. Embedded Analytics and Alert included. Made in Belgium.