MailStore Service Provider Edition (SPE)
Commercial multitenant email archive operated by service providers in their own cloud accounts.
3 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Package / binary installer
Runs in
Documented customer environment
MailStore Service Provider Edition services on supported Windows IaaS instances and high-throughput persistent storage.
- AWS: Customer cloud account
- Azure: Customer cloud account
- AWS
- Azure
Servers / containers
Operated by
Your team
The service provider operates SPE in its own cloud account and serves its customers; this is not an end-customer-owned mailbox archive.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
MailStore SPE FAQ ↗ · Source checked 2026-11-19
- Azure: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
MailStore SPE FAQ ↗ · Source checked 2026-11-19
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Package / binary installer |
|---|---|
| Infrastructure | Servers / containers MailStore Service Provider Edition services on supported Windows IaaS instances and high-throughput persistent storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure. |
| Licensing model | Commercial Only Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. |
| License | Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
4 of 12 fields researched (33%) · 4 documented · 0 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
SPE end-user access documents redirecting synchronised Microsoft 365 or Google Workspace users to the provider for authentication, including client and web access. Configure the tenant instance and directory integration. This does not establish the same mechanism for the service-provider management console.
MailStore SPE tenant archive-user federated login; infrastructure administrators separate · Source ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
SPE supplies a Windows installer through its partner portal that installs binaries for any server role; initial configuration assigns single-server or distributed roles. Obtain partner access and licence, then configure instances, TLS, firewall, persistent storage and updates.
MailStore SPE partner-delivered role installer; operational configuration separate · Deployment artifact ↗ (Current vendor SPE installation instructions) · Reviewed 2026-11-21
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The SPE requirements give each standalone Management Server and Client Access Server 2 GB RAM and 150 MB installation disk, with x64 CPU; archive Instance Hosts have separate workload-dependent requirements. These role baselines exclude stored mail/indexes, database working sets, replicas and HA capacity.
MailStore SPE management/access role minimums; not a whole archive host or HA footprint · Source ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
MailStore Service Provider Edition (SPE); software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
Show all fields (8 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
- Release snapshot / cadence
- Not researched Supply a public source.
Scope & considerations
The buyer/operator is the service provider. Its end customers do not thereby own the provider's cloud account. SPE licensing and tenant operations are separate from MailStore Server and from a vendor-hosted archive subscription; account for the documented storage and I/O demands.
Category fit
- Records management
- Commercial multitenant email archive operated by service providers in their own cloud accounts.
Compare within Records management
- Alfresco Content Services + Governance ServicesCustomer-operated content and records management with retention and record-declaration workflows.
- AWS
- FormKiQ Records Management Directory PublisherImplement retention, legal hold, defensible disposition, and compliant lifecycle policies for governed records.
- AWS
- Hyland OnBase On-PremiseCustomer-hosted enterprise content and case platform for document-heavy business processes.
- AWS
- Azure
- Google Cloud
- iTernity Compliant Archive Software (iCAS)Licensed immutable-archive software provisioned in a customer STACKIT deployment.
- STACKIT
- Laserfiche Self-HostedSelf-hosted document and records platform with forms and configurable business process automation.
- AWS
- Azure
- M-Files On-PremisesCustomer-operated document vault and information-governance platform with metadata-driven workflows.
- AWS
- Azure
- Google Cloud
- Mail-ArchiverOpen-source email archiving, search and export service with a community Railway deployment.
- Railway
- Open ArchiverOpen-source email archive with provider-packaged VPS deployment and retention-oriented workflows.
- Hostinger
Showing 8 of 12 other listings in Records management. These products address related workflows; read their category-fit notes before comparing scope. See all of Records management →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- MailStore SPE FAQ ↗help.mailstore.com
- MailStore SPE Product ↗www.mailstore.com
- SPE Changelog (v26.4) ↗www.mailstore.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- MailStore SPE FAQ ↗ · AWS, Azure
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
MailStore Service Provider Edition services on supported Windows IaaS instances and high-throughput persistent storage. The buyer/operator is the service provider. Its end customers do not thereby own the provider's cloud account. SPE licensing and tenant operations are separate from MailStore Server and from a vendor-hosted archive subscription; account for the documented storage and I/O demands.
- MailStore SPE FAQ ↗ · AWS, Azure
- Infrastructure evidenceChecked
- Licensing evidenceChecked