Coming soon
Email, ready for your agents.
pks-agent-inbox
An SMTP server built for agents — every email lands as clean Markdown your agents can read and act on.
Email is how the world talks to your systems. Agents can't read it.
Reports, alerts, requests, hand-offs — most of the work that should reach your agents still arrives as email. So teams bolt on a third-party inbox API, hand their mail to a platform they don't control, and write fragile glue to drag MIME, attachments and HTML soup into something an agent can use. Every layer is a dependency you didn't choose and a place a breach can land. The work is right there in the inbox; it just can't get to the agent cleanly.
Email arrives as MIME, encodings and HTML soup — not as something an agent can act on.
To receive it at all, most teams rent an inbox from a platform they don't own and can't audit.
The glue between "an email arrived" and "an agent did something" is hand-written, brittle, and yours to maintain forever.
How it works
Run one container.
Start pks-agent-inbox, give it a data directory, and it's listening for mail.
Point a domain at it.
One A record and an MX record — your existing DNS stays untouched.
Mail becomes Markdown.
Every message is written to disk as a Markdown file with YAML frontmatter (from, to, subject, date) and its attachments beside it.
Your agents take it from there.
They watch the folder, read clean structured text, and act. No inbox API, no parsing layer in between.
Markdown, not MIME.
Every email lands as a clean Markdown file with YAML frontmatter — machine-readable from the first byte.
One container, port 25.
A single self-contained Go server: give it an address, a domain and a data dir, and it receives mail.
An inbox per domain.
Mail is filed on disk under each receiving domain, so every domain's inbox stays naturally separated.
Attachments kept intact.
HTML bodies and attachments — DMARC reports, files, payloads — are written beside the message, untouched.
Receive-only by design.
No outbound sending, no surprise relay — it accepts mail and stores it, and that's the entire job.
Your disk, your data.
Messages persist to a volume you own across restarts and updates — nothing leaves the machine.
Built from the foundation up. A small, deliberate Go SMTP server we wrote and own — not a managed inbox rented from a platform you can't audit.
No dependency we don't control. It speaks SMTP and writes files. That's the whole surface. Nothing between the wire and your disk that we didn't put there on purpose.
Runs everywhere. A single container with a volume — direct on a host, on Coolify, on your own metal. Your mail never leaves infrastructure you control.
The first layer of the stack. This is the inputs layer: the deliberate front door where outside work enters the suite as clean, structured text the upper layers can build on.
Composes with
The inbox your agents were waiting for.
Point a mail domain at it and you're done. Every message arrives as clean Markdown with structured frontmatter — no parsing, no glue code, no inbox API you don't own. Just work, ready for your agents to pick up.