Everything in context.
Build a promotion package with its components, dependencies and target mappings. See what will change before it moves.
Bring your apps, environments and approvals together.
QSBRIDGE is the release workspace designed for the way your Qlik team already works.
Planned open source · Self-hosted first · No installable release yet
A clear picture of your next release.
Windows concept: map the target stream and review application replacement before promotion.
Keep building in the Qlik Hub. The first QSBRIDGE release will bring the preparation, review and delivery of your work into one shared workspace.
Build a promotion package with its components, dependencies and target mappings. See what will change before it moves.
Separate preparation, approval and promotion with scoped roles. Make responsibility part of the release, from the beginning.
Track deployment outcomes and backups. Understand the recovery options supported by each component and destination.
One QSBRIDGE installation for your organization. Connect multiple Qlik Windows sites and Cloud tenants, with clear boundaries between test, acceptance and production.
Multiple environments. One release workspace.
Start with a self-hosted core. A managed service is planned for teams that want us to handle the operations.
Keep the release workspace on infrastructure you manage, alongside your own data policies.
The same foundation, with isolated customer deployments operated by our team.
Component catalog, target mappings, approvals, dependency checks and deployment recovery.
Current focus · Foundation in developmentGit-backed history, snapshots and text comparisons, managed through the QSBRIDGE interface.
Next · Version controlIndependent branches and merging for qualified component types, with explicit conflict review.
Later · CollaborationWe’re building the foundation now. Here’s what the product is designed to do.
No. The planned workflow keeps developers in Qlik and QSBRIDGE. GitLab will provide source history behind the scenes in V2.
No. A self-hosted installation serves one customer organization. That organization can connect multiple Qlik Windows sites and Qlik Cloud tenants.
V1 specifies direct OIDC authentication and SAML through an optional Keycloak broker. Identity-provider configurations will be documented after testing.
No. Their publication models, APIs and hosting options differ. QSBRIDGE will show those differences and block unsupported operations before deployment.
Not yet. The repositories and deployment foundation are in place, but the application is still being developed. Public source, verified releases and installation guides will be linked here when ready.
Built for Qlik teams. Designed to keep you in control.