Open Archiver

Open-source email archive with provider-packaged VPS deployment and retention-oriented workflows.

5 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

OpenArchiver runtime security rebuild

Upstream 0.6.2 rebuilds the image with a corrected Node.js Brotli runtime.

Scope: OpenArchiver v0.6.2 image update for CVE-2026-111497; custom source installations must inspect their actual Node.js runtime.

The release changes the container runtime rather than application code; a custom image may have a different runtime.

Action: Recreate containers from a compatible v0.6.2-or-later image containing the runtime correction; updating application files alone does not replace the runtime.

Primary source · Reviewed 2026-11-19

What lands where

  1. Supplied by

    Vendor or project

    Docker / Compose

  2. 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
  • Hostinger: Customer VPS account · Customer-operated

    An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.

    Hostinger Open Archiver ↗ · 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 methodDocker / Compose
InfrastructureServers / containers
Docker Compose application, PostgreSQL, Valkey, Meilisearch and persistent local or S3-compatible archive storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.
Licensing modelOpen Source / Open Core
GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
LicenseGNU AGPL-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%) · 5 documented · 0 unresolved. Evidence coverage is not a feature score.

Single sign-on
Edition-dependentEvidence and scope for Single sign-on

The vendor documents OIDC and SAML2 user SSO with provider discovery/metadata, callbacks, JIT/account linking and group roles, requiring an Enterprise licence with SSO enabled. Local MFA and mailbox-connector OAuth are separate. Do not apply this entitlement to the unactivated open-source build.

Open Archiver Enterprise user SSO feature entitlement · Source ↗ · Reviewed 2026-11-21

Edition-dependent · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The upstream guide supplies Docker Compose for the application and dependencies, with environment configuration, persistent storage and optional S3. Pin compatible images, protect keys/secrets and plan database/Redis/search upgrades, backups and TLS; one Compose host does not establish HA.

Open Archiver upstream Compose deployment; Enterprise activation and hosting packages separate · Deployment artifact ↗ (Current upstream installation guide reviewed on this date) · Reviewed 2026-11-21

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The installation guide requires at least 4 GB RAM with bundled services, or 2 GB when PostgreSQL, Redis/Valkey and Meilisearch run externally. That application-host baseline excludes the external services, retained mail/attachments, indexes, ingestion peaks and HA replicas.

Open Archiver host RAM baseline with bundled versus external dependency distinction · Source ↗ · Reviewed 2026-11-21

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Open 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 v0.6.2 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence.

Open 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

Hostinger supplies the named VPS deployment; the customer operates the complete stateful stack. Upstream's installation baseline is 4 GB RAM, or 2 GB with external data services. Those minima do not size the agreed HA workload or a complete retention budget. Recreate containers from a compatible v0.6.2-or-later image containing the runtime correction; updating application files alone does not replace the runtime.

Community & maintenance

The reviewed upstream contributor history includes weishest, tilwegener, axeldunkel, 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 archive with provider-packaged VPS deployment and retention-oriented workflows.

Compare within Records management

  • Alfresco Content Services + Governance ServicesCustomer-operated content and records management with retention and record-declaration workflows.
    • AWS
    Customer-operated · Open Source / Open Core
  • FormKiQ Records Management Directory PublisherImplement retention, legal hold, defensible disposition, and compliant lifecycle policies for governed records.
    • AWS
    Customer-operated · Commercial Only
  • Hyland OnBase On-PremiseCustomer-hosted enterprise content and case platform for document-heavy business processes.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • iTernity Compliant Archive Software (iCAS)Licensed immutable-archive software provisioned in a customer STACKIT deployment.
    • STACKIT
    Customer-operated · Commercial Only
  • Laserfiche Self-HostedSelf-hosted document and records platform with forms and configurable business process automation.
    • AWS
    • Azure
    Customer-operated · Commercial Only
  • M-Files On-PremisesCustomer-operated document vault and information-governance platform with metadata-driven workflows.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • Mail-ArchiverOpen-source email archiving, search and export service with a community Railway deployment.
    • Railway
    Customer-operated · Open Source / Open Core
  • MailStore Service Provider Edition (SPE)Commercial multitenant email archive operated by service providers in their own cloud accounts.
    • AWS
    • Azure
    Customer-operated · Commercial Only

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

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Hostinger Open Archiver ↗ · Hostinger

      Provider guide · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

      Docker Compose application, PostgreSQL, Valkey, Meilisearch and persistent local or S3-compatible archive storage. Hostinger supplies the named VPS deployment; the customer operates the complete stateful stack. Upstream's installation baseline is 4 GB RAM, or 2 GB with external data services. Those minima do not size the agreed HA workload or a complete retention budget.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory