About QOps

QOps (Qlik Operations) automates how Qlik applications are developed and deployed. It is a PowerShell module with 72 commands, a browser-based Portal, and an MCP server for AI assistants. It connects your Qlik applications to Git and to the CI/CD runners you already use, such as GitLab Runners and GitHub Actions. Wondering how it differs from other tools? Read the side-by-side comparisons.

QOps uses the Qlik APIs to take an application apart into source files: the load script, sheets, master dimensions and measures, variables and the app's properties. It works with Qlik Sense (client-managed), Qlik Cloud and QlikView. The source files are plain text, so you keep them in any Git repository, review them as diffs and merge them like code.

From those files QOps builds the application back, into a new application or into the one that already exists on the server. The source lives apart from the data, so several people can work on one application, and the same sources can be published to a development, test and production environment in turn.

You can drive all of it three ways:

  • PowerShell commands such as QOps-Prepare, QOps-Build, QOps-Publish and QOps-Release, by hand or in a pipeline.
  • The QOps Portal, a local web app started with QOps-StartPortal. It runs the same commands from buttons and adds a file editor, a Git panel with a merge editor, diffs, lineage and help pages. Portal results match command-line results because the Portal runs the same commands.
  • An AI assistant. The QOps MCP server lets Claude Desktop, Claude Code, Cursor or another MCP client work with your repositories and Qlik applications in plain language. The Portal also has its own Chat panel that uses the same tools with your own Claude or Gemini API key. The server runs on your machine and never passes your Qlik credentials to the assistant.

Technical Support

For manual activation use the following form

For technical support, contact DataLabs in one of the following ways:

Prerequisites

Operating system and PowerShell

  • Windows 10 or Windows 11, with Windows PowerShell 5.1 or PowerShell 7.4 or later. The Windows installer sets QOps up for both.
  • macOS on Apple silicon or Linux, with PowerShell 7.4 or later.
  • The Portal ships inside the module as a self-contained program. It needs no separate .NET install.

Git

  • Git installed and on PATH.

Qlik

  • Qlik Sense (client-managed): the server URL and a user, with certificate, JWT or Azure AD authentication.
  • Qlik Cloud: your tenant URL and an API key or an OAuth client.
  • QlikView 12 or later: Windows, with QlikView installed on the machine where QOps runs. QOps opens the documents through it.

Licence

  • A QOps licence key. Set it with QOps-SetLicense or in the Portal under Settings, Global, License. The machine activates itself the first time a command runs.
  • A QOps licence covers all QOps features and the base AI assistant tools. An MCP-QOps licence adds the analytic tools, which return the data values in an application.