Deployment

Deploy modern Webmail around your existing Zimbra.

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

Choose where Zimphony belongs in your environment.

Separate Host / VM and Same Zimbra Server are both supported. The installation flow remains essentially the same; the proxy arrangement changes to avoid conflicts.

01

Separate Host / VM

Public hostnameHTTPS + reverse proxy
Zimphony WebmailSeparate Linux host / VM
User + Admin SOAP
Existing ZimbraMail backend and data remain in place

Run Zimphony alongside the existing Zimbra web client without a disruptive cutover.

02

Same Zimbra Server

Zimbra ProxyPort 443 unchanged
Zimphony ProxyAnother available HTTPS port
Preferred low-impact arrangementNo proxy-port conflict. 10443 is an example only, not a fixed requirement.
Alternative environment arrangement

Zimphony may use 443 if the existing Zimbra proxy is moved to another non-conflicting port. This is not required.

Host requirements

Prepare a host that can run the Docker stack.

These are the current public readiness requirements. Detailed commands and network guidance belong in the technical installation guide.

Minimum and recommended Docker host requirements
RequirementMinimumRecommended
CPU2 vCPU4 vCPU
RAM4 GB8 GB
Disk40 GBSSD 80 GB+
Operating System64-bit Linux capable of running the required Docker stack64-bit Linux capable of running the required Docker stack
Docker Engine24+24+
Docker Compose2.x+2.x+
Hostname + DNSHTTPS / TLSReverse proxyZimbra SOAP

Deployment sequence

From existing Zimbra to a working Webmail layer.

Use this sequence to orient the deployment; detailed commands remain in the Installation guide.

Open the Installation guide
  1. 01Choose deploymentSeparate Host / VM or Same Zimbra Server.
  2. 02Prepare environmentPrepare Linux, Docker, and HTTPS/proxy access.
  3. 03Prepare Zimbra accessPrepare User and Admin SOAP access.
  4. 04Download & InstallDownload the release package and run the installer.

Zimbra compatibility

Connect to the Zimbra environment you already operate.

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 8.8 · testedZimbra 10 OSE · testedNetwork Edition · not validated

Zimbra connection

SOAP API
User SOAPAdmin SOAP
Connects Zimphony to the Zimbra environment you already operate.

Collaboration configuration

Choose the collaboration model to configure.

Both models keep Zimbra Mail and Zimbra Contacts as the shared email core.

Native Zimbra

Native Zimbra

  • Zimbra Calendar
  • Zimbra Tasks
  • Zimbra Briefcase

Collaboration remains inside the Zimbra environment.

Google Connect

Google Connect

  • Customer-managed Google Calendar
  • Customer-managed Google Tasks
  • Customer-managed Google Drive

Google services and their sharing configuration remain customer-managed.

Google services are not bundled, licensed, approved, or operated by Zimphony.

Self-managed deployment

Start self-managed. Add implementation help when you want it.

Deploy Zimphony around the Zimbra environment you already run. Professional Implementation is an optional assisted path, not a deployment prerequisite.

01Existing Zimbra remains in place
02Zimphony adds the Webmail layer
03Choose assistance when useful