Skip to content
Pidgely
  • pidgely
  • email-api
  • deliverability

Why we are building Pidgely

Pidgely is a developer email API that runs its own MTA. Here is why we built it, what already works today, and what comes after email.

Pidgely teamPublished 2 min readMarkdown version

On this page
  1. The problem we kept running into
  2. What Pidgely does today
  3. Built to stay cheap
  4. Email first, more channels next
  5. Frequently asked questions

Pidgely is an email API for developers that delivers mail with its own MTA. You call a REST API that accepts the same send format as Resend. Pidgely signs, queues and delivers the message itself, and reports what happened through signed webhooks.

The problem we kept running into

Most email APIs are a nice interface on top of somebody else's sending infrastructure. That works until you need to know why a message was deferred, which IP it left from, or what happens when a neighbour on the same platform starts sending spam. The answers are usually out of your reach.

We wanted an API that is just as pleasant to use, with a delivery path we fully control and can explain.

What Pidgely does today

  • Its own MTA. Separate IP pools for transactional and broadcast mail, automatic IP warm-up, per-destination concurrency limits and opportunistic TLS.
  • Authentication by default. Per-domain DKIM with RSA-2048 keys, aligned SPF through a custom return-path subdomain, DMARC guidance and automatic DNS checks.
  • List hygiene built in. Bounces (sync and async DSN via VERP) and complaints (ARF feedback loops) feed automatic suppression lists. Every message carries RFC 8058 one-click unsubscribe headers.
  • A familiar API. Batch sends of up to 100 emails, scheduling with cancel, and Idempotency-Key for safe retries.
  • Guard rails for a shared platform. New accounts start in a sandbox with daily quotas, and a reputation guard pauses accounts that cross bounce or complaint thresholds.

Built to stay cheap

Pidgely is one Go binary plus Postgres. Postgres also acts as the queue and stores rate limits and quotas, so there is no separate broker or cache to run. Fewer moving parts mean lower costs and fewer 3 a.m. surprises.

Email first, more channels next

Email ships first because it is the hardest channel to get right. SMS, WhatsApp and push are planned, and they will share the same API keys and webhooks.

If you want to try Pidgely, ask for early access.

Frequently asked questions

What is Pidgely?

Pidgely is a multi-tenant messaging API for developers. It starts with email, sends through its own MTA and accepts the same send request format as Resend.

Does Pidgely use a third-party sending provider?

No. Pidgely runs its own mail transfer agent with its own IP pools. The optional SMTP fallback goes to a second Pidgely-run node.

When can I use Pidgely?

Pidgely is in early access. Email us to join, and we will reply with next steps. Pricing will be published before general availability.

Pidgely team

Published

We build Pidgely, the email API that gets you to the inbox. We write about what we learn delivering email, citing the standards and mailbox provider guidelines behind every claim.

Also available in:

Related articles