Qrly is the self-hostable BI + AI platform Qlik Sense never quite is — Qlik's AI lives in expensive Qlik Cloud Analytics + AutoML, with no real on-prem AI story and 3–9 month deployments. Qrly ships natural-language Ask (NL→SQL), AI anomaly detection and BYO LLM (local Ollama / LM Studio or cloud Claude, Gemini, OpenAI, Azure) plus embedded analytics with signed-JWT, productive in minutes at a fraction of the cost.
No marketing fluff. Qlik Sense is a real product with real ITIL depth — here is where each tool is genuinely stronger.
The features most teams actually evaluate when scoping out of Qlik Sense.
From real procurement reviews and post-renewal conversations with IT leaders.
Named-user pricing. Module pricing — ITSM, ITOM, ITBM, SecOps and HRSD each priced separately. Implementation fees. Mandatory partners. The numbers routinely push a mid-market deal past €300,000 per year before a single workflow has been customised. And because the modules are sold independently, adding HR ticketing or security incidents later means a new commercial negotiation, not a feature flag.
Qrly's cheapest tier (The Pulse) delivers the 80% that everyone actually uses for €1,875 per year per tenant — unlimited users & projects inside the tenant. No renewal cliff. No module per-user line items. The 51st agent costs zero. So does the 501st. The finance team can stop modelling headcount against subscription elasticity — there is nothing to model.
A mid-size Qlik Sense rollout is 3–9 months of consulting — discovery, design workshops, process mapping, CMDB seeding, portal theming, integration build-out, UAT, go-live support. The platform is capable of almost anything, and every "almost anything" is a billable day. Elapsed time is rarely the fault of the software; it is the weight of the methodology the software demands.
Qrly deployments are days, not quarters. Install, connect SSO, import your first ticket. The pattern most teams follow is: pilot this week, production next week, retire the old queue in the same month. There is no partner certification required, no sandbox instance clone cycle, no release window calendar to sync against.
What Qlik Sense calls flexibility, most teams experience as complexity. Every customisation needs a process — a scoped app, an update set, a change window, an instance clone, sometimes a partner. The Now Platform is genuinely powerful; it is also the reason a small UI change takes two caps, and why the internal joke at almost every large customer is that the Qlik Sense team is larger than the team whose questions it holds.
Qrly picks sensible defaults, ships a flat configuration surface, and treats "change the wording on a form" as something an admin does in two clicks during a stand-up. The only update set is the Git history of your own automation scripts, and those are plain files, version-controlled like everything else in your infrastructure.
Qlik Sense data is hard to exfiltrate — the Table API works but is slow and rate-limited, update sets are platform-specific, attachments live in a proprietary store, and the skill pool is expensive to hire. Your workflows are written in the platform's DSL, which does not translate to anything else. Renewal season is negotiated from a position of "we are already in."
Qrly runs on your own infrastructure, exports to standard JSON, stores attachments on plain object storage, and uses plain REST and webhooks for integrations. The data is yours, portable and legible. If Qrly stops being the right answer in five years, the migration out is a script, not a programme of work.
Estimates as of 2026-04. Qlik Sense pricing is not publicly listed — figures below are compiled from customer-reported ranges and partner procurement data. 50-user team, 3-year total cost of ownership.
Most mid-size migrations land in four to eight weeks — a timeline Qlik Sense partners quote for discovery alone.
Qrly pulls from Qlik Sense's own APIs — no third-party ETL, no paid connector, no partner engagement required unless you want one. The same pattern works whether you are on the current release or several families behind.
incident, sc_request, change_request, problem and sys_journal_field. Rate-limit aware so your existing instance stays responsive for agents during the extract.sys_user, sys_user_group and cmdb_ci map to Qrly users, groups and assets. Table-based priority and category values map to Qrly fields — usually one-to-one, sometimes with a short lookup table for edge cases. CI relationships are preserved with typed edges, not flattened into strings.INC0012345 keeps working. Comments, worklog entries and alert breach events are preserved so QQL queries like resolution_time > sla still make sense historically.For most organisations under a few thousand employees — yes. Qrly covers what the majority of Qlik Sense customers actually use day-to-day: incident and request tracking, Alerts, the self-service portal, scheduled subscription, approvals, automation and reports. Teams who genuinely run the full ITIL + ITOM + SecOps + HRSD + GRC stack on the Now Platform are a different conversation, and that is stated honestly.
Qrly implements Incident, Request, Problem and Change as first-class question types, each with their own workflows, approvals, Alerts and CAB-style views. It is not ITIL-accredited to the same depth as Qlik Sense's reference implementation, but it covers what ITIL v4 Foundation-trained teams use in practice.
Qrly pulls data straight through Qlik Sense's REST / Table API. Incidents, requests, changes, problems, users, groups and CMDB CIs are extracted, mapped and imported with history and Alert events preserved. Most mid-size migrations land in four to eight weeks end-to-end.
€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 customer-reported numbers for a 50-user ITSM Professional deal that land in the €300,000 to €500,000 range over three years once named-user fees, annual minimums and the mandatory implementation partner are counted.
No. Qrly ships a self-service portal for end users — submit requests, track questions, browse the knowledge base, see approvals, approve / reject changes. It is less customisable than a bespoke Qlik Sense Service Portal build, and deliberately so: fewer knobs, faster setup, nothing to maintain across upgrades.
Qrly's Assets module supports typed relationships, dependency maps and direct question linkage, which covers most practical CMDB use. It is not a full federated CMDB with Discovery probes and Service Mapping — if you genuinely need Qlik Sense Discovery + Service Mapping + ITOM Visibility, keep Qlik Sense for that slice and use Qrly for the rest.
Self-hostable. Flat pricing. On-prem AI. EU data residency by default. Made in Belgium.