You can install Open Zaak in several ways, depending on your intended purpose and expertise.

  1. Deploy on Kubernetes for public testing and production purposes

  2. Deploy on a VM, VPS or dedicated server with Docker Engine (or Podman) for public testing and production purposes

  3. Run with docker compose on your computer for private testing purposes

  4. Run from Python code on your computer for development purposes

Before you begin


These requirements are aimed towards public testing and production deployments, though they are _interesting_ to understand the workings of Open Zaak.

  • Check the minimum system requirements for the target machine(s).

  • Ensure you have the Prerequisites available

  • Make sure the target machine(s) have access to the Internet.

  • The target machine(s) should be reachable via at least a local DNS entry:

    • Open Zaak: open-zaak.<organization.local>

    • Open Notificaties: open-notificaties.<organization.local>

    The machine(s) do not need to be publically accessible and do not need a public DNS entry. In some cases, you might want this but it’s not recommended. The same machine can be used for both Open Zaak and Open Notificaties.

  • If you want to use NLX, make sure you have a publicaly available domain name, for example nlx.<>, where your NLX-inway is accessible to the outside world.