Cold email infrastructure that runs itself.
outreachstack finds leads from a 343M-domain lake you don't rent from anyone, provisions and warms its own sending domains, and improves its own sequences from reply data. One API. One CLI. No vendor dashboards.
$ outreachstack domain add outreachstack.org✓ MX, SPF, DKIM, DMARC provisioned via Cloudflare✓ records verified — 4/4 resolving$ outreachstack icp create --from-url acme-competitor.com✓ criteria drafted — 12 dimensions, awaiting approval$ outreachstack leads build --icp icp_8f21 --limit 500✓ 500 leads promoted — verified, deduped, provenance attached$ outreachstack campaign launch✓ sequence live — replies route to the unified inbox// zero dashboard visits. zero manual DNS.
Four stages. Each one owned end to end, not stitched from vendors.
Owned domain data, not a rented list
343M domains, ~1,570 zones, ~300k new registrations a day. MX and TXT records reveal the target's email provider and tech stack before you ever send a message — an ICP is a query against this lake, not a CSV someone else already sold four times.
Sending domains provision and warm themselves
DNS, SPF, DKIM, DMARC, and a warmup ramp are API calls, not runbook steps. Setting up a new sending domain end to end is one CLI command — zero dashboard visits, zero hand-edited DNS.
Sequences that write and optimize themselves
A bandit optimizer runs Thompson sampling over subject and body variants, rewarded on positive reply rate — not opens, which are unreliable and trivially gamed. Model choice is an eligible arm alongside copy.
An autopilot that watches reputation every 15 minutes
Bounce rate, complaint rate, blocklist status, and seed-inbox placement feed a control loop that throttles, rotates, or pauses before reputation collapses — with hysteresis so it can't oscillate, and a hard ceiling so it can never raise volume past the ramp curve.
The company selling this runs its outbound on it.
Tenant #1 is us. Our own sending domain is provisioned, warmed, and sent from through the same API and CLI every other tenant uses — deliberately kept separate from the brand domain you're reading this on, so a reputation problem on one never touches the other. If the deliverability autopilot has a bug, we find it in our own inbox first.
Every operation is an API call — the UI and CLI are just two clients of it.
Domain purchase, DNS records, DKIM publication, mailbox connection, sequence launch — none of it is a runbook step, and none of it exists only behind a click. That means an autonomous agent, your CLI, and the dashboard all sit on the same /api/v1 surface, authenticated with the same scoped, tenant-bound keys and subject to the same access control as a human operator.
The dashboard for operators who want to look at the data.
Full parity with the UI — generated from the same contract, so it can't drift.
Ordinary API consumers with scoped keys — no privileged back door, so every action is auditable.