Deployment

Deployment options built around your infrastructure requirements

Run Sigora as a managed service or inside customer-controlled infrastructure, with deployment paths for shared SaaS, dedicated managed instances, all-in-one self-hosting, and distributed HA.

Schedule Deployment Review View Pricing

Two primary paths: Sigora-managed infrastructure or customer self-hosting. Each path supports deployment models for different operational and boundary requirements.

Deployment paths

Choose the deployment model that fits your environment

Sigora can be operated by Sigora or deployed inside customer-controlled infrastructure. Managed options reduce infrastructure ownership, while self-hosted options provide stronger customer control over hosting, networking, certificates, and data boundaries.

Model comparison

Compare Sigora deployment models

Managed SaaS

Shared Sigora infrastructure for fully managed operation.

Dedicated Managed

Dedicated Sigora infrastructure reserved for one organization.

Self-Hosted AIO

Single-server customer-controlled deployment. Not recommended over 50 users.

Self-Hosted HA

Distributed customer-controlled deployment for resiliency, capacity, and horizontal scaling.

Model	Managed SaaS	Dedicated Managed	Self-Hosted AIO	Self-Hosted HA
Deployment path	SaaS	SaaS	Self-Hosted	Self-Hosted
Infrastructure operated by	Sigora	Sigora	Customer	Customer
Infrastructure model	Shared managed infrastructure	Dedicated customer instance	Single customer-controlled server	Distributed customer-controlled deployment
Customer-managed servers	No	No	Yes	Yes
Customer-controlled infrastructure	No	Dedicated instance only	Yes	Yes
Dedicated customer instance	No	Yes	Yes	Yes
Shared with other customers	Yes	No	No	No
GCC / GCC High support	Supported	Supported	Supported	Supported
Data-boundary fit	Standard managed	Dedicated managed	Customer-controlled	Customer-controlled + resilient
HA / distributed processing	Sigora-managed	Sigora-managed	No	Yes
Horizontal scaling	Sigora-managed	Sigora-managed	No	Yes
Load balancer	Sigora-managed	Sigora-managed	Not required	Strongly recommended
Additional processing nodes	Not customer-facing	Not customer-facing	Not applicable	Available
Best fit	Fully managed simplicity	Dedicated managed requirements	Smaller self-hosted environments	Production / larger self-hosted deployments

GCC High

GCC and GCC High compatibility

All Sigora deployment models can support GCC and GCC High requirements. The right model depends on the customer's data-boundary, infrastructure-control, and operational requirements. Organizations that require signature processing inside customer-controlled infrastructure can use self-hosted deployment.

Self-hosted

Self-hosted infrastructure requirements

These requirements apply to Self-Hosted All-in-One and Self-Hosted HA deployments.

Shared requirements

OS	Ubuntu 24.04 LTS.
Public DNS/domain	Required.
Controller inbound ports	80 optional for Let's Encrypt renewal; 443 for web management and node communication.
Node inbound ports	25 for SMTP; 80 optional for Let's Encrypt renewal.
Outbound ports	25 for SMTP.
Certificates	Publicly trusted TLS certificates for `smtp.sigora.yourdomain.com` and `sigora.yourdomain.com`.

Sizing by model

Requirement	Self-Hosted All-in-One	Self-Hosted HA / Distributed
Number of VMs	1	n+1, where n = number of processing nodes.
CPU	4 cores.	2 cores per VM.
Memory	16 GB.	8 GB per VM.
Disk	64 GB.	64 GB controller, 16 GB per node.
Load balancer	No.	Yes.

Pricing

Pricing follows deployment model

Deployment scope affects pricing. Managed deployments include Sigora-operated infrastructure, while self-hosted deployments use customer infrastructure. Dedicated managed infrastructure and additional self-hosted HA nodes may affect final pricing.

View Pricing Schedule Technical Evaluation

Choose the deployment path that fits your mail flow

Review managed, dedicated, all-in-one, and self-hosted HA options for your Microsoft 365 environment.

Schedule Deployment Review View Pricing