Requirements
1. What you will be hosting
Cyver Core on-prem consists of two main components running within your environment:
- Cyver Core application - delivered as a Linux container image and pulled from Cyver's private container registry. The application serves the Cyver Core web portal over HTTPS.
- Microsoft SQL Server databases - provisioned and managed within your environment. Customer data is stored in these databases.
In a standard on-premise deployment, the application maintains outbound connections to selected Cyver-hosted services, including licensing, master data, the knowledge base, and the container registry.
No inbound access from Cyver to your network is required.
For environments that require complete network isolation, an air-gapped deployment option is also available.
2. Minimum hardware requirements
The minimum recommended resources for the Cyver Core application are:
| Resource | Minimum |
| CPU | 2 cores (x64 architecture) |
| RAM | 8 GB |
| Disk | 100 GB SSD |
Actual resource requirements depend on factors such as the number of users, data volume, concurrent activity, and reporting workload.
Because the infrastructure is managed within your environment, CPU, memory, and storage can be increased as usage grows.
3. Host platform
Cyver Core is delivered as a standard Linux container image.
The reference and supported deployment uses Docker Engine or Docker Desktop on a Windows or Linux server. On Windows hosts, Docker must be configured to run Linux containers.
The image can also be deployed on OCI-compatible platforms such as Kubernetes or OpenShift. In these environments:
- Cyver supports the application image and its documented configuration.
- Deployment manifests, networking, orchestration, and platform operations remain the customer's responsibility.
- The Cyver Core application should run as a single replica.
Physical servers, on-premise hypervisors such as Hyper-V or VMware, and cloud-hosted virtual machines can be used.
When Docker is running inside a virtual machine, ensure that the hypervisor exposes the required virtualization capabilities to the guest and that sufficient memory is available.
Administrator/root access is required during installation.
4. Database requirements
Cyver Core requires Microsoft SQL Server 2019 or later.
Supported editions include:
- Standard
- Enterprise
- Express
Cyver currently tests against SQL Server 2019 and 2022.
SQL Server Express can be used for smaller deployments, subject to Microsoft's Express edition limitations, including the 10 GB maximum database size and 1 GB database engine memory limit.
The SQL Server environment must meet the following requirements:
- TCP/IP enabled.
- Port 1433/TCP available.
- SQL Server authentication (Mixed Mode) enabled.
- A SQL login available for the Cyver Core application.
- SQL Server reachable from the host running the Cyver container.
The database may be hosted on the same server as the application or on a separate server.
5. Network requirements
The following network connectivity is required for a standard on-premise deployment:
| Direction | Port | Purpose |
| Inbound to application | 443/HTTPS | User access to the Cyver Core portal |
| Internal | 1433/TCP | Cyver Core application → customer SQL Server |
| Outbound to Cyver | 1433/TCP | Cyver master database and knowledge base |
| Outbound to Cyver | 443/HTTPS | Container registry and image downloads |
Cyver does not require inbound network access to the customer's environment.
6. DNS & TLS
A domain name must be configured for the Cyver Core portal, for example:
portal.yourcompany.com
An A record should point the domain to the server hosting the application.
A TLS certificate for the domain is also required. The certificate should be supplied as a PFX/PKCS#12 file and include its private key.
Certificates issued by the following can be used:
- Public certificate authorities
- Internal certificate authorities
- Let's Encrypt
Self-signed certificates can also be used, although users will receive browser security warnings unless the certificate is trusted by their devices.
7. Recommended tools
For database administration and troubleshooting, we recommend having a SQL management client available, such as:
- SQL Server Management Studio (SSMS)
- Azure Data Studio
These tools are optional and are not required for the Cyver Core application itself.
8. Cyver infrastructure connectivity
Cyver Core supports different deployment models depending on your security and infrastructure requirements.
Standard on-premise deployment
By default, the self-hosted application connects outbound to Cyver infrastructure for required services such as licensing and supporting platform services.
Telemetry is optional and can be configured according to your organization's requirements.
No inbound connection from Cyver to your environment is required.
Air-gapped deployment
For environments requiring full isolation, Cyver also supports an air-gapped deployment.
In this configuration, the Cyver Core instance does not depend on or communicate with Cyver-hosted infrastructure during normal operation.
Specific installation and update procedures are provided for air-gapped environments.
AI integrations
Support for connecting Cyver Core on-premise deployments to a customer-provided AI service/model is planned and will be documented separately when available.
Initial setup & data migration
Cyver will provide the required database copy for the initial deployment.
The customer then completes the deployment by following the Cyver Core On-Premise Installation Manual, which will be provided as part of the onboarding process.
For migrations from an existing Cyver-hosted environment, a maintenance window will be coordinated to prepare and transfer the database.
A few hours of downtime may be required during the database migration and final cutover. The exact maintenance window will be agreed in advance based on the deployment and database size.
After the migration is complete, the self-hosted Cyver Core application will use the database hosted within the customer's environment.
Updates & releases
On-premise releases are aligned with Cyver Core cloud releases.
Release availability and platform status can be followed through Product Updates.
Customers receive access to Cyver's private container registry. When a new supported version becomes available, the latest Cyver Core Docker image can be pulled from the registry and deployed within the customer's environment.
This allows the customer to retain control over when the new version is deployed to their infrastructure.
Support & SLA
Cyver provides support for self-hosted deployments according to the terms applicable to Custom Hosting.
The applicable support scope, responsibilities, and conditions are available in the Cyver Custom Hosting Terms:
https://core.cyver.io/custom-hosting-terms/
Because the infrastructure is customer-managed, responsibilities are shared between Cyver and the customer. Cyver supports the Cyver Core application and its documented configuration, while the customer remains responsible for the underlying infrastructure, operating system, database administration, networking, backups, and other customer-managed components unless otherwise agreed.
Backup & restore responsibilities
Because the SQL Server database is hosted within the customer's environment, the customer is responsible for implementing and maintaining an appropriate backup and disaster recovery strategy.
This should include regular SQL Server backups and appropriate retention, storage, and recovery procedures based on the organization's internal requirements.
Cyver's installation documentation will provide the relevant database information required to support backup and restoration of the application.