# Deployment Options 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** Both 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 service * **Windows:** 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 ## 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://.zigiwave.eu` * **US:** `https://.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** ## 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 deployments ## Licensing Overview ZigiOps uses the same licensing model for both cloud and on-premise deployments. | Deployment | Licensing | | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **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. | ## Choosing the Right Deployment Option | Factor | On-Premise (Linux or Windows) | ZigiWave-Hosted Cloud | | -------------------------- | ------------------------------------------- | ------------------------------ | | **Infrastructure control** | Full control | Managed by ZigiWave | | **Network restrictions** | Suitable for highly restricted environments | Requires outbound connectivity | | **Time to value** | Requires installation | Immediate access | | **High availability** | Configurable | Enabled by default | | **Maintenance** | Customer-managed | Fully managed by ZigiWave | | **SSL certificates** | Customer-managed | Included per instance | ## Related Documentation * [Installation on Linux](/installation-and-deployment/installation-linux.md) * [Installation on Windows](/installation-and-deployment/installation-windows.md) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.zigiwave.com/integration-platform/deployment-options.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.