About

Cold email you can trust.

Purpgo is a hosted platform for email warmup and cold outreach, built to keep your mailboxes out of spam.

Start freeRead the story

Why Purpgo exists

For years the main tools for cold email have charged by the mailbox while keeping their warmup logic, sending rules and abuse thresholds closed. You paid for volume. You never got to see how decisions about your reputation were made.

We started Purpgo to take that away: we built the sending workers, warmup pool and health rules so you never pay a tax on every mailbox.

So when Purpgo slows a mailbox down, the dashboard says why in a full sentence. The figure beside this is a real one: the reason a throttled mailbox shows, and the rule behind it.

Founders, agencies, sales teams, recruiters and fundraisers get the engine run for them, and see every decision it makes about their mailboxes.

We are a small team in Winnipeg. We say what we are working on, we don’t invent numbers, and the product gets better where everyone can see it.

When deliverability breaks, you should see why in plain words, not write to support and wait.
A mailbox slowed for spam placement, and the rule that slowed it.

What we believe. Six rules the code is held to.

These aren’t values for a slide. They are written into the codebase, and a feature that breaks one doesn’t ship. Each pair below sits next to the code or the record that proves it.

Transparent
  1. 01

    Transparent by default

    Every pause, bounce and health change is explained in the app.

  2. 02

    A dated changelog

    The changelog is public and dated. We don’t invent metrics or pretend to be bigger than we are.

Safe by default
  1. 03

    Safety is per mailbox

    A safe day of sending is the sum of what each mailbox can safely send. We will not ship a feature that pushes a mailbox past its own limits to make a chart look better.

  2. 04

    Act before the providers do

    Our thresholds for the shared warmup pool are stricter than the points where Google or Amazon SES start penalising a sender. By the time a provider would act, the mailbox has already been slowed down.

Nothing hidden from you
  1. 05

    Encrypted by design

    Mailbox credentials are encrypted with a dedicated credentials key, and message content with a data key that belongs to your workspace alone.

  2. 06

    No black boxes

    Every health state, suppression and pool block comes with a reason you can read in the dashboard, and the rules behind them are documented.

How it’s built. One part decides, the other part sends.

Adding capacity means adding small workers, not growing one giant server. Your mailbox provider delivers the mail, so a worker is only where your mailbox signs in from, and Purpgo keeps that stable.

The control plane decides

The backend and consumer hold your data, decide which mailbox sends what and when, and assign each mailbox to a worker.

The bus carries the work

Commands go out on a topic per worker and results come back on one shared stream, over NATS or Kafka.

Workers send and sync

They sign in to your mailboxes, send, sync and report back. They hold no database connection, so one that goes away is simply replaced.

What’s different. An open engine, in a category of closed ones.

PurpgoPurpgoClosed-source tools
DeliverabilityHealth rules shown in-app.Undocumented until something goes wrong.
SetupConnect a mailbox in 2 minutes.Often a setup call first.
Health rulesDocumented, and stricter than provider enforcement.Undocumented until something goes wrong.
ChangelogPublic and dated.Announcements on a marketing schedule.
PricingPer workspace, with warmup on every mailbox and unlimited teammates.Often per mailbox or per seat.

This describes how Purpgo is built. We don’t speak for any other company’s plans or pricing.

The platform. How the platform is put together.

Purpgo platform
  • cmd/backendThe API and the business logic. Owns the database.
  • cmd/consumerFolds results from the workers back into the platform.
  • cmd/workerSends and syncs mail. Holds no database connection.
  • cmd/cliThe purpgo command-line tool.
  • tracking/The open and click tracking service, in Rust.
  • realtime/The live websocket layer for the dashboard, in Elixir.
  • web/The dashboard.
Changelog Security and trust [email protected]

Let us run your outbound.

Start free, no card.

Start free See pricing