StellarVerifier: Building a Proprietary Email Verification Engine From the Ground Up

Published September 2026 · SaaS / Email Infrastructure

The Challenge

Every cold email operation lives or dies on list quality — sending to invalid or risky addresses tanks deliverability and can trigger the exact spam-complaint thresholds that get domains blacklisted. Most verification tools on the market rely on cached databases or pattern-based guessing rather than checking mailboxes live — and the ones that do live verification charge per-credit, with costs scaling directly against the volume an agency needs to verify across dozens of client campaigns. The goal was to eliminate the need for a third-party tool or ongoing per-verification credit spend entirely.

What I Built

Built StellarVerifier as an independent, live SMTP verification system rather than paying for a third-party API. The architecture separates concerns cleanly: a Next.js frontend for the user-facing product, a Node.js API layer between the frontend and the engine, a real-time SMTP verification engine running in an isolated containerized environment, and Supabase handling auth and the database layer.

Isolated Verification Engine — fully containerized and separated from the main application for stability and security
Dedicated API Layer — a Node.js service between the product and the engine, so the two scale and deploy independently
Supabase-Backed Auth & Data Layer — a managed, scalable foundation for user accounts and application data
Automated Backup Strategy — covers the full application data layer

Why It Worked

Third-party verification APIs charge per credit and rely on cached, often stale data. Building a live SMTP verification engine instead means checking a mailbox's real-time state, with zero per-verification cost and no dependency on someone else's database.

💡

Owning the verification engine over renting one killed per-check costs entirely

Results

Fully Operational, Independent System — built and owned end-to-end, not licensed or rented from a third party
Live SMTP-Level Verification — checks mailbox validity in real time rather than relying on static list-matching or pattern guessing
Zero Per-Verification Credit Cost — eliminated entirely by owning the infrastructure end-to-end, removing an ongoing operating expense that scales with volume

Conclusion

Choosing to build rather than pay per credit meant a slower initial setup, but zero marginal cost per verification going forward regardless of volume. Isolating the verification engine in its own containerized environment kept the core product stable even while the underlying verification logic was iterated on, and treating infrastructure as a product from day one — proper backups, environment separation, documented deployment — rather than a quick internal script.

StellarVerifier demonstrates the same infrastructure-ownership philosophy applied across all of Lead Gen AI Systems' work — building systems that are owned and controlled end-to-end, rather than paying recurring fees to third-party vendors. It's a working proof point that the same discipline used for client cold email infrastructure extends to building standalone products, with zero per-verification cost as the direct result.