Choosing the Right Qlik Cloud Licensing Model: What You Need to Know
This article is for Qlik Cloud administrators and business stakeholders evaluating or planning a switch to capacity-based licensing.
TL;DR
Qlik Cloud offers two licensing models: user-based and capacity-based. Capacity-based is Qlik's strategic direction for new deployments since March 2025 and suits organizations with dynamic or growing user bases. User-based remains available for existing subscribers.
Intro
If you're managing a growing analytics platform, controlling costs while scaling access is one of the hardest balancing acts, and your licensing model plays a bigger role than most organizations realize. Qlik Cloud addresses this through two distinct pricing models: the well-established user-based model, suited for stable teams with clearly defined access needs, and the capacity-based model, designed to scale with data usage and support more dynamic analytics environments.
This insight unpacks the key differences between the two models, exploring how they impact cost, scalability, and administration. Whether you're planning a new deployment or considering a switch, this guide will help you weigh the pros and cons, identify the best fit for your use case, and navigate the transition with confidence.
Understanding Qlik Cloud Licensing Models
Qlik Cloud offers two licensing models: the legacy user-based model and the capacity-based model, which represents Qlik's strategic direction for new deployments.
The user-based model assigns named roles, such as Professional or Analyzer, to individual users and remains available to existing subscribers, who can still add users under their current contract. It is well suited for smaller, stable teams with predictable and clearly defined access requirements. However, since March 2025, capacity-based licensing is the only model available for new Qlik Cloud subscriptions.
The capacity-based model is built for modern, data-driven organizations. It aligns licensing with actual usage, offering predictable costs based on the volume of data analysed, stored, or moved, rather than on the number of named users. Depending on the subscription tier, this model supports unlimited user access, removing the administrative overhead of managing individual licenses and making it straightforward to extend access to internal teams, as well as external stakeholders such as partners, suppliers, and contractors.
Beyond flexibility and scalability, capacity-based licensing unlocks a broader set of platform capabilities, including automation, data lineage, overage protection, and data movement. These ensure continuous analytics operations even when usage temporarily exceeds subscribed capacity. The model also includes generous free tiers for AI-powered tools such as Qlik Answers, for natural language insights, and Qlik Predict, for predictive analytics.
By aligning with Qlik's product roadmap and offering a more adaptable, cost-efficient foundation, capacity-based licensing is the recommended starting point for organizations looking to scale analytics and maximize the long-term value of Qlik Cloud.
| User-Based | Capacity-Based | |
|---|---|---|
| Pricing basis | Per named user (Professional / Analyzer role) | Volume of data analysed, stored, or moved |
| Availability | Existing subscribers only — no longer available for new contracts | Default model for all new Qlik Cloud subscriptions since March 2025 |
| User access | Limited to purchased named user licenses | Unlimited users depending on subscription tier |
| Key features | Core analytics, standard Qlik Sense capabilities | Automation, data lineage, overage protection, data movement, Qlik Answers, Qlik Predict |
| Best for | Smaller, stable teams with clearly defined and predictable access needs | Growing organizations needing flexible, scalable access across internal and external users |
Optimization Strategies for Capacity Planning
As organizations scale their use of Qlik Cloud, efficient capacity planning becomes essential, not only to control costs, but also to ensure consistent performance and a seamless user experience.
Whether you're operating under a user-based or capacity-based licensing model, optimizing how data is stored, processed, and monitored can significantly impact your overall resource consumption.
In this section, we explore five practical strategies that help you make the most of your Qlik Cloud environment. From staging reusable data and leveraging efficient file formats to implementing incremental loads and monitoring usage, these best practices are designed to help you stay within your licensed limits while maximizing the value of your analytics platform.
1. Stage Data on your Qlik Cloud Tenant
Organize and store reusable datasets in shared or managed spaces within your Qlik Cloud environment. This approach minimizes the need to repeatedly extract and reload data from external sources, significantly reducing both reload frequency and memory consumption. By centralizing curated data, you also improve consistency across apps and streamline collaboration between teams.
2. Leverage Parquet instead of QVD
Consider using Parquet files as an alternative to QVDs, especially in cloud-native environments. Parquet offers superior compression and interoperability with other data platforms, making it ideal for scalable architectures. By reducing file sizes, it helps lower storage consumption, which is particularly beneficial under capacity-based licensing models where storage efficiency directly impacts cost and performance.
For a full breakdown of both formats and guidance on when to use each, refer to: Optimizing data storage and access in Qlik Cloud: QVD vs. Parquet | element61
3. Load Data incrementally
Implement incremental loading strategies to avoid full data reloads. By using techniques such as timestamp-based filtering, you can load only new or updated records. This approach significantly reduces reload time and memory usage, which is especially valuable in environments with concurrency limits or frequent data refreshes. It also improves overall system efficiency and scalability.
With extensive experience setting up robust incremental loading frameworks in Qlik Cloud, and ready-to-deploy template scripts to help you get started quickly, element61 can support you every step of the way. Contact element61 to discuss implementation support for your environment.
4. Set Up Monitoring Apps & Flows
Implement Qlik Monitoring Apps and Application Automation to gain visibility into your Qlik Cloud environment. These tools allow you to track key metrics such as app usage, reload performance, and resource consumption and are available in all Qlik Cloud Tiers. By proactively monitoring these indicators, you can identify inefficiencies, prevent unexpected overages, and ensure your environment remains within its licensed capacity. Automations can also trigger alerts or workflows when thresholds are exceeded, helping you stay ahead of potential issues.
5. Use SQL Pushdown wisely
Qlik Cloud supports SQL pushdown, allowing portions of your load script, such as WHERE clauses, to be executed directly on the source database. This can significantly boost performance by reducing the amount of data transferred and leveraging the processing power of the source system.
To fully benefit from SQL pushdown and avoid inefficiencies:
- Use a staging layer in the source system, such as views or stored procedures, to centralize and simplify query logic. This promotes consistency, optimizes performance, and reduces the complexity of Qlik load scripts.
- Keep Qlik scripts focused on loading, joining, and presenting data. Reserve heavy aggregations, filtering logic, and business rule transformations for the staging layer in the source system.
- Review the generated SQL queries to see how pushdown is being applied. Refine your staging views or script structure as needed to improve efficiency.
By designing your data model with pushdown in mind and using a staging layer effectively, you can enhance performance, minimize data movement, and stay within your licensed capacity limits.
At element61, we can help assess and optimize your Qlik data loading approach, including staging strategy and efficient use of SQL pushdown.
Transitioning from user-based to capacity-based licensing
Shifting from a user-based to a capacity-based licensing model requires thoughtful planning to ensure a smooth and cost-effective transition. Start by evaluating your current data usage patterns, including how much data is being analysed, moved, and automated across your Qlik Cloud environment. Monitoring apps can help estimate actual usage and highlight where a capacity-based model might offer greater flexibility or efficiency.
At element61, we have the IP and proven expertise to help you accurately estimate your required capacity and guide you through the migration process. We support customers in evaluating pricing tiers, planning capacity buffers, and aligning the new subscription model with your broader data strategy and growth roadmap. Whether you're just exploring options or ready to switch, our team will ensure your transition is seamless and designed to maximize the value of your Qlik investment. Contact us for more info.
Conclusion
Understanding the full scope of Qlik Cloud’s pricing models is essential for making informed, strategic decisions about your analytics environment. Whether your organization benefits more from the structure of the user-based model or the flexibility of the capacity-based model, knowing how each model works can lead to significant gains in efficiency, scalability, and cost control.
By applying the strategies outlined in this guide, such as staging reusable data, using Parquet files, and proactively monitoring usage, you can ensure your Qlik Cloud deployment remains efficient, scalable, and aligned with evolving business needs.
To dive deeper into Qlik’s pricing and licensing options, explore these helpful resources:
FAQ
Capacity-based licensing prices Qlik Cloud on the volume of data analysed, stored, or moved, rather than the number of named users. Depending on the subscription tier, it can support unlimited users - internal teams plus external partners, suppliers, and contractors - removing the overhead of managing individual licenses. Since March 2025, it is the only model available for new Qlik Cloud subscriptions.
User-based licensing assigns named roles, Professional or Analyzer, to individual users and is best for smaller, stable teams with predictable access needs. Capacity-based licensing instead charges for the volume of data analysed, stored, or moved, supports unlimited users depending on tier, and unlocks more platform features. User-based remains available to existing subscribers; capacity-based is the default for all new contracts.
Capacity-based licensing is Qlik's strategic direction for new deployments, and since March 2025, it is the only model available for new subscriptions. It aligns cost with actual usage, scales with dynamic or growing user bases, and follows Qlik's product roadmap, making it the recommended starting point for organizations looking to scale analytics and maximize long-term value.
Capacity-based licensing suits modern, data-driven organizations with dynamic or growing user bases that need flexible, scalable access across internal and external users. User-based licensing is better for smaller, stable teams with clearly defined, predictable access requirements. If you expect fluctuating usage or want to extend analytics to partners and contractors, capacity-based is typically the stronger fit.
Beyond flexibility and scalability, capacity-based licensing unlocks automation, data lineage, overage protection, and data movement features that keep analytics running even when usage temporarily exceeds subscribed capacity. It also includes generous free tiers for AI-powered tools: Qlik Answers for natural-language insights and Qlik Predict for predictive analytics. These extend the platform well beyond core Qlik Sense analytics.
We recommend five practical strategies: stage reusable data on your Qlik Cloud tenant, use Parquet instead of QVD for better compression, load data incrementally to avoid full reloads, set up monitoring apps and automation flows, and use SQL pushdown wisely. Together, these reduce reload frequency, storage, and memory, helping you stay within licensed capacity while maximizing performance.
Parquet files offer superior compression and interoperability with other data platforms compared to QVDs, making them ideal for scalable, cloud-native architectures. By reducing file sizes, Parquet lowers storage consumption, which matters under capacity-based licensing, where storage efficiency directly impacts both cost and performance. element61's guidance on QVD vs. Parquet explains when to use each format.
SQL pushdown lets parts of your Qlik load script, such as WHERE clauses, run directly on the source database, reducing the data transferred and leveraging the source system's processing power. Keeping heavy aggregations and filtering in a source staging layer minimizes data movement and helps you stay within licensed capacity. element61 can help assess and optimize your loading approach.
Set up Qlik Monitoring Apps and Application Automation, available in all Qlik Cloud tiers, to track app usage, reload performance, and resource consumption. Proactive monitoring surfaces inefficiencies before they cause overages, and automations can trigger alerts or workflows when thresholds are exceeded. Capacity-based licensing also includes overage protection to keep analytics running when usage temporarily spikes.
Start by evaluating current data usage patterns and how much data is analysed, moved, and automated across your Qlik Cloud environment. Monitoring apps help estimate actual usage and reveal where capacity-based licensing adds flexibility. element61 has the IP and proven expertise to estimate required capacity, evaluate pricing tiers, plan capacity buffers, and guide the migration. Contact element61 to plan your switch.
Yes, user-based licensing remains available to existing subscribers, who can still add users under their current contract. However, since March 2025, new Qlik Cloud subscriptions can only start on the capacity-based model. If you already run user-based and your usage is stable and predictable, you can continue; if your user base is growing, it may be worth evaluating a switch.
element61 supports the full journey: estimating required capacity with proven IP, building robust incremental-loading frameworks with ready-to-deploy template scripts, optimizing staging and SQL pushdown, and aligning your subscription with your data strategy and growth roadmap. Whether you're exploring options or ready to migrate, get in touch for tailored implementation support.
