Mail-Archiver
Open-source email archiving, search and export service with a community Railway deployment.
4 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
Application platform deployment
Runs in
Documented customer environment
Mail-Archiver application, PostgreSQL and persistent archive storage.
- Railway: Customer platform workspace
- Railway
Servers / containers
Operated by
Your team
Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Deployment boundaries by provider
- Railway: Customer platform workspace · Customer-operated
Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Railway Template ↗ · 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 | Application platform deployment |
|---|---|
| Infrastructure | Servers / containers Mail-Archiver application, PostgreSQL and persistent archive storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure. |
| Licensing model | Open Source / Open Core GNU GPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. |
| License | GNU GPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. |
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.
5 of 12 fields researched (42%) · 4 documented · 1 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
The upstream OIDC guide configures a provider authority, client credentials/scopes and callback, with user approval/provisioning and optional password-login disablement. This is archive-user SSO, separately from Microsoft/Gmail OAuth used to import mail. Review role creation and auto-approval deliberately.
Mail-Archiver upstream application-user OIDC configuration · Source ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
Upstream documents Docker Compose for the application and PostgreSQL, persistent volumes, environment/secrets and optional reverse-proxy/TLS configuration. The example uses moving image tags: select a compatible release and database version, then test backup and upgrades.
Upstream Mail-Archiver Compose deployment reference; provider template packaging separate · Deployment artifact ↗ (Current upstream setup documentation reviewed on this date) · Reviewed 2026-11-21
Documented · Editor reviewed.
- Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing
The setup guide identifies application/PostgreSQL services and configurable background jobs, but does not establish quantitative production CPU/RAM/storage requirements. Size ingestion, attachment/index work, concurrent searches, original messages, retention and HA separately.
Mail-Archiver complete production hardware baseline remains unconfirmed · Source ↗ · Reviewed 2026-11-21
Sources checked — unresolved · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
GNU GPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Mail-Archiver; software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
Reviewed upstream 2611.2 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence.
Mail-Archiver upstream application; verify compatibility with the selected package · Source ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
Show all fields (7 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.
Scope & considerations
The Railway template follows a moving application image. Review current upstream retention, deletion-lock and audit-export settings, pin the chosen release, and verify backup/restore and authentication before production use.
Community & maintenance
The reviewed upstream contributor history includes s1t5, Zappo-II, tilwegener, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.
Category fit
- Records management
- Open-source email archiving, search and export service with a community Railway deployment.
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
- MailStore Service Provider Edition (SPE)Commercial multitenant email archive operated by service providers in their own cloud accounts.
- AWS
- Azure
- 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
- Railway Template ↗railway.com
- Mail-Archiver Docs ↗s1t5.github.io
- GPL-3.0 LICENSE ↗raw.githubusercontent.com
- GitHub Releases ↗github.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.
- Railway Template ↗ · Railway
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Mail-Archiver application, PostgreSQL and persistent archive storage. The Railway template follows a moving application image. Review current upstream retention, deletion-lock and audit-export settings, pin the chosen release, and verify backup/restore and authentication before production use.
- Railway Template ↗ · Railway
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Community, governance or adoption evidence ↗github.com
- Upstream project ↗github.com