Skip to content

Deployment

Run Sigora in our infrastructure or yours.

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

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

SigoraOne Cloud

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.

Self-Hosted architecture

Choose one appliance or active-active HA

Self-Hosted sizing depends on message volume, infrastructure, and availability requirements. We provide deployment guidance during evaluation or quoting.

Standard Self-Hosted

One all-in-one Sigora appliance runs the Controller, Processing Node, and local SQL on the same VM or server. Standard does not require a load balancer, and external SQL is not supported for this non-HA deployment.

Self-Hosted HA

Two or more complete Sigora appliances operate active-active. Each appliance contains a Controller and Processing Node; the customer provides external SQL and load balancing.

End-to-end HA also requires appropriately resilient supporting infrastructure. Sigora does not control or guarantee the availability of customer-provided SQL, load balancing, networking, or compute.

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 SigoraOne Cloud when a BCM-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.

Pricing

Compare both operating models in one calculator

Cloud and Self-Hosted are available beginning at 10 users and use the same base user licensing. Self-Hosted is billed annually and adds a $2,500 annual platform license, including one complete appliance. Each additional appliance is $1,250 per year. Both include every feature; 501+ users receive custom pricing and architecture guidance.

Calculate 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.

Scroll to Top