DevOps for Qlik Sense and Qlik Cloud
Short answer: DevOps for Qlik means treating an app like code: every change is stored in Git, each developer works on a copy of the app in a branch, changes are reviewed in a pull request, checked before release and promoted from development to test to production in a repeatable way, with a roll back to any earlier version. Qlik provides the environments — spaces in Qlik Cloud, streams and servers in Qlik Sense Enterprise — and the APIs and qlik-cli to automate them. It does not keep sheets and master items in Git. Gitoqlok fills that part: it commits whole apps to your own Git provider from inside Qlik, so the rest of the cycle has a history to work with.
The cycle, step by step
| Stage | What Qlik provides | What Gitoqlok adds |
|---|---|---|
| 1. Version control | Qlik Cloud: load script history; Qlik for VS Code to edit load scripts locally. Sheets and master items: no history | Every sheet, master item, variable, bookmark and script section committed to Git (Commit) |
| 2. Parallel development | Duplicate the app; in Qlik Cloud the load script is locked while one user edits it | Each copy of the app is its own branch |
| 3. Review | — | Pull request on GitHub, GitLab, Bitbucket or Azure DevOps with one file per sheet and measure; visual compare with Diff Viewer |
| 4. Checks before release | — | Pre-deployment Checklist, shared across the team |
| 5. Promote dev → test → prod | Qlik Cloud: publish to managed spaces. Enterprise: publish to streams, replace apps | Deploy from Git to any tenant or server; Environment Migration for tasks, connections and security rules (Enterprise) |
| 6. Roll back | Re-import an older QVF or restore a backup | Update the app to any commit, or import single objects |
| 7. Automation | qlik-cli, REST APIs, Qlik Automate | The repository is plain Git, so any CI tool can run on it |
1. Put every app in Git
Without a history there is nothing to review, promote or roll back. In Gitoqlok, open the app, create a repository and commit. Gitoqlok reads the app through the Engine API and writes one JSON file per sheet and master item and one .qvs file per script section (Repository File Structure). Data is committed only if you add a QVF with data to the commit.
The options and their trade-offs — QVF exports, Qlik Automate, qlik-cli, Gitoqlok, DevOps platforms — are compared in Version Control for Qlik Sense and Qlik Cloud.
2. One copy of the app per developer
Git's branches map onto Qlik's habit of duplicating apps. The owner keeps the master app on the main branch; each developer duplicates it and Gitoqlok offers Create Branch for the copy. Everyone commits to their own branch, and nothing they do touches the master app or each other.
Split the work by layer and by sheet: one developer on the load script, others on sheets. The full scenario with roles and rules is in Team Workflow.
3. Review changes in a pull request
When a feature is done, the developer opens a pull request from their branch into the main branch on the Git provider. Because every sheet and measure is its own file, the reviewer sees which chart, expression or script line changed. For a visual check, the Diff Viewer, Sheets Comparator and Load Script Diff compare two versions inside Qlik.
After the merge the owner opens the master app and clicks Update: the merged sheets appear in the app.
4. Check the app before it is released
A Pre-deployment Checklist lists what has to be verified before publishing — data model, performance, naming, documentation. Checklists can be shared with the whole Git organization, and the Publish App dialog opens the checklist before the app goes out.
5. Promote from development to production
Qlik Cloud. A common layout is a shared space for development, a managed space for test and a managed space for production, or a separate tenant for production. An app is published from a shared space to a managed space, and the same app can be published to several managed spaces. Republishing replaces the published copy. Two details catch teams out: scheduled reloads are not copied when an app is first published, and variables created in the published copy are removed on republish (managing apps in managed spaces).
Qlik Sense Enterprise on Windows. Development, test and production are usually separate servers or streams. To release a new version, the published app is duplicated, edited and published again with Replace existing app.
With Gitoqlok the repository is the source of each release. Deploy from Git builds an app from a chosen commit in the hub of any environment — another space, another tenant, another server — optionally with a data reload. Publish App in the Gitoqlok header publishes to a stream or managed space and can replace the existing published app. On Qlik Sense Enterprise, Environment Migration moves reload tasks with their triggers, data connections, streams and security rules between sites.
6. Roll back when a release goes wrong
Pick an earlier commit in Gitoqlok and click Update: the app returns to that state, deleted objects come back and objects added later are removed. To restore only one sheet or measure, import it from the older commit. See Update and Roll Back.
7. Automate with a CI pipeline
The repository is ordinary Git, so the usual CI tools work on it: GitHub Actions, GitLab CI, Azure Pipelines. A pipeline can run on every merge into the main branch and call qlik-cli — for example qlik app import to upload a QVF or qlik app build to apply script, measures and objects from files and reload the app. Qlik documents a full example of moving apps between tenants with GitHub Actions and a code-based deployment to a tenant.
Note that the files qlik app unbuild produces and the files Gitoqlok commits are two different formats; pick one as the source of truth for a pipeline. A pipeline that only needs the binary app can use the QVF that Gitoqlok can add to every commit (Repository Settings).
Put your first Qlik app under version control in about five minutes. Install Gitoqlok from the Chrome Web Store · free for up to 30 repositories
Gitoqlok or a DevOps platform?
DevOps platforms for Qlik — PlatformManager, SenseOps, Ebiexperts WIP — are separate systems with their own server, users, roles and release workflows, run by an administrator. Gitoqlok runs in each developer's browser and uses the Git provider the team already has; it sends app content only to your Qlik environment and your Git provider (Security and Privacy). Teams that already work with pull requests and CI usually find that enough; teams that need a central release console with approvals per environment look at the platforms.
Related reading
- Version Control for Qlik Sense and Qlik Cloud: Your Options
- Moving Qlik Sense Apps Between Environments Without the Pain
- Keep the Same App ID When You Migrate a Qlik Sense App Between Environments
- Publish Over Any App in Qlik SaaS: Real Backup and Rollback with Gitoqlok
- Which Qlik Sense App Is the Latest? Comparing Your Work App to the Published Version
Frequently asked questions
Does Qlik have built-in DevOps or CI/CD for analytics apps?
Not for whole apps. Qlik Cloud gives you spaces to separate development from production, publishing to managed spaces, a load script history and, since November 2026, Qlik for VS Code to edit load scripts outside the browser. Sheets and master items have no Git integration. A DevOps workflow needs Git for the app content — for example with Gitoqlok — plus Qlik publishing or qlik-cli for releases.
How do I move a Qlik Sense app from development to production?
In Qlik Cloud, publish the app from the development space to a managed production space, or republish to replace the published copy. On Qlik Sense Enterprise, publish to a production stream with Replace existing app, or move the app to another server. With Gitoqlok, commit the release in development and use Deploy from Git in the target hub; on Qlik Sense Enterprise, Environment Migration also moves reload tasks, data connections and security rules.
Can several developers work on one Qlik app at the same time?
Yes, each on their own copy. With Gitoqlok every copy of the app is a Git branch; developers commit to their branches and merge with pull requests on GitHub, GitLab, Bitbucket or Azure DevOps. The app owner then updates the main app from the merged branch and republishes it. See Team Workflow.
Can I use GitHub Actions or Azure Pipelines with Qlik?
Yes. Once apps are in a Git repository, a pipeline can run on every merge and call qlik-cli to import, build, reload or publish apps in Qlik Cloud. Qlik documents moving apps between tenants with GitHub Actions on qlik.dev.
Do I need a separate DevOps server for Qlik?
Not with Gitoqlok. It is a Chrome and Edge extension that uses your existing Git provider; nothing is installed on the Qlik server. DevOps platforms such as PlatformManager or SenseOps are separate systems you deploy and administer.
Is Gitoqlok free?
Gitoqlok is free to install and use for up to 30 repositories per organization. Gitoqlok Platinum removes the limit; a 30-day trial is free — request one.