Our deepest specialisation: private mail servers, dedicated SMTP and the authentication, warm-up and monitoring that get mail to the inbox.
29 services in this discipline. Each one says what it includes and how we approach it — no jargon, no vague promises.
01
Your own mail server on your own IPs — no per-message pricing and no shared reputation.
Your own mail server on your own IP addresses, which removes per-message pricing and stops another sender's behaviour affecting your delivery. We handle installation, authentication, hardening and the warm-up plan that makes it actually viable rather than theoretically possible. You get full documentation, because a mail server nobody understands is a liability.
02
The full sending and receiving stack installed and configured from a bare server.
The complete stack — MTA, storage, authentication, TLS, spam filtering and webmail if you want it — installed and configured from a bare server. Everything is documented so it remains maintainable by someone other than us. Sending and receiving are both tested against real external providers before handover.
03
Sending infrastructure configured for volume, authentication and clean queue behaviour.
A sending server configured for your expected volume, with authentication, connection and rate tuning, queue policy and useful logging. Built to be diagnosable when something goes wrong at two in the morning, which is when mail problems tend to surface. Credentials and relay access are locked down so it can't be used by anyone else.
04
Licensed MailWizz deployed, tuned and connected to your delivery servers and lists.
Licensed MailWizz deployed and connected to your delivery servers, with lists, segments, bounce handling, feedback loops and cron jobs configured correctly. In our experience most MailWizz problems come down to cron scheduling and delivery-server misconfiguration, so we get those right first. Tracking domain, unsubscribe handling and templates are set up alongside.
05
Production access, dedicated IPs, configuration sets and reputation dashboards set up properly.
Whichever sending platform you are on, we take it from sandbox to production: access requested and granted, domains and DKIM verified, dedicated IPs where volume justifies them, and event destinations wired into your own dashboards. We tune sending rate against your actual reputation metrics rather than pushing blindly toward the quota. Suppression list management is configured so bounces don't repeat.
06
Open-source Postal deployed as a self-hosted sending platform with full control.
Postal deployed as a self-hosted sending platform, with organisations, mail servers, webhooks and API access configured for your workflow. A strong option when you want full control and a proper interface without ongoing licensing costs. Message retention, tracking and IP pools are configured to suit your sending profile.
07
Queues, transport maps, TLS and relay rules configured for reliable delivery.
Transport maps, relay policy, TLS, header rewriting, queue tuning and per-destination rate limits set for your actual sending pattern. Configured to be debuggable through logs rather than guesswork, which matters enormously during a deliverability incident. Sensible defaults are replaced with values that reflect real-world receiver behaviour.
08
Virtual MTAs, IP pools and traffic shaping for genuinely high-volume sending.
Virtual MTAs, IP pools, domain-level throttling, bounce classification and traffic shaping for genuinely high-volume sending. Configuration is matched to each receiving network's known tolerances rather than applying one global rate. Logging is set up so per-domain performance can be analysed properly.
09
Diagnose and fix the real reason your mail lands in spam instead of the inbox.
We audit the whole path — authentication, IP and domain reputation, content, list hygiene, engagement and complaint rates — to identify the actual cause rather than guessing. You get a prioritised fix list with the reasoning explained, and we implement it. Results are measured by inbox placement, not by whether the message was accepted.
10
Isolated sending infrastructure where the reputation you build belongs only to you.
Isolated sending infrastructure where the reputation you build belongs only to you and nobody else's mistakes affect your inbox rate. Includes warm-up, monitoring and ongoing maintenance, because a dedicated setup left unmanaged performs worse than shared. Suits regular senders with meaningful volume and a long-term view.
11
Cost-effective sending for lower volumes without running your own infrastructure.
For lower volumes where running dedicated infrastructure isn't justified, we set you up on well-maintained shared sending with proper authentication on your own domain. Cheaper to run, with a clear upgrade path to dedicated when your volume grows. We'll tell you honestly which side of that line you're on.
12
Receipts, OTPs and alerts on a separate, protected path so marketing can't break them.
Receipts, password resets, one-time passwords and alerts sent on a separate path from marketing, so a campaign problem can never delay a login code. Separate IPs, separate subdomains and tighter monitoring keep the critical mail critical. Delivery latency is monitored, since a slow OTP is effectively a failed one.
13
An architecture that sends at scale without burning your domain's reputation.
An architecture designed for volume: multiple sending IPs, domain separation, queue management and throttling per receiving network. Built so that growth means adding capacity rather than rebuilding from scratch. Segmentation by engagement is designed in, because sending to unengaged recipients is what damages reputation fastest.
14
Authorise your senders correctly and stay inside the DNS lookup limit.
Every legitimate sender authorised, nothing extra included, and the record kept within the ten DNS lookup limit that silently breaks a surprising number of setups. Verified against real sending rather than only syntax-checked. We also remove the stale includes left behind by services you stopped using years ago.
15
Cryptographic signing so receivers can verify your mail wasn't altered in transit.
Keys generated, published and signing verified for every sending source, with a rotation plan agreed. Alignment with your From domain is checked, since DKIM that passes but doesn't align won't satisfy DMARC. Key length and selector naming follow current recommendations.
16
Policy and reporting that stops others spoofing your domain and shows you who tries.
We start at p=none with reporting enabled, read the actual aggregate reports, fix what's failing, and only then move you to quarantine and reject. Rushing straight to reject is the most common way legitimate mail disappears without anyone noticing. Reports are monitored on an ongoing basis, not just during setup.
17
Reverse DNS matched to your sending hostname — a basic trust signal every filter checks.
Reverse DNS set on each sending IP to match its forward hostname, which is one of the first things receiving servers check. We coordinate with your hosting provider where they control the IP range. Forward and reverse records are verified to match in both directions.
18
Open and click links served from your own domain instead of a shared, often-blocked one.
Open and click tracking links served from your own subdomain with its own SSL certificate, instead of a shared domain that may already be blacklisted. It also stops your links looking suspicious to both filters and recipients who hover before clicking. Redirects are configured so tracking doesn't add noticeable delay.
19
SPF, DKIM, DMARC and BIMI aligned and verified end to end.
SPF, DKIM, DMARC and where useful BIMI, configured, aligned and verified end to end from a real test send to major providers. You receive evidence that it passes, not an assumption that it should. Every sending source you use is included, which is where most setups have gaps.
20
A staged volume plan that builds reputation instead of triggering immediate blocks.
A staged volume schedule across several weeks, starting with your most engaged recipients, because reputation is built on engagement rather than raw volume. We monitor and adjust the ramp based on what receivers actually do, rather than following a fixed table. Rushing warm-up is the single most common cause of a new setup failing.
21
Hard and soft bounces processed automatically to protect your sender score.
Hard bounces suppressed immediately, soft bounces retried within sensible limits and suppressed after repeated failure. Keeping invalid addresses out of your sends is one of the highest-impact deliverability fixes available and costs nothing. Bounce reasons are categorised so you can see whether the problem is your list or your reputation.
22
Spam complaints captured and suppressed immediately, before they compound.
Spam complaints captured through feedback loops and list-unsubscribe headers, then suppressed instantly across every list you hold. Complaint rate is monitored as a leading indicator rather than reviewed after the damage is done. A rising complaint rate triggers an alert while there's still time to act.
23
ISP feedback loops registered so complaint data actually reaches your system.
Registered with the ISPs that offer feedback loops, with the reports parsed automatically into your suppression list. Without this you simply don't find out who marked you as spam until your delivery has already degraded. Coverage is documented so you know which providers report and which don't.
24
Watch deferrals and queue growth so a slowdown never becomes an outage.
Queue depth, deferral reasons and per-destination behaviour tracked continuously, because a rising deferral rate is the earliest warning of a block. Alerts reach you before customers notice missing mail. Historical data shows whether a problem is new or has been building quietly for weeks.
25
Identify the listing, fix the underlying cause, and file the delisting request.
We identify which lists you're on, determine the sending behaviour that caused it, fix that first, and then file the delisting request. Delisting without fixing the cause simply repeats the problem within a week or two. You get an explanation of what triggered it, so it can be avoided rather than just resolved.
26
Encrypted transport correctly configured for SMTP, IMAP and webmail.
Certificates and modern TLS configured for SMTP, submission, IMAP and webmail, with opportunistic and enforced TLS applied where each is appropriate. Encrypted transport is now a trust signal to receiving servers as well as a privacy measure. Configuration is verified externally rather than assumed from the config file.
27
Every mail-related DNS record set, propagated and verified.
MX, SPF, DKIM, DMARC, tracking and autodiscover records set, propagated and verified together, because mail breaks when any single one of them is wrong. The result is documented as a complete zone you can hand to anyone who needs it. We check from multiple resolvers before confirming completion.
28
Move providers or servers without losing a single message or breaking authentication.
Mailboxes, DNS records, authentication and sending history moved with an overlap period so nothing is lost during the switch. Cutover is planned around your sending calendar rather than ours. Reputation transfer is handled deliberately, since a new IP or domain starts from zero regardless of your history.
29
Ongoing checks on reputation, deliverability and queue health, with fixes as needed.
Ongoing checks on reputation, blacklists, authentication, queue health and deliverability by destination, summarised in a report you can actually read. Problems are caught and fixed before a campaign is affected rather than diagnosed afterwards. This is the difference between a mail setup that works for a month and one that works for years.
Intelligent systems that take repetitive work off your team — from LLM-powered assistants to end-to-end business process automation.
Production-grade Telegram bots for sales, support, payments and trading — built on the official Bot API and ready to scale.
Reach customers where they already are. Official WhatsApp Business API setup, chatbots, broadcasts and CRM-connected workflows.
Let's talk
Tell us what you are trying to do. If we are not the right people for it, we will say so.