Deployment Options
Description: Explore ZigiOps deployment models: on-premise (Linux/Windows), ZigiWave-hosted cloud, and Docker. Choose the right option for your enterprise.
This page provides a concise overview of the available deployment models and helps you choose the best option for your organization.
ZigiOps offers flexible deployment options designed to meet the security, compliance, and operational needs of enterprise environments.
Deployment Models Overview
ZigiOps supports the following deployment models:
On-Premise Deployment (Linux or Windows)
ZigiWave-Hosted Cloud Deployment
Docker Deployment (Self-Hosted Container)
All deployment options use the same ZigiOps integration engine and provide a consistent security and functional baseline, including:
FIPS 140-2-compliant encryption for sensitive data
TLS-secured UI and listener endpoints (TLS 1.2 / TLS 1.3)
Support for enterprise-grade security and access controls
Full compatibility with all ZigiOps integration templates
On-Premise Deployment (Linux and Windows)
On-premise deployment gives organizations full control over infrastructure, network access, and operational processes.
Supported Operating Systems
Linux: Installed under
/opt/zigiwave/zigiops, managed via systemd serviceWindows: Installed under
C:\ZigiWave\ZigiOps, running as a Windows service
When to Choose On-Premise
Highly restricted or closed network environments
Strict data residency or regulatory requirements
Environments requiring full control over networking and security
Use cases requiring on-premise listener endpoints
Organizations that need to manage SSL certificates and encryption locally
Availability and Operations
Supports high-availability configurations using a primary/backup model
HA can be implemented on both Linux and Windows
Customers manage installation, upgrades, and infrastructure
ZigiWave Support can assist with installation and upgrades when needed
For detailed installation instructions, see Installation on Linux or Installation on Windows.
ZigiWave-Hosted Cloud Deployment
The ZigiWave-hosted cloud option delivers the fastest time-to-value with minimal operational overhead.
Key Characteristics
Each customer receives a dedicated, isolated ZigiOps instance
Single-tenant deployment (multi-tenancy is not currently supported)
Hosted on Amazon Web Services (AWS)
Access Model
Secure, dedicated regional URL
EU:
https://<customer>.zigiwave.euUS:
https://<customer>.zigiwave.us
Access credentials are provided by ZigiWave
No installation or infrastructure management required
Security and Availability
Each instance is secured with its own SSL certificate
High availability is enabled by default
Monitored with a target uptime of 99%
Dynamic IP addresses by default
A static IP can be assigned on request for customer-side whitelisting
Listener Support in Cloud
Listener (webhook) endpoints are not enabled by default but can be enabled upon customer request, depending on the use case and security requirements.
Updates and Maintenance
Fully managed by ZigiWave
Bug fixes, updates, and new features are delivered by ZigiWave
Updates are applied only after customer approval
Docker Deployment (Self-Hosted Container)
The Docker deployment option packages all ZigiOps services into a single container image. This model is suited for organizations that use containerized infrastructure and want a portable, self-managed ZigiOps installation.
Key Characteristics
All ZigiOps services (platform, frontend, persistence, troubleshooting) are bundled in a single image
Services start sequentially inside the container; startup takes approximately 1-2 minutes
Named Docker volumes ensure data persists across restarts and upgrades
The ZigiOps UI is accessible at
http://<host>:8080
When to Choose Docker
Organizations using containerized infrastructure
Teams that prefer portable, image-based deployments
Environments where a self-managed container model is preferred over a traditional OS service
Availability and Operations
Customers manage the Docker host, container lifecycle, and upgrades
High availability is configurable via container orchestration tools
ZigiWave provides the image archive and a license file
For detailed setup instructions, see the Docker Deployment Guide.
Security Overview (All Deployments)
Across all deployment options, ZigiOps applies consistent security controls:
Sensitive data visible in the UI or filesystem is encrypted using a FIPS 140-2-compliant AES/CBC algorithm with a 256-bit key
Encrypted data includes:
Authentication credentials (passwords, tokens, API keys)
Security-related HTTP headers (Authorization, Set-Cookie, and others)
Configuration and log files
All UI and listener endpoints are secured with TLS
Customers can use their own SSL certificates for on-premise and Docker deployments
Licensing Overview
ZigiOps uses the same licensing model for all deployment types.
On-Premise
ZigiWave provides a license file. Customers apply it to their local ZigiOps instance. High Availability requires additional license files for backup/failover instances.
Cloud
ZigiWave issues and applies licenses transparently as part of the cloud service.
Docker
ZigiWave provides a license file. Customers apply it to the ZigiOps instance running in Docker.
Choosing the Right Deployment Option
Infrastructure control
Full control
Managed by ZigiWave
Full control
Network restrictions
Suitable for highly restricted environments
Requires outbound connectivity
Suitable for restricted environments
Time to value
Requires installation
Immediate access
Requires Docker setup
High availability
Configurable
Enabled by default
Configurable via orchestration
Maintenance
Customer-managed
Fully managed by ZigiWave
Customer-managed
SSL certificates
Customer-managed
Included per instance
Customer-managed
Container support
Not applicable
Not applicable
Native Docker support
Related Documentation
Last updated
Was this helpful?