mailplace.hr
What is mailplace.hr?
A freshly registered sending domain has no reputation, so mailbox providers treat it with suspicion. Send a thousand transactional emails on day one and most of them land in spam. Warming the domain — starting small and raising the volume on a schedule the providers recognise — fixes that, but doing it by hand means a spreadsheet tracking which domain is on which day and how much it's allowed to send.
I built Mailplace for two reasons. The first was that I was tired of the spreadsheet. The second, and the one that mattered more, was not wanting a third party sitting in the middle of our transactional mail. The big sending providers see everything that passes through them — every recipient, every subject, every timestamp. For products whose whole point is that your data stays in the EU and out of other people's hands, routing the mail through someone else's servers would have been a strange exception to make. So we send it ourselves.
It runs on your own infrastructure, against your own IPs and domains. You set the ramp once — where it starts, where it ends, how fast it climbs — and it follows the curve, watches the bounce and complaint rates as it goes, and backs off on its own if a domain's reputation starts to slip. After that you mostly leave it alone.
What it does
Automated volume ramp
Set where the schedule starts, where it ends, and how fast it climbs. Mailplace follows the curve and adjusts the daily limit itself. No manual stepping, no spreadsheet.
Many domains at once
Warm five domains or fifty. Each gets its own schedule, its own reputation tracking, and its own limits, watched from one place.
Self-hosted, your own IPs
Your servers, your domains, your reputation — not a shared sending pool where you inherit a stranger's blacklist, and not a relay that gets to read your mail on the way out.
Bounce and complaint tracking
Watches bounces, spam complaints, and delivery rates per domain, and pauses the warmup automatically if the signals drop below what you set.
DKIM, SPF, DMARC
Guided setup for the authentication records, validated against your DNS before anything sends — because most of deliverability is getting those records right in the first place.
A dashboard that answers one question
Daily volume, delivery, bounces, and warmup progress per domain. Mostly it's there to tell you whether a domain is ready yet, without reading logs to find out.
How it's built
Built in Go and Rust, with PostgreSQL for state. It runs on any Linux server you point it at — no external service in the loop, no per-email cost, and no relay that sees your mail on the way out. The authentication records (DKIM, SPF, DMARC) are validated before a domain starts sending, since that's where most deliverability is won or lost.
Where we are
In active development, and already running in-house warming our own sending domains — which is what it was built for. The scheduling engine and the reputation back-off work today; the dashboard and bounce tracking are being finished.
A private beta for outside teams is planned. If you're running several sending domains and warming them by hand — or not warming them and wondering why your mail keeps landing in spam — that's the conversation to have.