Legal & Documents

Required Software

Technical requirements, supported platforms, configurations and lifecycle of the MazeVault Applications.

Verze / Version 1.0Effective date: 1 April 2026

This is a convenience translation. The binding version is the Czech document — please download the PDF.

This document forms an integral part of the contractual documentation between the Provider and the Customer within the meaning of the License Terms for the use of MV Applications (the “License Terms”). In the event of a conflict between this document and the License Terms, the provisions of this document prevail in matters of technical support and lifecycle; in all other matters the License Terms prevail. This English text is a convenience translation; the binding version is the Czech document available for download.

1. Introduction

MAZEVAULT s.r.o. (“MV”) is the author and owner of the MazeVault Applications — an enterprise platform for the centralized management of encryption keys, digital certificates, passwords and other secrets (KMS and PKI infrastructure). MV releases the Applications, develops them, issues updates and security fixes, and defines the product lifecycle rules.

The Applications are provided to customers (the “Customer”) through a Partner — an entrepreneur that obtained a license from MV and resells it to Customers, arranges deployment of the Application and is the primary contact point for technical support (the “Partner”). MV is responsible towards the Partner; towards the Customer, the Partner alone is responsible for the operation, maintenance and security of the Application, unless expressly agreed otherwise in the relevant agreement.

The Customer installs and operates the Applications on its own infrastructure or in the Partner’s cloud environment. MV in no case ensures or operates the Customer’s infrastructure. The Customer bears all costs of operation, security, infrastructure and its expansion in all chosen operating modes.

For the purposes of the Agreement, the Applications provided by the Provider to the Customer are defined in the following license variants:

  • MazeVault PoC – a time-limited evaluation or pilot license for verifying the solution;
  • MazeVault Small Business – a standard paid license for smaller customers;
  • MazeVault Enterprise – a full enterprise license.

This document (the “Policy”) defines:

  • MV’s commitments regarding the release of updates, security patches and lifecycle announcements;
  • the Customer’s responsibilities when operating the Applications;
  • security commitments specific to the security-critical nature of the Applications: cryptographic standards, security incident handling, vulnerability reporting, security advisories.

2. Scope of the document

2.1 Applications in scope

This Policy applies to the following components of the MazeVault Applications:

ComponentDescription
MazeVault Backend APISecrets management, certificate lifecycle, RBAC, audit logging
MazeVault Web interfaceBrowser-based administration interface
MazeVault AgentLightweight endpoint agent for distributing secrets and certificates
MazeVault GatewayIngress and routing layer
MazeVault OCSP ResponderCertificate validity verification service
MazeVault CLICommand-line interface for management and automation
MazeVault Helm chartsDeployment manifests for Kubernetes
MazeVault Terraform providerInfrastructure-as-Code integration
MazeVault License serverLicense validation and enforcement
DocumentationCustomer documentation

2.2 Out of scope

This Policy does not apply to:

  • the Customer’s infrastructure (hardware, OS, network infrastructure, Kubernetes cluster, database, backups, monitoring, physical security) — the Customer alone is responsible for these areas, unless expressly agreed otherwise;
  • the Partner’s infrastructure (where the Customer uses the Partner’s cloud operation) — the Partner is responsible for this;
  • the Customer’s application code or integration logic created by the Customer on top of the Applications’ API;
  • third-party services integrated with the Applications (Azure Entra ID, Azure Key Vault, AWS Secrets Manager, HashiCorp Vault, external CA) — these are governed by the terms of the respective third parties;
  • custom development and professional services — governed by a separate work contract;
  • training and certification — governed by a separate agreement.

2.3 Parties and support model

Support operates under the following model:

TierPartyCommitment
Development (upstream)MVRelease of updates, security patches, security advisories; definition of the version lifecycle
DistributionPartnerPrimary support to the Customer; deployment and configuration; escalation to MV
OperationalCustomerOperation of infrastructure; application of updates; environment security; backups

2.4 Supported deployment models

Deployment modelInfrastructure operatorApplication coverage
On-premise Docker ComposeCustomerApplication layer
On-premise Kubernetes / Azure AKSCustomerApplication layer
Partner cloudPartnerApplication layer + infrastructure per the agreement with the Partner
Hybrid (on-premise Gateway + cloud control plane)Customer / per configurationApplication layer per component

3. Definitions

Capitalized terms have the same meaning in this document as in the License Terms, unless defined otherwise below.

TermDefinition
MV or ProviderMAZEVAULT s.r.o., Company ID 24517194, author and owner of the Applications
PartnerAn entrepreneur authorized by MV to offer and sell Licenses to Customers; primary support to the Customer
CustomerAn entrepreneur that concluded an agreement with the Partner and uses the Applications under a License
UserA person on the Customer’s side authorized to use the Application
ApplicationThe MazeVault computer programs in all versions, modules, updates and add-ons
LicenseA non-exclusive, time-limited and non-transferable right to use the Applications granted to the Customer
SubscriptionThe period for which the Customer is granted access to the Application under the License
Updates and fixesBug fixes, security patches, modifications or improvements released by MV
Customer DataAll data that the Customer or its Users enter into the Application or process through it
Security AssetsDigital certificates, private keys, encryption keys, API keys, credentials, passwords, tokens, secrets, cryptographic materials and configuration data
Security IncidentAny event leading to or capable of leading to a breach of the confidentiality, integrity or availability of the Application or Security Assets
Supported configurationA configuration of the Application operated in accordance with MV documentation and recommended versions of the OS, database, middleware and other components
IncidentAn unplanned interruption or degradation of Application functionality, or a Security Incident
CVECommon Vulnerabilities and Exposures — a standardized identifier of publicly known vulnerabilities
CVSSCommon Vulnerability Scoring System — a framework for assessing vulnerability severity
Critical vulnerabilityA vulnerability with a CVSS score ≥ 9.0 or any vulnerability enabling unauthorized access to Security Assets regardless of CVSS score
Supported versionA version of the Application actively receiving maintenance and security patches under this document
EoSEnd of Sale — the version is no longer offered to new Customers
EoMEnd of Maintenance — no maintenance updates are released for the version
EoSupEnd of Support — no patches are released and no support requests are accepted for the version
EoLEnd of Life — the version receives no updates
Business hoursMonday–Friday, 08:00–16:00 CET, excluding Czech public holidays
Extended hoursMonday–Friday, 07:00–18:00 CET
On-call operation24/7, exclusively for critical P1 incidents
Maintenance windowA planned period of permissible operational interruption for an Application update or maintenance
Security advisoryA formal MV notice describing a confirmed vulnerability and the available remedy
SBOMSoftware Bill of Materials — an inventory of all software components and dependencies

4. Technical requirements for operation

4.1 Minimum technical requirements for operation

ComponentCPURAMHDD
API server2 cores4 GB20 GB SSD
PostgreSQL2 cores4 GB50 GB SSD
Redis1 core1 GB5 GB SSD
Web interface1 core512 MB1 GB SSD
OCSP responder1 core512 MB1 GB SSD
Agent1 core128 MB1 GB SSD
Documentation1 core512 MB1 GB SSD

4.3 Network requirements

External ports:

  • TCP 443 for HTTPS
  • TCP 80 for redirect to HTTPS

Internal ports that must not be publicly exposed to the Internet without proper firewall protection or another adequate means under the License Terms:

  • TCP 8080 for the API
  • TCP 8081 for OCSP
  • TCP 5432 for PostgreSQL
  • TCP 6379 for Redis

Outbound communication depending on the functions used:

  • HTTPS 443 to the MazeVault License Server – https://license.mazevault.com
  • HTTPS 443 to Azure Entra ID when using SSO
  • HTTPS 443 to Azure Key Vault or other external vaults when using integrations
  • HTTPS 443 to an external CA when using external certification authorities
  • HTTPS 443 to the MazeVault agent / proxy when used in hybrid infrastructure mode outside the LAN
  • UDP 123 to an NTP server for time synchronization
  • TCP 1433, 1521, 5432 and others to various database platforms for database integrations for the management and rotation of Secrets and Certificates
  • any custom ports chosen by the Customer when integrating components with the MazeVault system (JIRA, Teams, e-mail, SIEM, ELK, Slack and other existing or newly added integrations)

4.4 List of software required to operate the Applications

Software and services required for standard operation of the Applications:

  • PostgreSQL 15+;
  • Redis 7.x+;
  • Docker Engine 24+ or Podman;
  • Docker Compose 2.20+ or podman-compose;
  • Nginx 1.24+ or another reverse proxy or ingress equivalent;
  • a web browser in a supported version.

Software and services required for the Kubernetes operating variant:

  • Kubernetes 1.28+;
  • Helm 3.12+;
  • kubectl 1.28+;
  • Azure CLI 2.50+;
  • External Secrets Operator and Workload Identity when using the customer Azure model with Azure Key Vault.

Conditionally required software or services when the corresponding functions are used:

  • Azure Entra ID when using SSO;
  • Azure Key Vault, AWS Secrets Manager or HashiCorp Vault when using external secrets or key management;
  • external CA systems when issuing certificates outside the internal CA;
  • HSM when deploying HSM functions.

The Customer acknowledges that, in addition to the Provider’s License, licenses or authorizations to third-party software and services governed by the terms of the respective third parties may also be necessary for proper use of the Applications.

5. Supported licenses

Technical support is provided to Customers with an active and paid License. The scope of support depends on the license variant:

LicenseSupport levelBusiness hoursOn-call operation (P1)
MazeVault PoCCommunitySelf-service documentationNo
MazeVault Small BusinessStandardBusiness hoursNo
MazeVault EnterpriseExtendedExtended hoursNo
Enterprise + premium add-onPremium24/7Yes

PoC license: Provided exclusively for evaluation, for a maximum of 3 months, free of charge. No SLA commitment applies to it. Security patches are notified to the PoC Customer through Security advisories.

Expiry of the Subscription: Upon termination or expiry of the Subscription, technical support commitments cease. Security advisories continue to be issued within the lifecycle window of the given version.

6. Supported platforms

The Applications are supported on the following platforms when deployed in accordance with MV documentation. This section defines the MazeVault software support matrix — i.e. for which platforms MV releases patches and provides technical support, including the contractual minimum technical requirements for the Customer.

6.1 Operating systems (on-premise)

OSVersionStatus
Rocky Linux9.xSupported
RHEL9.xSupported
Rocky Linux8.xSupported (security updates only)
RHEL8.xSupported (security updates only)
Ubuntu22.04 LTSSupported
Ubuntu20.04 LTSSupported (security updates only)
Other Linux—Best effort; no warranty
Windows Server—Not supported
macOS—Not supported (development environment / CLI only)

6.2 Containers and orchestration

PlatformVersionStatus
Docker Engine24.x, 25.x, 26.xSupported
Docker Compose2.20+Supported
Podman4.xBest effort
Kubernetes1.28 – 1.32Supported
Azure AKSCurrent – N-2Supported
Helm3.12+Supported
Nginx or a functionally equivalent reverse proxy solution1.24+Supported
kubectl1.28+Supported
Azure CLI2.50+Supported
Terraform1.5+Supported

6.3 Databases

DatabaseVersionStatus
PostgreSQL15, 16, 17Supported
PostgreSQL14Supported (security updates only)
SQLite3.xPoC / dev only; not supported in production

6.4 Cloud integrations

ProviderServiceStatus
Microsoft AzureKey Vault, Entra IDIntegration supported
AWSSecrets ManagerIntegration supported
HashiCorpVaultIntegration supported
On-premiseHSM (PKCS#11)Supported for Enterprise

6.5 Web browsers

BrowserVersionStatus
Google Chrome100+Supported
Mozilla Firefox100+Supported
Microsoft Edge100+Supported
Safari16+Supported

Versions marked “security updates only” are technically supported by MazeVault software but may not meet the stated contractual minimum of Rocky Linux / RHEL 9+, PostgreSQL 15+ and Redis 7.x+. Customers running older versions do not meet the minimum technical requirements of the Agreement; the Provider may proceed under the terms of the relevant agreement.

7. Supported configurations

The supported configurations within the meaning of the License Terms are:

ConfigurationInfrastructureDetails
On-premise Docker ComposeCustomerSingle-node; Small Business; recommended for non-production environments or smaller installations
On-premise Kubernetes HACustomerMulti-replica; PostgreSQL 15+; Redis with persistence; Nginx/Traefik ingress
Azure AKSCustomer or PartnerKubernetes on Azure; cert-manager; Workload Identity
Hybrid GatewayCustomerOn-premise Gateway + the Customer’s cloud control plane; mTLS
Azure Workload IdentityCustomerManaged Identity for access to Azure Key Vault without static credentials
External CA integrationCustomerACME, SCEP, Step CA, internal CA
SSO via Entra ID (OIDC)CustomerFederation with Azure Active Directory / Entra ID
SSO via SAML 2.0CustomerAny SAML 2.0-compatible IdP
SIEM integrationCustomerElasticsearch, Splunk HEC, Microsoft Sentinel, IBM QRadar, Syslog RFC 5424
HSM key protectionCustomerPKCS#11 HSM for the root CA; Enterprise

8. Unsupported configurations

Problems arising from an Unsupported configuration are not eligible for warranties or SLA commitments. Operating the Application in an Unsupported configuration may be assessed as a material breach of the Agreement:

Unsupported configurationReason
Production operation on SQLiteUnsuitable for HA; risk of data loss
Direct exposure of the Application to the public Internet without a reverse proxy / firewallMaterial breach of the License Terms; security risk
A version past End of SupportNo security patches; non-compliance with the Customer’s security obligations
Custom patches or modification of Application binariesBreach of the License Terms; voids warranties
Sharing the PostgreSQL database instance with untrusted workloadsData isolation security requirement
Disabling TLS for internal service communicationBreach of the minimum security posture; untested
Disabling audit logging in productionBreach of the License Terms; non-compliance with regulatory requirements
Running the Agent as rootUnnecessary privilege escalation; explicitly discouraged
Deployment without network isolation in KubernetesPlatform security requirement
SHA-1 or MD5 for certificate signingCryptographically broken; the platform rejects it
Circumventing the Application’s license or security mechanismsMaterial breach of the License Terms
Penetration testing without prior written consentBreach of the License Terms

Related documents

Share this page