We built the tool we needed to run our own outbound.
Every cold email vendor sells the same rented list through a different UI. We wanted to own the data supply, not rent access to it — so outreachstack starts from a 343M-domain dataset we ingest and refresh ourselves, not a database everyone else is also buying.
It's multi-tenant from day one, and the company that builds it is tenant #1: our own outbound runs through the same API, the same warmup ramps, and the same deliverability autopilot every other tenant uses. If something in the sending pipeline breaks, we notice in our own inbox before a support ticket tells us.
Everything the dashboard can do, the CLI can do, and everything the CLI can do, an authenticated agent can do — because we think the next generation of outbound tooling gets run by agents as often as by people, and a platform that hides capability behind a click can't be one of them.
We build and host in the European Union, on Hetzner infrastructure, and we say what that covers and what it doesn't rather than putting a flag in the footer and hoping nobody asks.
Where we are
Pre-launch. No paying customers yet, no case studies, no testimonials, and no logos on this site belonging to companies that have never used the product. The only production tenant is our own. When that changes this page will change with it.
Talking to us
There is no sales team to route you through. The fastest way to evaluate outreachstack is the pipeline write-up on the features page and the machine-readable index at /llms.txt, which points an assistant at a Markdown copy of every page on this site.