An alternative to the Qlik Hub: how to choose the right one

You have seen this scene before: an alternative to the Qlik hub could keep the manager from opening a list of apps with no brand context, no guidance on where to click, and closing the tab. Five minutes later, they open a ticket to the BI team asking for the same information that was right there, one click away.

The Qlik Hub does exactly what it promises: centralize apps, organize spaces and give access to published content according to each user's permissions. The problem is that it was designed for people who live inside the tool, not for the sales manager who needs a number before the nine o'clock meeting. When the audience changes, the default interface can become a problem.

Some Brazilian companies already running on Qlik Cloud solved this without starting from scratch: they found portals built natively on top of that infrastructure, which preserve the existing governance and deliver an experience that business users actually use. This article shows when it's worth seeking that switch, what exists on the market, the real trade-offs of each option and the concrete criteria to decide.

What the Qlik Hub delivers and where it stalls for business users

The native features the Hub covers well

The Qlik Cloud Hub is, in essence, the front door to find, open and publish applications. It centralizes apps in Spaces and Collections, controls what each user sees based on permissions configured in the admin panel, lets analysts create and publish content, and offers search and navigation across apps in a grid or list. For the technical profile, who knows the organization structure and moves between apps naturally, the Hub is functional. The problem appears when the audience changes.

The experience that pushes managers and business areas away

When the user is not an analyst, the gaps become evident. The interface doesn't carry the company's identity and requires familiarity with the logic of Spaces to navigate. On top of that, there's no way for the user to build a personalized view of KPIs by bringing together panels from different apps. Governance is available only to the Tenant Admin, invisible and functional, but the consumption experience doesn't match that technical sophistication.

Why the lack of brand customization is a real problem

For companies that deliver reports to external clients, such as independent software distributors and consultancies, or that want the tool to feel like part of the company's product, the generic Hub hurts the perception of value. A portal with its own logo, colors and domain is not vanity, it is adoption. When users recognize the brand in the data environment, the tool feels like part of their workflow, not a parallel IT system, and they tend to access it more naturally and rely less on support for basic tasks.

When looking for an alternative to the Qlik Hub makes sense

Practical signs that the default hub no longer serves

Some triggers indicate that the bottleneck is in the consumption layer, not in the data or the dashboard itself. A high volume of tickets to the BI team for simple tasks is the most obvious sign. Business users who ignore Qlik Cloud and keep asking for spreadsheets by email confirm the diagnosis. The need to deliver reports to end clients with their own visual identity, and the expansion of Qlik to profiles that never opened the tool, complete the picture. When these signs appear together, the question is no longer technical: it is about experience.

Technical and business criteria to evaluate the switch

Before choosing any alternative to the Qlik hub, four criteria need to guide the decision. The governance already configured in Qlik needs to be preserved, not reconfigured from scratch. The single sign-on from the current identity provider needs to be reused without creating a second authentication layer. The total cost needs to include development and ongoing maintenance, not just the initial license. And the solution cannot create a dependency on permanent custom development to work.

The main categories of alternatives to the Qlik Hub and their real trade-offs

Mashups with Capability APIs: flexibility with high technical cost

Mashups are HTML/JavaScript pages that use Qlik's Capability APIs to render objects and apps outside the default Hub. The design freedom is total. The real cost is what companies underestimate. Dedicated front-end engineering, integration with authentication, compatibility testing at every Qlik Cloud update and a permanent technical team for maintenance form a set that rarely enters the initial budget.

Based on estimates for projects of this size, the initial development of a robust mashup can range from US$ 30k to US$ 200k; the recurring costs of the first two years frequently exceed US$ 250k. For those who don't have this internal structure, the maintenance cost tends to exceed the perceived value before completing two years.

Custom internal portals: full control with constant rework

Building a corporate portal from scratch using Qlik's APIs, such as the Engine API and the Apps API, offers complete control over navigation, visual identity and integration with other systems. The structural problem is that every Qlik Cloud update can break the integration, requiring continuous cycles of adaptation. In Brazilian public contracts, this type of project accumulated consulting and maintenance costs in the range of R$ 503k in the first year of operation, with relevant growth in the following years, according to publicly available tenders. The portal gets ready, but it never gets finished.

External BI platforms used as a consumption layer

Some companies adopt other data analytics platforms as a presentation layer while keeping Qlik as the data engine. This approach fragments governance: the access rules configured in Qlik need to be replicated in the external platform, creating two control layers to keep in sync. The risk of access inconsistency and the additional licensing cost make this option problematic for those who have already invested in Qlik Cloud governance and need to stay compliant with the LGPD.

Native white-label portals: the category that solves it without starting over

What sets apart a portal built natively on Qlik Cloud

A white-label portal built natively on Qlik Cloud does not copy data or recreate the access logic. It uses secure OAuth to operate with the authenticated user's permissions, inheriting the rules already configured in the tenant, respecting the scopes approved by the OAuth client and the tenant's settings. This means that a permission change made in Qlik applies immediately in the portal, with no rework. For companies with audit trail and per-user isolation requirements, this distinction separates a solution that reduces technical debt from one that merely moves it somewhere else.

NewHub as a practical reference for this category

NewHub is a white-label portal built natively on Qlik Cloud. According to the vendor, the client's logo, colors, fonts and own domain are configurable with no custom development. The platform includes, in every plan, a natural-language query feature so that anyone can interact with the data and get answers in text or chart form. The single sign-on via OAuth/OIDC integrates with the existing identity provider, without creating a new authentication layer.

The business user builds their own view by bringing together panels from different Qlik apps in a single place, without writing code. When they run into a problem or need a deeper analysis, they open a ticket to the data team directly from the context of the panel they are viewing.

Direct comparison: default Hub versus native white-label portal

The difference between the two experiences is not only aesthetic. In the default Hub, the user sees the generic Qlik Sense Hub interface: no company identity, no simple and direct navigation and no ability to build a personalized view of KPIs. In the native white-label portal, they access an environment with the company's visual identity, interact with the data in natural language, organize their favorite panels and open contextual tickets without leaving the screen. The real difference is in adoption and autonomy: the first creates dependency on the BI team; the second significantly reduces the volume of tickets by removing friction before it accumulates.

How to evaluate alternatives to the Qlik Hub: SSO, cost and governance

Authentication and single sign-on: what each alternative requires in practice

Mashups and custom portals may require their own authentication configuration separate from Qlik Cloud in specific scenarios, such as anonymous embedding, machine-to-machine integrations or applications with their own back-end. This additional layer increases the risk of inconsistency and widens the surface for security incidents. Native white-label portals take advantage of the OAuth/OIDC already configured in the tenant, eliminating that extra complexity. For companies with LGPD as a requirement and a need for an audit trail, this difference is critical: per-tenant isolation and access tracking need to work end to end, not just inside Qlik.

Real costs the initial budget usually ignores

The initial budget for a mashup or custom portal usually covers development and deployment. What's left out are the costs that grow over time: evolutionary maintenance when Qlik Cloud updates the APIs, a dedicated technical team to sustain the solution and compatibility cycles at every new version. As mentioned, Brazilian public contracts documented the first year of operation of custom solutions on Qlik in the range of R$ 503k, with expansion in the following years. In comparison, the per-user subscription model of native software-as-a-service portals, such as NewHub, transfers the responsibility for maintenance and compatibility to the vendor, turning variable and unpredictable cost into fixed and controllable cost.

Contractual and support risks when leaving the default Hub

Solutions that use APIs outside the model approved by Qlik, or that rely on unofficial integrations, may reduce the manufacturer's support scope for incidents tied to the custom layer, though the exact extent depends on the current license agreement, which is worth reviewing before any decision. The manufacturer supports what is inside the approved ecosystem. Portals built natively on Qlik Cloud by certified technology partners mitigate this risk because they operate inside that ecosystem. Cluster, the developer of NewHub, acts as a Qlik technology partner, positioning the solution within the manufacturer's support perimeter.

First steps to evaluate and migrate without risk

How to structure the evaluation before deciding

Start by mapping the user profiles that generate the most tickets to the BI team. Then, identify which Hub features are actually used versus ignored by most users. List the company's single sign-on and governance requirements and define whether the delivery is for internal users or for external clients. This exercise turns a technical decision into a strategic one: you choose the right category of solution for your context, not the most sophisticated nor the cheapest on paper.

Questions that reveal whether a vendor delivers what it promises

Before closing any contract with a vendor of a portal that is an alternative to the Qlik hub, ask these questions directly. Is the Qlik Cloud governance inherited via OAuth or does it need to be reconfigured in the portal? Is the natural-language query feature included in the plan or charged by usage? Does the single sign-on use the existing identity provider or require a new one? What is the maintenance model when Qlik Cloud updates a critical API? These questions separate solutions that reduce complexity from those that merely move it somewhere else.

If you already use Qlik Cloud and want to understand how an alternative to the Qlik hub fits into your current infrastructure, the best step is a direct conversation with someone who has already run this kind of deployment. Start with the diagnosis, not the demo: understanding where the adoption bottleneck is is what defines which path really makes sense for your scenario.