Our take
Activeregular commits and releases- Activity
- 56
- Community
- 24
- Issues
- 62
- Pull requests
- 68
+67 stars in the last 30 days
OpenArchiver is a promising, actively maintained self-hosted email archive, but its compliance claims warrant validation because most contributions come from one person and legal holds are still listed as TBD.
Good fit if
- You need to archive and search email from the listed providers or import formats, and want to host the system yourself.
- Your team can run Docker Compose and operate PostgreSQL, Redis-compatible queueing, and Meilisearch services.
- You can comply with the AGPL-3.0 license and review whether it fits your deployment and distribution model.
Look elsewhere if
- You need a demonstrated legal-hold workflow now, since the README marks that capability as TBD.
- Your compliance process requires a mature product with development spread across a broader contributor base.
- You cannot meet the Node.js 22+ runtime requirement or manage a Compose-based deployment.
All health signals
| Last commit | 2026-09-17 (24 days ago) |
|---|---|
| Commits, last 90 days | 20 |
| Releases, last 12 months | 7 (latest v0.6.0, 2026-08-24) |
| Contributors | 6 (top contributor: 93% of commits) |
| Issues closed, last 90 days | 30 (typically closed in 10 days) |
| Pull requests merged, last 90 days | 20 (typically merged in 0 days) |
| Project age | 15 months |
Checked on 2026-10-12 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
2,482Forks
163Change since Nov 17, 2026: +2 stars·0 forks
Overview
OpenArchiver is a self-hosted system for collecting email from providers and archive files, then preserving and searching it in one place. It aims to give organizations a durable, searchable record of communications without relying on a vendor-hosted archive.
It is intended for teams with email retention or eDiscovery needs that can operate a Docker Compose deployment and manage its supporting services. The project is active, with recent commits and releases, but development is concentrated among a small contributor base.
Key Features
- Import email from IMAP, Google Workspace, Microsoft 365, PST, zipped EML, and Mbox sources.
- Synchronize supported email sources continuously after initial imports.
- Store messages as
.emlfiles with deduplication, compression, and encryption at rest. - Use local filesystem or S3-compatible storage backends.
- Search message and attachment contents, with filters and conversation-thread context.
- Apply retention policies and place legal holds, though legal holds are marked as TBD in the README.
- Record file hashes and provide integrity reports to help detect changes to archived files.
- Maintain an audit trail of system activity.
Use Cases
- An IT team can consolidate mail from Google Workspace or Microsoft 365 into an archive it hosts and administers itself.
- A legal or compliance team can search archived messages and attachments when responding to internal investigations or discovery requests.
- An organization migrating email providers can retain searchable copies of historical mail rather than relying on the previous provider.
- A team with PST, Mbox, or EML exports can ingest those files into a searchable archive alongside ongoing email sources.
What you need
Detected in the repository
- Node.js >=22.0.0 (from package.json)
- A Compose file to run it with its related services
- Automated checks on GitHub Actions
License in plain words
AGPL-3.0network copyleft
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the license notice
- Share your changes: yes, the full source, also when people only use it over a network (e.g. as a hosted service)
- Includes an explicit patent grant from the contributors:
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
git clone https://github.com/LogicLabs-OU/OpenArchiver.git
cd OpenArchiver
cp .env.example .env
docker compose up -d
Configure the required secrets and settings in .env before starting. See the README for full setup and email-source configuration details.
Considerations
The project is young, and although it has recent commits and releases, its six contributors are highly concentrated, with most code attributed to one person. Issue and pull request activity is ongoing, but that concentration may affect continuity and support capacity. The supplied requirements do not indicate a test suite.
A deployment involves more than the web app: the documented stack includes PostgreSQL, Redis or Valkey, Meilisearch, and storage, with Docker Compose as the deployment path. The README describes legal holds as TBD, so teams should verify retention and legal workflows against their requirements rather than assume full compliance coverage. AGPL-3.0 obligations should also be reviewed before adopting or modifying the software.
Found this useful?
Share it with someone who would like OpenArchiver.