Wildmail

Email intake for real workflows

Make incoming email work for your application.

Bring invoices, orders, and claims into your app as signed JSON. Shape the fields, inspect deliveries, and replay retained events.

Test before changing DNSSigned deliveryReplay retained events

Email becomes an event

email.received

Signed webhook
Illustrative payload excerptJSON
{
  "schema_version": "wildmail.v1",
  "event_type": "email.received",
  "event_id": "evt_example",
  "message": {
    "subject": "Purchase order PO-8812",
    "attachments": [{
      "filename": "purchase-order.pdf",
      "download_url": "https://wildmail.app/api/messages/…/attachments/…"
    }],
    "authentication": {
      "dkim": { "result": "pass" }
    }
  }
}
01

Email received

02

Parsed content

03

Delivery history

What works today

From incoming email to the JSON your app needs.

Signed delivery, flexible payloads, and a clear view of every attempt.

Keep your focus on the workflow. Wildmail handles incoming email, attachments, and webhook delivery.

  1. 01

    Start with a real email

    Get a Wildmail test address, connect a webhook, and receive your first message before changing DNS.

  2. 02

    Keep the source and context

    Keep the original email while retained. Get parsed content, attachment details, and available sender-authentication results.

  3. 03

    Shape the payload

    Choose the fields your app needs. Rename keys, build nested JSON, and preview each endpoint’s payload.

  4. 04

    Verify each delivery

    Verify HMAC-signed events and access private attachments with scoped API keys.

  5. 05

    Recover and replay

    Inspect attempts, fix your receiver, and replay retained events. Stable IDs help prevent duplicate actions.

Open-source foundations

Built on proven email foundations.

Wildmail is powered by WildDuck and Kirin, bringing proven email infrastructure to your application.

WildDuck logo

WildDuck

Message processing and storage

Parses incoming messages and manages attachments, message storage, and retention.

Explore WildDuck
Kirin logo

Kirin

Inbound SMTP

Receives email over SMTP and connects the intake flow to WildDuck.

Explore Kirin

Plans and pricing

Every plan includes a hosted test address, signed webhook delivery, payload shaping, private attachments, and delivery history. Retry and replay require positive retention.

Free

€0/ month

No card required

  • 1 custom domain
  • 10,000 messages per month
  • 5 MiB per raw email
  • 0–7 days of retention
  • 2 GB retained storage
  • Domain catch-all routing
Sign in

Monthly message limits reset on the first day of each month at 00:00 UTC. Hard limits apply. There are no automatic message overage charges.

Size limits cover the full email, including encoded attachments. At 0 days, at most one attempt, no retry or replay. Plan and retention details.

Your first event

Your first event, without the DNS setup.

Try the full flow with your Wildmail test address. Connect your own domain when you’re ready.

  1. 01

    Create a webhook endpoint

    Add your endpoint URL and save the signing secret.

  2. 02

    Copy your test address

    Connect your endpoint and send an email with a sample attachment.

  3. 03

    Inspect and replay

    Check the parsed event and delivery history. Replay retained events after a fix.

  4. 04

    Bring your own domain

    Verify a receiving subdomain and point its MX records to Wildmail.

Product direction · Planned

The next step: trusted application contracts.

We’re working toward schema-defined routes, validated data with source provenance, and testing changes against retained messages. These are planned capabilities.

01

Schema-defined routes

Declare which address expects which event and pin a route revision when mail arrives.

02

Validated events

Map fields from messages and documents into typed output with clear validation outcomes and provenance.

03

Contract testing and replay

Run draft contracts against saved messages, compare results, and promote changes with evidence.

Try the full intake path

One email can start your next workflow.

Sign in, connect a webhook, and choose the payload your app receives.

Sign in