self-sufficient. confidential. connected.

verinice – operation in-house

Operating verinice on your own systems is a common scenario for ensuring the protection goal of confidentiality. Another option is to operate it at a trusted hosting service, e.g. in a municipal data center, a state-owned enterprise or the outsourced corporate IT.

Starting in early 2026, SerNet offers verinice.onprem for in-house operation with maximum sovereignty.

All prices and configurations can be found in the verinice.onprem shop:

Visit the verinice.onprem shop

Kubernetes & Appliance

There are two configuration options available, both of which can be customised to suit individual customer requirements:

verinice.onprem Kubernetes Cluster:
With Kubernetes expertise, you can set up the foundation for verinice yourself. This includes setting up the database and installing the Kubernetes cluster. verinice.onprem can then be installed via Helm Chart.
verinice.onprem Virtual Appliance:
As an alternative for smaller environments, SerNet offers virtual appliances running the Talos operating system. These come with the Kubernetes environment and verinice.onprem pre-configured and can be easily put into operation – no Kubernetes knowledge is required.

Operation and Migration

We provide comprehensive technical support for the installation of verinice.onprem. This begins with the design of the system to determine the sizing of the target systems and the technical requirements for server and network configuration. We advise you on the necessary licenses and, upon request, supply all required software from a single source. Simply book our Installation Support directly in the shop.

For operating verinice with multiple clients, we support you with the security concept for client separation and the necessary verinice licenses for users and units (clients). If needed, we work in close coordination with your verinice.Partner, who provides technical consulting for the operation of the ISMS tool.

We significantly simplify the migration of your existing verinice.PRO servers by deploying the existing and new servers in parallel. This allows you to test and optimize the data transfer multiple times before going live.

For ongoing operations, we recommend our Support Budget for technical questions.

White Label

You want to set up your own verinice.cloud? You can license verinice from SerNet for this purpose. SerNet provides the complete account management. This includes the implemented payment systems, which also underlie the verinice.cloud operated by SerNet.

This alternative is suitable for large customers or partners who want or need to operate verinice with a maximum of autonomy. For this purpose, you conclude the corresponding license agreements directly with SerNet GmbH.

verinice.onprem in a Talos VM

To use verinice.onprem with a Talos VM, you will receive a pre-configured virtual machine that you can import into your virtualisation environment.

Recommended resources for the VM:

CPU: 6 vCores
RAM: 12 GB
Storage: 200 GB

Minimum resources for the VM:

CPU: 4 vCores
RAM: 8 GB
Storage: 50 GB

Operating system:

All – access to verinice.onprem is web-based.

Virtualisation:

The verinice.onprem Virtual Appliance requires a virtualisation environment with Intel, e.g. VMware, Proxmox or – coming soon – Hyper-V. The verinice.onprem virtual appliance can be run in other virtualisation environments. However, SerNet does not test with these.

No requirements for Java or a database – everything is supplied ready to use.

Requirements for operation in air-gapped environments:

verinice.onprem can be run in air-gapped environments. A more convenient solution for this scenario is currently under development and will be available in the coming months.

Currently, a local OCI registry, a DNS server, and a time server are required. The OCI registry is required to host the Helm chart and the component images (including verinice and the authentication service) locally. This can be set up, for example, following these instructions: https://docs.siderolabs.com/talos/v1.7/platform-specific-installations/air-gapped#preparing-the-internal-registry

New versions of images and Helm Charts must be manually updated.

verinice.onprem for Kubernetes Cluster

A fully functional Kubernetes environment is required to use verinice.onprem. You can install verinice.onprem in your existing environment using the Kubernetes package manager Helm.

Recommended resources for the Kubernetes environment:

Kubernetes cluster with at least three nodes
CPU: 6 vCores/node
RAM: 12 GB
Storage: 200 GB for the database

Minimum resources for the Kubernetes environment:

Kubernetes cluster with one node
CPU: 4 vCores/node
RAM: 8 GB
Storage: 50 GB for the database

Operating system:

All, as access to verinice.onprem is web-based.

Additional information:

Integration of your own/existing Ingress, PostgreSQL database, Keycloak or RabbitMQ may be possible under certain circumstances, but is not required – verinice.onprem provides all necessary components.

Requirements for operation in air-gapped environments:

verinice.onprem can be run in air-gapped environments. A more convenient solution for this scenario is currently under development and will be available in the coming months.

New versions of images and Helm Charts must be manually updated.