Last updated: August 4, 2026
Self-hosted email verification means running email verification software on your own servers instead of sending addresses to a cloud API. The software performs the same checks a cloud verifier does: syntax validation, DNS and MX lookups, SMTP mailbox probing, disposable and role account detection, and catch-all analysis. The difference is where it runs and who holds the data. With a self-hosted setup, email addresses never leave your infrastructure, there is no per-email fee, and you are not dependent on a vendor's uptime or pricing changes. The trade-offs are real: SMTP verification requires outbound port 25 access and clean IP reputation, which most cloud hosts restrict, and you take on deployment and maintenance work. In 2026 the realistic options are two commercial products, EVA Self-Hosted and Reacher, one small perpetual-license tool, Wipebounce, and several open source libraries such as Truemail and AfterShip email-verifier.
Three reasons teams move verification onto their own infrastructure.
Email addresses are personal data. Sending your list to a cloud verifier makes that vendor a data processor you must vet, contract with, and audit. Self-hosting keeps every address inside infrastructure you control, so there is no third-party transfer to justify.
Cloud verifiers typically charge $2.00 to $2.75 per 1,000 emails at volume. At a million verifications a month that is $24,000 to $33,000 a year, every year. Self-hosted software costs the same whether you verify ten thousand or ten million.
Cloud verifiers change prices, expire credits, and sometimes shut down. Software you run yourself keeps working on your terms. With a perpetual license or open source code, nobody can turn your verification pipeline off.
Six products and libraries you can actually run today, from one-time commercial licenses to free open source code. All facts checked August 2026 against the linked sources.
| Option | License model | Price | Language / stack | Dashboard / API / bulk | Maintained | Support included |
|---|---|---|---|---|---|---|
| EVA Self-Hosted | One-time perpetual license | $4,995 one-time (Deployment); OEM source from $29,995 | Go, PostgreSQL, Redis, Docker Compose | Yes / Yes / Yes (50,000 per job) | Yes | Yes, priority support + 12 months of updates |
| Reacher | AGPL-3.0 open source, or monthly commercial license | Free under AGPL; €699/month commercial | Rust, Docker | No / Yes / No UI | Yes | With commercial license |
| Wipebounce | One-time lifetime license | $149 single domain; $749 with unlimited subdomains | Go backend, Vue.js frontend | Yes / Yes / Yes | Uncertain; listed for sale by its developer | Not published |
| Truemail | Open source, MIT | Free | Ruby gem, plus truemail-rack API server | No / Yes (truemail-rack) / No | Yes | Community only |
| trumail | Open source, BSD-3 | Free | Go | No / Yes / No | No; repository archived since July 2018 | None |
| AfterShip email-verifier | Open source, MIT | Free | Go library | No / Reference API server only / No | Yes | Community only |
Pros: The only option on this list that ships a complete product rather than an engine: web dashboard, REST API, bulk CSV/XLSX jobs up to 50,000 emails, Prometheus metrics with Grafana dashboards, and a 28-check pipeline with provider-specific SMTP strategies for Google, Microsoft, Yahoo, Apple, ProtonMail, Zoho, and Mail.ru. The Deployment License is $4,995 one-time with unlimited verifications, priority support, and 12 months of updates; renewals afterward are optional at $995/yr and the software keeps running either way. An OEM Source License from $29,995 adds the full Go source.
Cons: It is commercial software with no free self-hosted tier, and the standard license ships Docker images, not source. It is also our product, so weigh this section accordingly and see the license page for exact terms.
Pros: A well-regarded open source Rust engine with an active repository at github.com/reacherhq/check-if-email-exists and good self-hosting docs. If your service can comply with AGPL-3.0, meaning you publish your source, it is free to run. There is also a hosted SaaS at $69/month for 10,000 verifications.
Cons: For proprietary commercial use the license is €699 per month, which is €8,388 per year recurring, with servers extra. What you get is a REST API backend, not a product: no dashboard and no bulk upload UI. See our full EVA vs Reacher comparison.
Pros: The cheapest commercial option: lifetime licenses at $149 for a single domain or $749 with unlimited subdomains, one-time. It is a real application with a Vue.js dashboard on a Go backend, bulk verification with greylist retries, an API, webhooks, and multi-user support.
Cons: The project's future is uncertain. As of August 2026 the developer has listed the entire product for sale, citing lack of time. A verifier that stops receiving updates degrades quickly as mail providers change behavior, and no support terms are published.
Pros: A configurable, MIT-licensed Ruby validator (github.com/truemail-rb/truemail) with four validation layers: allowlist/blocklist, regex, DNS/MX, and SMTP. The companion truemail-rack project wraps it in a lightweight web API, and both ship as Docker images. Free and maintained.
Cons: It is a library for Ruby developers, not a product. No dashboard, no bulk file processing, no disposable-domain intelligence at commercial depth, and no vendor support. You own IP reputation, proxy rotation, and provider quirks yourself.
Pros: Historically notable as a free, BSD-licensed Go verification server with a public API and Docker image. The code still exists and can be studied.
Cons: Abandoned. The GitHub repository was archived and made read-only in July 2018 and has not been updated since. Eight years of provider changes make its SMTP classifications unreliable today, and its dependencies are unpatched. Do not use it in production.
Pros: An actively maintained, MIT-licensed Go library (github.com/AfterShip/email-verifier) with roughly 1,600 GitHub stars. It covers syntax, MX, SMTP, disposable domains, role accounts, free providers, Gravatar, and typo suggestions, and it supports SOCKS5 proxies for SMTP checks where port 25 is blocked. A good foundation if you are building your own verification service in Go.
Cons: It is a library, not an application. There is only a reference API server, so the dashboard, queueing, bulk processing, storage, and reporting are all yours to build, and there is no commercial support or accuracy tuning for individual mail providers.
Cloud verifiers charge per email; published volume rates from leading services run $2.00 to $2.75 per 1,000. A one-time license is a fixed cost, so break-even is simple division. The table uses the $4,995 EVA Deployment License as the reference.
| Monthly volume | Cloud cost at $2.00 to $2.75 per 1,000 | One-time $4,995 license breaks even in |
|---|---|---|
| 100,000 emails/mo | $200 to $275 per month | 18 to 25 months |
| 500,000 emails/mo | $1,000 to $1,375 per month | 4 to 5 months |
| 1,000,000 emails/mo | $2,000 to $2,750 per month | 2 to 3 months |
Add roughly $10 to $50 per month for a server with port 25 open. Below about 100,000 emails per month, cloud pricing usually wins on simplicity; EVA's own cloud plans start free at 300 verifications per month. A monthly license like Reacher's €699/month never breaks even against cloud pricing until volume passes roughly 300,000 emails per month, and the payments never stop.
It depends on what you need. For a complete supported product with a dashboard, API, and bulk processing, EVA Self-Hosted ($4,995 one-time) is the strongest option. If you can comply with AGPL-3.0, Reacher's open source engine is free to self-host, with a €699/month commercial license otherwise. Developers who only need a library can use AfterShip email-verifier (Go, MIT) or Truemail (Ruby, MIT) for free.
Yes. Reacher's check-if-email-exists engine is free under AGPL-3.0 if you open source your service. Truemail (Ruby) and AfterShip email-verifier (Go) are free MIT-licensed libraries. None of them include a web dashboard, bulk file processing, or vendor support, so you build and maintain those pieces yourself.
The most reliable check is an SMTP conversation with the recipient's mail server on port 25, asking whether the mailbox exists without sending a message. Most residential ISPs and many cloud providers block outbound port 25, so self-hosters need a VPS or dedicated IPs with port 25 open and a clean sending reputation.
It simplifies compliance. Email addresses are personal data under GDPR, and sending them to a third-party cloud verifier makes that vendor a data processor you must contract with and audit. With self-hosting, addresses never leave infrastructure you control, which removes the third-party transfer entirely. You remain responsible for securing your own deployment.
Open source libraries are free plus server costs. Wipebounce sells lifetime licenses at $149 to $749 one-time. EVA Self-Hosted is $4,995 one-time for unlimited verifications with support and updates. Reacher's commercial self-hosted license is €699 per month, or €8,388 per year. All options also need a server, roughly $10 to $50 per month.
It is not recommended. The trumail repository has been archived and read-only since July 2018. Mail providers change their SMTP behavior constantly, and a verifier that has not been updated in years will misclassify addresses at Gmail, Microsoft, Yahoo, and most large providers. Unmaintained code also accumulates unpatched dependencies.
EVA Self-Hosted is $4,995 one-time: unlimited verifications, full dashboard and API, bulk processing, and 12 months of updates. Or start with the free cloud tier and switch later.