Qlik runs four meters at once.
Yurbi runs one annual subscription.

Qlik does not publish OEM or embedded pricing. As of March 2025, Qlik Cloud Analytics moved to capacity-based pricing across all tiers. Reported Qlik Sense deployments range from $30,000 to $300,000+ per year depending on capacity, user counts, and bundled add-ons. Published Enterprise bundle pricing for non-OEM customers runs roughly $11,000–$27,500/month.

The Qlik OEM Partner Program offers custom-negotiated agreements for ISVs embedding Qlik in their products, with 900+ active partners. Pricing is structured against each partner's business model — there is no list rate. ISVs cannot model budget fit without entering a sales conversation. Yurbi publishes flat annual pricing from $10,000/year.

In March 2025 Qlik moved to capacity-based pricing as the standard model across Qlik Cloud products. Instead of fixed user-license counts, customers now buy capacity measured in analytical impressions and consumption credits, with overage policies and auto-scaling options.

The result for ISVs embedding Qlik is that the bill has multiple meters running simultaneously: capacity used, consumption credits, user-license counts (Professional and Analyzer), AutoML and Qlik Answers add-ons, and any Talend bundle integration. Predicting cost across a growing customer base requires modeling each meter independently — and capacity-based pricing means a busy quarter from a major customer can move your bill the same way Power BI Embedded A SKU billing does. Yurbi charges a flat annual subscription that does not scale with usage or impressions.

The Qlik OEM Partner Program is a separate channel for ISVs and software vendors who embed Qlik analytics inside their own products. Qlik reports 900+ active OEM partners. The program offers Quick Start packages, dedicated OEM account teams, training and consulting resources, and customized agreements structured around each partner's business model.

There is no published OEM pricing — every agreement is individually negotiated. That can work well for a partner with the leverage and procurement bandwidth to negotiate, and it's frustrating for ISVs trying to evaluate fit before committing time. Yurbi does not require a partner program or sales process to evaluate embedding cost; the published flat-tier pricing applies directly to embedded use, with the OEM license included.

Qlik offers two products: Qlik Cloud Analytics (SaaS, the strategic primary path) and Qlik Sense Enterprise on Windows (the on-premise classic). Both can support embedded analytics. Qlik Cloud is multi-tenant SaaS, so customer data flows through Qlik's cloud infrastructure. Qlik Sense Enterprise on-premise is genuinely self-hosted on customer infrastructure.

Two practical considerations. First, Qlik's investment is on Cloud — the AI roadmap, agentic features, and capacity-based pricing model all originated there. Some Cloud-only features are not available on the on-premise path. Second, on-premise still ties into Qlik's licensing and any AutoML/Talend add-ons run through their own meters. ISVs whose customers require self-hosted, air-gapped, or data-residency-compliant deployment should evaluate the on-premise path specifically — and verify which features they would lose. Yurbi is self-hosted by design across all tiers — Windows, Linux, or Docker, with no required outbound connections.

Thoma Bravo, a private equity firm, took Qlik private in 2016. PE ownership doesn't automatically mean a worse product — Qlik remains a Magic Quadrant Leader and is technically strong. The point for ISV embedded analytics evaluation is the governance pattern.

Pricing models, packaging, and feature investment are evaluated against PE-style return targets. The recent capacity-based pricing pivot in March 2025 is one example of that pattern in action. ISVs who embed are committed across multi-year customer contracts — and the vendor's pricing and packaging can shift underneath those commitments. Yurbi is bootstrapped — no VC, no PE, no institutional pressure to pivot pricing or push toward an exit.

Qlik's associative engine is genuinely differentiated for exploratory analysis — clicking any data point and seeing all related context across the dataset. Qlik also has stronger AI features (Insight Advisor, AutoML, conversational analytics, Qlik Answers), broader visualization options, and deeper data integration via the Talend bundle.

Yurbi has no associative engine — interactivity is parameter-driven via global filters and drill-down. Yurbi has no AI or natural-language analytics features yet (on roadmap, deliberately built on the semantic layer for safe multi-tenant query generation). Embedding is iframe and API only with no JS SDK. SSO is session-token based via the DoLogin API, not SAML or OIDC. If associative analysis or built-in AI are core requirements for your product, Qlik is the better fit and we'll tell you that in a demo.

Download the Yurbi trial, connect to your database, configure tenant structure, and you can have a working embedded dashboard within days. Full production deployment — your branding, your SSO configuration, your customer data — is typically 2 to 6 weeks depending on data architecture.

The Qlik OEM path begins with a sales conversation, OEM agreement negotiation, capacity sizing, and an implementation engagement. Even with Qlik's Quick Start packages, you cannot evaluate cost or fit before engaging a sales team. The 30-day Qlik Cloud trial lets you test the product, but it does not give you OEM pricing or terms. Starting with a free download versus starting with a sales call is a measurable difference in time-to-evaluate.