Bichon

Self-hosted email archiving, honestly reviewed. No marketing fluff, just what you get when you run it yourself.

TL;DR

• What it is: Open-source (AGPL-3.0) email archiving server — synchronizes emails from IMAP accounts, indexes them for full-text search, and exposes a REST API. It is not an email client and cannot send mail [README].
• Who it’s for: Founders and small teams who need a permanent, searchable local archive of their email history — compliance, discovery, or just not losing things — without paying per-seat for a commercial archiving service.
• Cost savings: Commercial email archiving services (Mimecast, Barracuda, Proofpoint) typically run $3–10 per user per month, scaling to hundreds monthly for even small teams. Bichon’s software is free; you pay only for the VPS to run it [README].
• Key strength: Zero external dependencies — pure Rust binary with embedded search (Tantivy), built-in WebUI, and de-duplication baked in. It just runs [README].
• Key weakness: AGPL-3.0 license (stricter than MIT), no email sending, SSO is not yet in the community build (listed as a 2026 roadmap item), and the project is young — 1,495 GitHub stars as of this review with no significant independent review coverage yet [README].

---

What is Bichon

Bichon is a server-side application that connects to your existing IMAP accounts, pulls down emails, indexes them for full-text search, and stores them in a local archive. The name, according to the creator, comes from the puppy his daughter adopted [README]. The software analogy holds: it fetches, stores, and retrieves, without getting distracted by anything else.

The project is explicit about what it is not: it cannot send email, it is not a mail server, and it is not a replacement for your email client [README]. What it replaces is the scenario where you lose access to an old Gmail account, your company switches providers, or you realize your entire business communication history lives on someone else’s servers and is inaccessible if they close your account or you stop paying.

Built in Rust by the same developer behind rustmailer (an email API middleware), Bichon emerged because users kept asking whether rustmailer could also archive emails and support unified full-text search across accounts. The developer built a dedicated tool rather than bolt archiving onto a middleware [README].

As of this writing it sits at 1,495 GitHub stars with 45 forks, under active development with 245 commits and a public 2026 roadmap survey asking users to vote on features like S3 support and enterprise SSO [README].

---

Why People Choose It

No meaningful independent third-party reviews of Bichon exist at the time of writing — the project is new enough that the usual review sites and tech blogs haven’t covered it. This section draws from the project’s own documentation, the problem it explicitly addresses, and the general landscape of alternatives.

The core problem it solves. Email history is business-critical and almost universally underprotected. Most founders rely entirely on Gmail or hosted Exchange, with no local copy and no search beyond whatever the provider offers. IMAP sync to Thunderbird gives you a local copy but no cross-account search, no deduplication, and no REST API for automation. Commercial archiving services solve the search problem but introduce per-seat pricing, vendor lock-in, and the same “their servers, not yours” problem you were trying to escape [README].

The Rust angle matters. The absence of an external database dependency (no PostgreSQL, no Redis, no Elasticsearch to manage) is a real operational advantage. Most open-source email archivers require a stack of services. Bichon runs as a single binary. This cuts the surface area for failure and the maintenance overhead for anyone who isn’t running a dedicated ops team [README].

The de-duplication design. Bichon uses a Message-ID-centric storage model: every email is identified by its Message-ID header, and moving an email between folders updates the existing record rather than creating a duplicate. Bulk imports of EML/MBOX/PST files automatically merge duplicates. For anyone who has ever synced a mail archive and ended up with 40,000 duplicates, this is not a minor feature [README].

Why the AGPL-3.0 matters. If you’re embedding this into a product or building a managed service on top of it, AGPL-3.0 requires you to release your modifications. For internal use — which is the primary use case here — it’s effectively the same as MIT. Know the license before you build a business around it [README].

---

Features

Based on the README:

Core archiving engine:

• IMAP synchronization with configurable date range, email count, or specific mailbox targeting [README]
• Full-text indexing via Tantivy (the Rust search library, roughly equivalent to Lucene) [README]
• Search by sender, subject, body, date, size, attachments, and custom tags [README]
• Single-Instance Storage with idempotent “Delete-then-Write” for maximum write throughput [README]
• Transparent compression and deduplication at the account level [README]
• Automatic state updates when emails move between folders [README]

Authentication and accounts:

• Password and OAuth2 authentication with automatic token refresh [README]
• Multi-account support with unified search across all accounts [README]
• Proxy support and automatic IMAP server discovery [README]

Organization and management:

• Tag and facet system for organizing emails using Tantivy’s facet indexing [README]
• Thread view, bulk cleanup operations, EML and attachment export [README]
• Import of existing archives via the bichonctl CLI: EML, MBOX, and PST formats [README]

Interface and access:

• Built-in WebUI with 18 language localizations [README]
• OpenAPI documentation with access-token authentication [README]
• REST API for programmatic access [README]
• Dashboard with analytics: email volume trends, top senders [README]

Access control:

• Multi-user support with role-based access control (RBAC) [README]

Not yet available:

• SSO / enterprise SAML — on the 2026 roadmap survey, not in the current build [README]
• S3 storage backend — also on the roadmap survey [README]
• Email sending — explicitly out of scope by design [README]

---

Pricing: Self-Hosted vs Commercial Archiving

Bichon is free software. AGPL-3.0, no SaaS offering, no paid tiers [README]. Your costs are:

• VPS to run it: $5–15/month on Hetzner or Contabo for a small team
• Storage: email archives are text-heavy; a decade of business email for 5 users typically runs 20–50GB compressed
• Your setup time

Commercial email archiving comparison:

Exact current pricing for competing services wasn’t verified at time of writing, but the general market looks like this:

• Mimecast Email Archive: per-user monthly pricing, typically in the $3–6/user/month range; for a 10-person team that’s $360–720/year minimum
• Barracuda Message Archiver: hardware appliance or cloud, typically $500–1,500+/year for small deployments
• Proofpoint Archive: enterprise-tier, contact sales
• Google Vault (if you’re on Google Workspace Business): included at higher tiers, but not portable and locked to Google’s ecosystem

For a five-person team running 10 years of email history, Bichon on a $10/month VPS with 100GB attached storage costs roughly $240/year versus $600–1,800/year for commercial alternatives — and you own the data and the search index.

The math is straightforward. The question is whether you trust yourself to keep a VPS running.

---

Deployment Reality Check

What you need:

• A Linux VPS (2GB RAM is workable for a small team; 4GB is more comfortable once you have multiple accounts syncing and heavy search load)
• Docker and docker-compose (the primary documented deployment path) [README]
• Storage sized to your email volume (plan for 2x your current archive size for indexing overhead)
• A domain and reverse proxy (Caddy or nginx) for HTTPS if you’re exposing the WebUI externally

What you don’t need:

• PostgreSQL — Bichon uses an embedded store [README]
• Elasticsearch or Solr — Tantivy is bundled [README]
• Any runtime dependencies beyond Docker

This is a meaningful advantage over alternatives like Piler (which requires MySQL, Sphinx, and several other components) or self-hosted Zimbra (which is an entire mail server stack).

What can go sideways:

• The project is young — 245 commits, active development. APIs and configuration formats are more likely to change than in a mature project. Pin your Docker versions.
• AGPL-3.0 means any modifications you deploy to users must be open-sourced. Read this carefully if you’re building a product.
• SSO isn’t here yet. If your team uses an identity provider and requires SSO for access control, you’re waiting on the 2026 roadmap [README].
• The bichonctl CLI for imports is separate from the main server — expect some manual operations when migrating existing archives.
• There’s no managed cloud option. If the VPS goes down, your archive is unavailable until you bring it back up. This is not a concern for most use cases but worth stating explicitly.

Realistic setup time for a technical user: 30–60 minutes to a working instance with Docker. For a non-technical founder following a guide: 2–4 hours including storage provisioning and reverse proxy setup. PST import from Outlook can add another hour depending on archive size.

---

Pros and Cons

Pros

• No external dependencies. Single Rust binary, embedded search, embedded storage. The operational surface area is minimal compared to alternatives that require a full database and search stack [README].
• Genuine de-duplication. Message-ID-centric storage means you can re-sync, re-import, or bulk-load archives without ending up with duplicates. This is a solved problem here, not an afterthought [README].
• PST import. Many founders have years of email history in Outlook PST files going back to previous jobs or companies. The ability to import PST alongside EML and MBOX makes historical migration realistic [README].
• Unified cross-account search. If you run personal and business accounts, or have multiple domains, a single search covers everything [README].
• REST API with OpenAPI docs. Unlike Thunderbird or manual IMAP tools, you can build automations against the archive — alert when certain emails arrive, pull data for reporting, integrate with other tools [README].
• 18-language WebUI. Unusual for a project at this star count. Suggests serious internationalization intent [README].
• RBAC. Multiple users with different permission levels. Not common in small open-source archiving tools [README].

Cons

• AGPL-3.0, not MIT. Fine for internal use. A hard stop if you want to embed it in a product or SaaS without open-sourcing your modifications [README].
• No SSO yet. If your team requires SAML/OIDC login, you’re blocked until the 2026 roadmap item ships [README].
• Young project. 1,495 stars, 45 forks, no independent review coverage. You’re betting on a project that doesn’t have years of production deployments behind it. The de-duplication wiki is detailed and the code is Rust, which limits certain classes of bugs — but track record is thin.
• No sending. This sounds obvious once you understand the tool, but it trips up people looking for a self-hosted email solution. Bichon does exactly one thing: archive [README].
• No hosted option. If you want to evaluate before committing to a VPS setup, you can’t. It’s self-hosted or nothing.
• S3 storage not yet supported. For large-scale archives where storing tens of gigabytes on local VPS disk is impractical, you’re waiting on a roadmap item [README].
• Community size. The Discord server exists, but at this star count the community is small. Bug reports and edge-case documentation are thinner than you’d find for a more established project.

---

Who Should Use This / Who Shouldn’t

Use Bichon if:

• You’re a founder or small team currently paying $30–150/month for commercial email archiving and want that bill to go away.
• You have PST/MBOX archives from old accounts or companies and need to make them searchable without uploading them to a third-party cloud.
• You’re comfortable with Docker deployment or willing to pay someone to set it up once.
• Your compliance requirement is “have the emails, be able to search them” — not “prove chain of custody with certified audit logs.”
• You want a REST API so you can automate against your email archive (alerting, reporting, integration).

Skip it if:

• Your team uses SSO and you can’t manage separate credentials for an archiving tool.
• You need certified compliance archiving (SEC, HIPAA, SOX) with audit trails and legal hold features — commercial tools exist specifically for this and Bichon isn’t positioned there.
• You’re not technical and don’t have someone technical available to do the initial setup and periodic maintenance.
• You want to embed it in a commercial product — read the AGPL-3.0 carefully first.
• You need S3 or object storage for cost-effective large-scale archiving — wait for the roadmap.

---

Alternatives Worth Considering

• Piler — the most established open-source email archiver. More mature, more community resources, requires MySQL + Sphinx (more setup complexity). GPL-3.0. Worth comparing if operational complexity is acceptable.
• MailArchiva Community Edition — another long-standing open-source option. Java-based, heavier resource requirements.
• Thunderbird + IMAP local folder sync — the zero-infrastructure approach. No search across accounts, no API, no deduplication. Fine for a single person, breaks down at team scale.
• Dovecot + FTS plugin — if you’re already running your own mail server, adding full-text search to Dovecot gives you searchable IMAP without a separate archiving layer. More infrastructure to manage.
• Mimecast / Barracuda / Proofpoint — the commercial options. Expensive, vendor-dependent, but carry certifications and support contracts that matter for regulated industries.
• Google Vault — if you’re already paying for Google Workspace Business Plus or higher, Vault is included. Not portable, not self-hosted, but zero additional setup.

---

Bottom Line

Bichon fills a gap that’s been genuinely underserved in the self-hosted space: a single-binary email archiver that requires no external dependencies, handles deduplication correctly from the start, and exposes a real API. The Rust foundation means it runs lean and avoids a whole class of concurrency and memory bugs common in similar tools built on older stacks. The trade-offs are real — AGPL-3.0 instead of MIT, no SSO yet, a young community, no managed cloud option — but for a founder or small team who just needs “all our email, searchable, on our own server,” the math against commercial archiving services is obvious and the deployment story is clean.

The project is worth watching. At 1,495 stars and active development, it hasn’t yet accumulated the track record that would make it a safe default recommendation for production-critical use. But for archiving — where the failure mode is “search is slow” rather than “business stops” — it’s a reasonable bet for technically capable teams who’d rather own the data.

---

Sources

Primary sources:

1. GitHub Repository and README — rustmailer/bichon (1,495 stars, AGPL-3.0 license, 245 commits). https://github.com/rustmailer/bichon
2. Bichon De-duplication Wiki — deep-dive on the Message-ID storage strategy. https://github.com/rustmailer/bichon/wiki/De%E2%80%90duplication
3. Bichon 2026 Roadmap Survey — user feedback form listing S3 and Enterprise SSO as candidate roadmap items. https://docs.google.com/forms/d/e/1FAIpQLScOlwsiUMfyQPBCLW2MLkygdRmAutEgvXDYPzzvEGPz0HFPXQ/viewform
4. Docker Hub — rustmailer/bichon — container image and pull statistics. https://hub.docker.com/r/rustmailer/bichon

Note: No independent third-party reviews of Bichon as email archiving software were available at the time of writing. All claims in this article are sourced from the project’s own documentation [1][2][3] or represent general market context for the email archiving category.