Deployment

Run Sigora in our infrastructure or yours.

Choose Sigora-managed Cloud-Hosted deployment for operational simplicity, or fully Self-Hosted deployment when your organization needs to control the infrastructure and message-processing environment. The product capabilities stay the same.

Compare the options View Pricing

Start with one question

Should Sigora operate the platform infrastructure, or should your organization?

Compare deployment

Two operating models, one Sigora product

Both options support Microsoft 365 Commercial, GCC, and GCC High. The meaningful difference is who owns the hosting and operational responsibilities.

Sigora-managed

Cloud-Hosted

Best when you want the simplest path and the least infrastructure to operate.

Sigora operates

Hosting and platform infrastructure.
Platform updates, availability, and scaling.
Day-to-day infrastructure operations.

Your team manages

Microsoft 365 connection and mail-flow configuration.
Signature content, assignments, users, and organization settings.
Your policies, controls, and compliance program.

Customer-controlled

Self-Hosted

Best when signature processing needs to operate entirely inside infrastructure controlled by your organization.

Your team operates

Hosting, networking, certificates, and infrastructure security.
Availability, scaling, backups, and platform operations.
Microsoft 365 connection and Sigora administration.

Sigora provides

The full Sigora platform and licensed product capabilities.
Deployment requirements and product guidance.
A path for customer-controlled processing infrastructure.

Dedicated and resilient options

Match the infrastructure to your operating requirements

The high-level deployment model comes first. Dedicated hosting and availability design are then evaluated within that choice.

Dedicated Cloud-Hosted

A Sigora-managed environment reserved for one organization is available by custom quote when shared managed infrastructure is not the right fit.

Ask about dedicated hosting

Capacity and resilience

Multiple processing nodes can support capacity and resilience. Controller high availability and load-balancer behavior require a deployment-specific design and validation plan.

Read the node guidance

Government environments

Commercial, GCC, and GCC High work with either model

One Sigora deployment can support multiple connected Microsoft 365 tenants, including Commercial and GCC High together. Choose Self-Hosted when your internal requirements call for Sigora processing inside customer-controlled infrastructure. Choose Cloud-Hosted when a Sigora-operated environment fits your requirements.

Deployment choice does not make an organization compliant or authorized. Your organization remains responsible for its compliance scope, technical controls, assessment, and authorization decisions.

Review GCC High considerations

Technical requirements

Choose here. Implement in the Help Center.

The marketing decision should not require studying ports, certificates, service configuration, or installation commands. Those details remain available for the team responsible for a Self-Hosted deployment.

Installation and configurationHost preparation, network access, certificates, and verification. Nodes and processingRegistration, health, capacity, resilience, and controlled testing. Platform administrationOperations, security, maintenance, diagnostics, and reference material.

Pricing

The operating model determines the rate

Cloud-Hosted is $3 per user / month and Self-Hosted is $2 per user / month, billed annually. Commercial, GCC, and GCC High use the same base pricing. Dedicated Cloud-Hosted infrastructure is quoted separately.

Estimate Pricing

Not sure which model fits?

Tell us about your Microsoft 365 environment and who should own the infrastructure. We can help narrow the choice without turning the first conversation into a formal evaluation.

Ask a deployment question See How It Works