Eonvelope

Open-source email archiving, honestly reviewed. Built by one developer, for self-hosters who want more than an inbox.

TL;DR

• What it is: Open-source (AGPL-3.0) self-hosted email archiving server — automatically fetches, stores, and indexes your email from any major mail protocol [1][README].
• Who it’s for: Self-hosters and privacy-conscious individuals who want a permanent, searchable local copy of their email history, independent of any cloud provider [1][3].
• Cost savings: SaaS email archiving products exist primarily in the enterprise tier (pricing data not available for direct comparison). Self-hosted Eonvelope runs on a $5–10/mo VPS for free, since the software itself costs nothing [README].
• Key strength: Broad protocol support (IMAP, POP3, Exchange, JMAP), tight integrations with the self-hosted ecosystem (Paperless-ngx, Immich, Searxng, Grafana), and SSL baked in out of the box [1][README].
• Key weakness: Small, single-developer project (198 GitHub stars, 8 forks). Independent coverage is thin — virtually all in-depth writing about it comes from the developer’s own introduction post [1][3]. No managed cloud option.

---

What is Eonvelope

Eonvelope is a self-hosted email archiving server. You point it at a mail account, it fetches everything, stores it locally, and gives you a searchable web interface plus a full REST API to query the archive programmatically [1][README].

The tool exists because the developer wanted to make their homelab the central hub for all private data — and email was the missing piece. As they put it: “The only thing that was missing was a simple and open-source software to archive our emails. So I decided to take on the challenge of creating that tool.” [1]. That developer-origin story matters because it shapes the product: this is not a commercial project trying to replace enterprise archiving software. It is a homelab tool built to solve a specific personal problem and shared with the community.

The backend is Django (Python), deployed via Docker/Podman/Kubernetes, with a Bootstrap 5 web UI that supports PWA and mobile [README]. It has 2,238 commits on its development branch as of the scrape date, meaning it is actively developed despite the modest star count. The project’s main source of truth is the GitLab repository; the GitHub page is a read-only mirror [README].

The AGPL-3.0 license is an important detail. Unlike MIT, AGPL requires any modifications to the software — including when run as a network service — to be shared back under the same license. That is fine for personal self-hosting. It becomes relevant if you are building a commercial product on top of Eonvelope or reselling hosting to clients [README].

---

Why people choose it

The honest answer here is that third-party coverage of Eonvelope is thin. The deepest available source [1] is written by the developer. The only independent mention found is a brief entry in the Self-Host Weekly newsletter from November 2025 [3], which flagged it alongside three other email-archiving tools launching around the same time (Bichon, Mail-Archiver, Open Archiver) and noted — somewhat pointedly — “I’m wondering if I missed something aside from the typical privacy concerns that prompted the creation of these tools all at once” [3].

That context matters. Eonvelope is not a tool with a long track record of independent reviews. What follows is grounded in the developer’s own documentation and the README, which is the honest situation for a tool this early.

With that caveat, the reasons self-hosters reach for it are legible:

Email permanence. Cloud mail providers can and do lose email, throttle storage, change retention policies, or simply go away. If your Gmail account gets suspended, your archive goes with it. A locally hosted copy is yours indefinitely [1].

Protocol breadth. Most mail archiving tools support IMAP. Eonvelope also handles POP3, Microsoft Exchange (EWS), and JMAP — which covers nearly every mail server someone running a homelab might encounter, including self-hosted setups like Mailcow or Stalwart [1][README].

Self-hosted ecosystem fit. The integrations list is notable for a project this size: send attachments directly to Paperless-ngx, push images to Immich, sync correspondents to Nextcloud contacts, expose data to Searxng for full-text search, pipe statistics to Grafana via a Prometheus endpoint [1]. These are the exact tools that dominate homelab setups, and wiring them together in one click rather than writing custom scripts has obvious appeal.

Setup speed. The developer claims five-minute setup via the minimal docker-compose file. That’s a marketing claim, but the install surface is small: one container, environment variables for configuration, SSL handled automatically [1][README].

---

Features

Based on the README and the developer’s introduction [1][README]:

Email fetching and ingestion:

• Automatic, continuous background fetching on configurable schedules [1]
• IMAP (with and without SSL), POP3 (with and without SSL), MS Exchange, JMAP [1][README]
• Spam and junk filtering to keep the archive clean [1]
• Fully configurable: archive one mailbox or full two-way account traffic [1]
• Thread detection — links related emails into conversations [1]

Search and browsing:

• Web interface with filtering by sender, date, attachments, and keyword [1]
• Full-text search via the built-in UI and extended search via the API [1]
• Correspondent tracking and linking across conversations [1]

Import / Export:

• Import and export emails, attachments, and correspondents in various formats [1][README]
• Restore emails back to your mail account [README]

API:

• Full REST API covering everything in the web interface and more [1][README]
• Searxng integration is configured via the API — search archived mail from within your search engine [1]

Self-hosted ecosystem integrations:

• Paperless-ngx — send attachments directly from the UI [1]
• Immich — push images from emails to your photo server [1]
• Nextcloud — sync correspondents to your address book [1]
• Searxng — query the mail archive from a search engine [1]
• Grafana — Prometheus metrics endpoint for custom dashboards [1]

Deployment:

• Docker, Podman, Kubernetes — all supported [README]
• SSL certificate included out of the box [1][README]
• Slim mode for Raspberry Pi and low-spec hardware [1][README]
• Configuration via Docker environment variables or admin panel [1]

• 95% test coverage in the codebase, per the README [README]

Accessibility and localization:

• Translation via Weblate — multiple languages supported [README]
• Bootstrap 5 responsive UI, PWA support [README]

---

Pricing: SaaS vs self-hosted math

There is no Eonvelope SaaS. This is purely self-hosted software. The cost is:

Eonvelope (self-hosted):

• Software: $0 (AGPL-3.0) [README]
• VPS to run it: $5–10/mo on Hetzner, Contabo, or DigitalOcean
• Domain + reverse proxy if you want a clean URL: optional, you may already have one
• Time: claimed five minutes with the minimal docker-compose [1]

What you’re replacing: Enterprise email archiving SaaS (Mimecast, Barracuda, etc.) is priced per seat, typically targeting companies rather than individuals, and tends to start well above $10/user/month. Specific current pricing for competing services was not available in the sources reviewed. For personal use, most people are replacing nothing formal — they’re replacing the informal solution of “hope Gmail doesn’t lose it” with a real local archive.

If you’re already running a homelab with a VPS, the marginal cost of adding Eonvelope is near zero — it shares hardware with other containers. That’s the realistic framing for this tool’s audience.

---

Deployment reality check

The developer’s own post [1] presents setup as a five-minute operation via the minimal docker-compose file in the repository. The README confirms Docker, Podman, and Kubernetes are all supported paths, with example configs available in the docker/ directory [README].

What you actually need:

• A Linux server or VPS (Raspberry Pi is explicitly supported via slim mode) [1][README]
• Docker or Podman
• A mail account with IMAP/POP3/Exchange/JMAP access enabled
• Optionally: a domain and reverse proxy (Caddy or nginx) for HTTPS, though SSL is built in

What can go sideways:

• The developer is a single person. There is no commercial company behind this, no support tier, no SLA. If something breaks and the developer is unavailable, you are reading docs and GitLab issues [README].
• The GitHub repo is a read-only mirror; the actual development happens on GitLab [README]. This is not a problem, but users who reflexively open GitHub issues will need to redirect to gitlab.com/Dacid99/eonvelope.
• AGPL licensing means you cannot quietly build a commercial product on top of this without sharing your modifications [README]. For personal self-hosting, this never comes up.
• No one outside the developer has published a detailed setup walkthrough as of this writing. If you hit a problem, you are working from the ReadTheDocs documentation and the issue tracker.
• The project launched in late 2025 [3]. It has 2,238 commits and >95% test coverage, which suggests genuine engineering discipline [README] — but it hasn’t had years of community hardening.

Realistic setup time for someone comfortable with Docker Compose: 15–30 minutes including mail account configuration. For a complete beginner starting from a fresh VPS: budget a couple of hours to also handle the reverse proxy and DNS setup.

---

Pros and cons

Pros

• Broad mail protocol support. IMAP, POP3, Exchange, JMAP — covers everything [1][README]. Most competing open-source options only handle IMAP.
• Self-hosted ecosystem integrations. Paperless-ngx, Immich, Nextcloud, Searxng, Grafana — these integrations are specific, not generic webhooks [1]. Built for homelab setups, not corporate IT.
• SSL out of the box. Most self-hosted tools punt this to the user. Eonvelope handles it [1][README].
• Slim mode for low-spec hardware. Raspberry Pi is a first-class deployment target [1][README].
• Full REST API. Programmatic access to the entire archive — useful if you want to pipe mail data into other tools [1][README].
• >95% test coverage. Rare for a personal project. Signals the developer takes reliability seriously [README].
• Active development. 2,238 commits, CI pipeline, Weblate translations, Renovate for dependency updates [README]. Not abandoned.
• Agentic install option. The README includes a one-liner to have an AI agent install it for you — a small but genuinely interesting signal that the developer is thinking about modern deployment UX [README].

Cons

• Single developer, small community. 198 stars, 8 forks. If the developer steps away, the project loses most of its momentum [GitHub]. There is no commercial entity to absorb that risk.
• Almost no independent reviews. The only substantive coverage found is from the developer [1] and a single newsletter mention [3]. You cannot triangulate this tool’s real-world quality from third-party experience the way you can with n8n or Nextcloud.
• AGPL-3.0 license. More restrictive than MIT. Not a problem for personal use, but relevant for anyone building a commercial service on top of it [README].
• No managed cloud option. There is no “let me pay someone to host this” path. You own the deployment entirely [README]. That’s a feature for some, a blocker for others.
• Email archiving is a niche inside a niche. The Self-Host Weekly author noted that Eonvelope launched at the same time as three other similar tools [3] — Bichon, Mail-Archiver, Open Archiver — suggesting the space is fragmented. It’s unclear which of these will consolidate community support over time.
• Bootstrap 5 UI. Functional but not modern. The reference screenshot aesthetic is form-over-polish [README]. Not a dealbreaker, but if you care about the UI of internal tools you look at every day, factor this in.

---

Who should use this / who shouldn’t

Use Eonvelope if:

• You run a homelab and want a permanent, searchable copy of your email history that you own.
• You already use Paperless-ngx, Immich, or Nextcloud and want email integrated into that stack.
• You have a non-Gmail/standard mail provider (Exchange, JMAP server) that other archiving tools don’t support.
• You’re comfortable deploying and maintaining Docker containers and reading documentation when something breaks.
• A Raspberry Pi is your server — slim mode makes this a realistic option [1].

Skip it (wait and watch) if:

• You want a tool with an established community and multiple years of third-party validation. Eonvelope is promising but too new to have that track record yet [3].
• You’re building a product that would depend on this as infrastructure — the AGPL license and single-developer bus factor are real risks.

Skip it (use a different approach) if:

• Your actual need is email search rather than archiving — Thunderbird with local IMAP sync handles this without a server.
• You want a managed cloud option. That doesn’t exist here.
• You are running this for a team or business where you need someone to call if things break. There is no commercial support tier.

---

Alternatives worth considering

The Self-Host Weekly November 2025 issue [3] noted that Eonvelope launched alongside several other email archiving tools in the same week — which means the space has more options than it did a year ago:

• Bichon — launched the same week as Eonvelope [3]. No data available on its current status or feature set.
• Mail-Archiver — another contemporaneous launch [3]. No data available.
• Open Archiver — same launch window [3]. No data available.
• Paperless-ngx — not an email tool, but the overlap is real: if you’re archiving email attachments (invoices, documents), Eonvelope integrates with Paperless-ngx rather than competing with it [1].
• Mailpile — older self-hosted email client with built-in archiving. Much larger community but development has been slow in recent years.
• Thunderbird local archives — the zero-infrastructure option. Download everything via IMAP to local storage. No server, no API, no integrations, but works and costs nothing.
• Dovecot with full-text search — the ops-heavy option. Run your own mail server with local spool storage and Solr/Xapian for indexing. Significantly more complex than deploying Eonvelope.

Eonvelope’s strongest differentiator against all of these is the combination of multi-protocol support and homelab ecosystem integrations. If those integrations (Immich, Paperless-ngx, Searxng, Grafana) are part of your stack, it’s the only tool in this list that connects to all of them out of the box.

---

Bottom line

Eonvelope is a well-engineered personal project solving a genuine homelab gap: email archiving that works with non-IMAP protocols and connects to the tools self-hosters actually use. The test coverage is high, the development is active, and the five-minute setup claim appears plausible for someone comfortable with Docker. The caveats are real and worth weighing honestly: single-developer bus factor, AGPL licensing, minimal independent review coverage, and a market where three other tools launched the same week [3] means you’re making a bet on which project the community coalesces around. If you run a homelab today and want email archiving today, Eonvelope is a credible choice — just go in knowing you’re an early adopter, not following a well-trodden path.

---

Sources

1. Dacid99 (Eonvelope developer), noted.lol — “Eonvelope – Simple Email Archiving For Self-Hosters”. https://noted.lol/eonvelope/
2. Ayush Pande, XDA Developers — “4 self-hosted apps that changed how I manage my finances” (Feb 12, 2026). https://www.xda-developers.com/self-hosted-apps-that-changed-how-i-manage-my-finances/
3. Ethan Sholly, selfh.st — “Self-Host Weekly (21 November 2025)”. https://selfh.st/weekly/2025-11-21/
4. blacktemple.net — “BLACK TEMPLE — Self-Hosting & Homelab” (aggregator, references noted.lol). https://blacktemple.net/homelab

Primary sources:

• GitHub repository (read-only mirror): https://github.com/dacid99/eonvelope (198 stars, AGPL-3.0)
• GitLab repository (primary): https://gitlab.com/Dacid99/eonvelope
• Documentation: https://eonvelope.readthedocs.io