Separate Host / VM
Run Zimphony alongside the existing Zimbra web client without a disruptive cutover.
Deployment
Zimphony Webmail runs on-premise as a Docker-based layer around your existing Zimbra environment. Zimbra remains the mail backend, and your mailboxes and data stay in place.
Deployment topology
Separate Host / VM and Same Zimbra Server are both supported. The installation flow remains essentially the same; the proxy arrangement changes to avoid conflicts.
Run Zimphony alongside the existing Zimbra web client without a disruptive cutover.
Zimphony may use 443 if the existing Zimbra proxy is moved to another non-conflicting port. This is not required.
Host requirements
These are the current public readiness requirements. Detailed commands and network guidance belong in the technical installation guide.
| Requirement | Minimum | Recommended |
|---|---|---|
| CPU | 2 vCPU | 4 vCPU |
| RAM | 4 GB | 8 GB |
| Disk | 40 GB | SSD 80 GB+ |
| Operating System | 64-bit Linux capable of running the required Docker stack | 64-bit Linux capable of running the required Docker stack |
| Docker Engine | 24+ | 24+ |
| Docker Compose | 2.x+ | 2.x+ |
Deployment sequence
Use this sequence to orient the deployment; detailed commands remain in the Installation guide.
Open the Installation guideZimbra compatibility
Current tested targets are Zimbra 8.8 and Zimbra 10 OSE. Network Edition is not formally validated and is not presented as validated or unsupported here.
Zimbra connection
SOAP APICollaboration configuration
Both models keep Zimbra Mail and Zimbra Contacts as the shared email core.
Google services are not bundled, licensed, approved, or operated by Zimphony.
Self-managed deployment
Deploy Zimphony around the Zimbra environment you already run. Professional Implementation is an optional assisted path, not a deployment prerequisite.