Choose a deployment model
Overview
Section titled “Overview”Zbix CRM 1.2.0 is distributed as a self-hosted Linux server package and a native Windows Server installer. Both provide shared browser access to a CRM installation. A server running in AWS remains a self-hosted deployment when the customer or implementation team operates its database, application and recovery processes.
Purpose
Section titled “Purpose”Choose an installation method before ordering infrastructure or preparing an implementation plan. The deployment model determines service management, HTTPS configuration, storage paths and recovery responsibilities.
Prerequisites
Section titled “Prerequisites”-
An approved release package and a named implementation owner.
-
A decision about who operates the host, database, certificates and recovery keys.
Procedure
Section titled “Procedure”-
Choose the Ubuntu amd64 package when Docker Engine, Compose v2 and systemd are the intended host platform. Use the Linux requirements and installation guides together.
-
Choose the native Windows Server package when the team requires a Windows service and Server Manager. The package includes its application runtime, PostgreSQL and HTTPS gateway; it does not require Docker or WSL.
-
For AWS, choose the operating system first. Follow the corresponding Linux or Windows installation method, then add cloud networking, storage and operational controls. Do not combine commands from the two packages.
-
Use the repository Docker Compose environment for local development and isolated testing. Keep its volumes and configuration separate from an installed customer system.
-
If a managed SaaS service is required, assess the separate SaaS readiness article. Establish the control plane, provisioning, subscription authority, provider recovery and operational responsibilities before describing a managed service as available.
Expected result
Section titled “Expected result”The implementation plan names one release, one operating model, its supported installation procedure and the owners of ongoing operations.
Fields and controls
Section titled “Fields and controls”| Field or control | Rule |
|---|---|
| Ubuntu amd64 | Offline application images with Docker Compose and systemd; host HTTPS prerequisites are prepared separately. |
| Native Windows x64 | Bundled runtime and database supervised by a Windows service; browser-based users. |
| AWS EC2 | An infrastructure location for either self-hosted package, with separate cloud operational responsibilities. |
| Local Compose | Development and isolated testing; not a customer production qualification. |
| Managed SaaS | Partial supporting capabilities; full managed-service readiness is not established. |
Important notes
Section titled “Important notes”-
The release baseline is tag v1.2.0-20261027. Its published database migration head is 0033_record_list_performance.
-
Source inspection verifies package behavior. Historical acceptance records describe particular test environments and do not establish every customer platform or workload.
-
An existing cloud-hosted installation does not prove unrestricted commercial readiness, high availability or a managed multi-tenant SaaS service.
Troubleshooting
Section titled “Troubleshooting”-
If package names, reported versions and deployment records disagree, stop the installation handover and obtain the matching release manifest. Preserve existing data while the release identity is resolved.
-
Escalate unsupported operating systems, ARM hosts, high-availability designs and pooled-tenant recovery requirements to the implementation owner before installation.
Related articles
Section titled “Related articles”Search the guides or talk to the ZBIX team.
Software products, application engineering and IT services from Zbix Technologies.
Visit our company website ↗