Compliance software that is
|
on your own infrastructure
Z-CMS runs entirely on infrastructure you control. This page explains how it keeps your data secure, how a single instance scales across your organisation, and what your IT team needs to install and update it.
Z-CMS at a glance
Z-CMS is installed on a server you own and serves your whole organisation from there. Three things define how it works.
Data security
Your compliance data stays on infrastructure you control. Zealience has no access to it.
- Self-hosted, on-premises or in your private cloud
- No SaaS analytics, AI training, or external processing
- Your existing security controls apply
Scalability
One instance serves every business unit, with access rights set per user and per tenant.
- A dedicated tenant per business unit
- Permissions per user, per tenant
- New business units without a new deployment
Easy installation and updates
Container-based on a standard Linux server, with dedicated IT support in your SLA.
- Deployed and updated with Docker
- Runs on Ubuntu, RHEL, or Debian
- Support for your IT team from day one
01 Data security
Your data never leaves your infrastructure
Z-CMS is self-hosted and needs no internet connectivity to operate, so you choose how and where to deploy it. In both models, Zealience has zero access to your data: no SaaS analytics, no AI training, no external processing.
Two deployment models
Isolated On-Premises
Run Z-CMS inside your own network. It needs no internet connectivity to operate, so you decide how far to isolate it, up to a fully disconnected environment.
Self-Hosted Private Cloud
Deploy within your own cloud or internal infrastructure to enable secure remote access while retaining complete control.
Your existing security controls remain fully enforceable
Firewalls, identity management, network segmentation, and monitoring — all your infrastructure policies apply. You define who accesses the system, enforce authentication, monitor traffic, and integrate with your existing security stack.
02 Scalability
One Z-CMS instance for your whole organisation
The Cyber Resilience Act covers a broad range of products, so compliance work often extends beyond one team. Z-CMS supports a multi-tenant architecture: you can create a tenant for each business unit inside a single deployment, with data segregated between them and access rights defined per tenant.
Multi-tenant inside your instance, not shared with anyone else
Tenants are your own business units, running on your own server, inside your own network. This is not a shared vendor platform: no data is co-located with another organisation, and Zealience has no access to any tenant.
A tenant for every business unit
Welcome to Z-CMS
Select a tenant to continue. You have access to 3 of them.
Building Systems
12 users · 9 products
Industrial Automation
18 users · 14 products
Energy & Grid
11 users · 7 products
A dedicated database per tenant
Each tenant stores its products and compliance data in its own database. Data in one business unit is never visible from another, even to users who have access to both.
Permissions set per user, per tenant
A user can hold full read and write access in one tenant and read-only access in another. Read-only access prevents accidental changes or overwrites in business units a user only needs to consult.
One rollout, every business unit
Create as many tenants as you need in a single instance. Adding a business unit does not mean a new deployment, a new server, or a new update cycle for your IT team.
Access rights per user, per tenant
Permissions are assigned to each user for each tenant, so people can collaborate within a business unit and across business units without being able to change data they only need to read. The full list of available permissions is shown in the Admin Panel.
| Example user | Building Systems | Industrial Automation | Energy & Grid |
|---|---|---|---|
| Group compliance lead | Read & write | Read & write | Read & write |
| Product engineer, Building Systems | Read & write | Read-only | No access |
| Internal auditor | Read-only | Read-only | Read-only |
Group compliance lead
Building Systems
Read & writeIndustrial Automation
Read & writeEnergy & Grid
Read & writeProduct engineer, Building Systems
Building Systems
Read & writeIndustrial Automation
Read-onlyEnergy & Grid
No accessInternal auditor
Building Systems
Read-onlyIndustrial Automation
Read-onlyEnergy & Grid
Read-onlyIllustrative example. Permissions are configured by your own administrators.
03 Easy installation and updates
Straightforward for your IT team to install, update, and support
Z-CMS ships as containers and runs on a standard Linux server. Your IT team installs and updates it with tools they already use, and our SLA gives them a direct line to us whenever they need help.
Container-based installation and updates
Z-CMS is built on container technology, making installation straightforward and updates seamless. Your IT team can get up and running quickly, with no complex infrastructure changes required.
Docker
Ubuntu Server Red Hat Enterprise Linux
DebianSystem requirements
Minimum Server Specifications
- OS Linux server (Recommended: Ubuntu Server 22.04.4 LTS or higher. RHEL or Debian also possible.)
- RAM 8 GB
- CPU 2 cores, x86_64 microarchitecture (Intel or AMD) with AVX instruction set support
- Storage 200 GB
- Snapshots Ability to take snapshots (e.g., VM)
Required Dependencies
- Docker Engine — Version 26.1.4 or higher
- Docker Compose Plugin
Planning for a larger rollout? These are minimum requirements. If you plan to manage a large number of products in Z-CMS (for example, more than 30), the server may need more resources. Contact us and we will help you size it for your expected use.
Dedicated IT support in your SLA
Our SLA includes timely, dedicated support for your IT team. Whenever you encounter an issue, from deployment to day-to-day operations, our team is committed to resolving it promptly so your compliance work is never blocked.
Support options available during business hours:
As we do not have direct access to your instance of Z-CMS deployed on your server, our support is provided in conjunction with your IT team. If you encounter a technical issue, contact us through any of the channels above and we will work with your team to resolve it.
Keep your compliance data out of attackers' reach
Manufacturers of connected products operate in one of the most sensitive data environments in modern industry. The information collected for compliance reflects your risk landscape — making where it is stored critically important.
What your compliance data reveals
Example of Data Stored in Typical Compliance Software
This is not just operational data — it is the blueprint of your products and competitive advantage.
If this information were exposed, the consequences could be severe:
Intellectual Property Theft
Competitors could replicate or undermine your products using exposed specifications and architectures.
Weaponised Vulnerabilities
Vulnerability data in the wrong hands accelerates targeted attacks against your products.
Regulatory Penalties
Disclosure of non-compliance details can trigger fines, reputational damage, and market exclusion.
Attack Roadmaps
Even technical metadata like dependencies or architecture diagrams can provide attackers with an entry point.
How Z-CMS compares to SaaS and AI-driven tools
The comparison below covers what each approach lets you do as well as what it asks you to give up.
| Criteria | Z-CMS | SaaS Platforms | AI / API-Driven Tools |
|---|---|---|---|
| Multi-Business-Unit Rollout | Multi-tenant, in one instance you run | Depends on vendor plan | Rarely supported |
| Access Control Granularity | Per user, per tenant | Depends on vendor plan | Typically limited |
| Deployment & Maintenance Effort | Container-based, run by your IT team | Vendor-managed, no effort required | Vendor-managed, no effort required |
| Data Location | Fully internal (on-prem or your cloud) | Stored in vendor cloud | Uploaded to external AI services |
| External Connectivity | Not required to operate; any connections are controlled by you | Required | Required |
| Vendor Access to Your Data | No vendor access whatsoever | Vendor-controlled infrastructure | Third-party AI providers may process data |
| IP Protection | Maximum — data never leaves your infrastructure | Moderate — depends on vendor | Low — data shared externally |
| Attack Surface | Minimal / controlled by you | Internet-facing | Internet-facing + API exposure |
| Risk of Data Leakage | Extremely low | Medium | Higher |
| Security Monitoring | Full visibility (traffic analysis, logging) | Limited visibility | Limited visibility |
| Compliance Control | Full ownership and auditability | Shared responsibility | Complex due to external processing |
Multi-Business-Unit Rollout
Z-CMS
Multi-tenant, in one instance you run
SaaS Platforms
Depends on vendor plan
AI / API-Driven Tools
Rarely supported
Access Control Granularity
Z-CMS
Per user, per tenant
SaaS Platforms
Depends on vendor plan
AI / API-Driven Tools
Typically limited
Deployment & Maintenance Effort
Z-CMS
Container-based, run by your IT team
SaaS Platforms
Vendor-managed, no effort required
AI / API-Driven Tools
Vendor-managed, no effort required
Data Location
Z-CMS
Fully internal (on-prem or your cloud)
SaaS Platforms
Stored in vendor cloud
AI / API-Driven Tools
Uploaded to external AI services
External Connectivity
Z-CMS
Not required to operate; any connections are controlled by you
SaaS Platforms
Required
AI / API-Driven Tools
Required
Vendor Access to Your Data
Z-CMS
No vendor access whatsoever
SaaS Platforms
Vendor-controlled infrastructure
AI / API-Driven Tools
Third-party AI providers may process data
IP Protection
Z-CMS
Maximum — data never leaves your infrastructure
SaaS Platforms
Moderate — depends on vendor
AI / API-Driven Tools
Low — data shared externally
Attack Surface
Z-CMS
Minimal / controlled by you
SaaS Platforms
Internet-facing
AI / API-Driven Tools
Internet-facing + API exposure
Risk of Data Leakage
Z-CMS
Extremely low
SaaS Platforms
Medium
AI / API-Driven Tools
Higher
Security Monitoring
Z-CMS
Full visibility (traffic analysis, logging)
SaaS Platforms
Limited visibility
AI / API-Driven Tools
Limited visibility
Compliance Control
Z-CMS
Full ownership and auditability
SaaS Platforms
Shared responsibility
AI / API-Driven Tools
Complex due to external processing
Control — not convenience — defines the right solution
Uploading product data to external platforms, especially AI-driven ones, can look like the faster route. In practice the capabilities remain largely unproven in enterprise environments, and teams are often left sorting through inaccurate recommendations. For manufacturers handling critical intellectual property and security data, giving up control of that information for uncertain benefits is not worth the risk.
Secure, scalable, and easy to deploy, on your own infrastructure
Whether deployed on-premises in an isolated network or in your own private cloud, Z-CMS keeps your data inside your environment, scales across your business units, and is straightforward for your IT team to install and update.
Explore Z-CMS