RemarkableCloud

Apps / Mailcow

Managed Mailcow hosting.
One server, no app limits.

A complete self-hosted mail suite: Postfix, Dovecot, Rspamd, and SOGo webmail in one dockerized stack. Your domains, your mailboxes, your data, running behind the managed mail gateway.

What it is

Mailcow is the complete self-hosted mail suite: Postfix, Dovecot, Rspamd, and SOGo webmail in one dockerized stack. Your domains, your mailboxes, your data, with a real admin UI over all of it. Here it comes paired with what self-hosters usually cannot get: a managed server underneath and MailChannels carrying your outbound.

Minimum RAM

6 GB

Fits on SC-6GB; SC-16GB is the comfortable pick with room to stack.

What we install

The playbook deploys Mailcow dockerized per the official documentation, DNS records (MX, SPF, DKIM, DMARC, PTR) prepared with you, TLS issued, and the stack placed behind the managed network so port 25 life starts on the right foot. Outbound mail leaves preconfigured through our authenticated gateway, so your first message delivers like your thousandth.

What managed covers

Stack and server updates with snapshots first; daily snapshots plus dual offsite backups of every mailbox; monitoring on queues and services; the managed firewall; and a team whose actual specialty is mail infrastructure.

The app is $0. The managed server is the only bill, and everything above is part of it.

What does managed Mailcow hosting include?

The whole suite deployed correctly, DNS done properly the first time, mailboxes backed up twice offsite, and monitoring on the queues. Mail is the most operations-heavy thing you can self-host, and this is a host whose differentiator is mail operations.

Why self-host email at all?

Unlimited mailboxes at flat cost, aliases and domains without per-seat pricing, and mail data under your jurisdiction. Per-mailbox SaaS pricing makes a twenty-inbox company pay forever for what one server does; Mailcow makes mailboxes free to mint.

Is self-hosted mail deliverability hopeless?

Not on infrastructure built for it. Deliverability lives and dies on IP reputation, correct DNS, and authentication, which is precisely the stack we run for a living: SPF, DKIM, DMARC, and rDNS set up as part of the install, on network space we keep clean. Test it yourself with our deliverability tester afterward.

How big a server does Mailcow need?

6 GB of RAM is the official requirement and the catalog respects it: the suite runs a dozen services. SC-8GB is the natural home, with room left for an Uptime Kuma watching it.

How does a brand-new mail server deliver from day one?

Because outbound never leaves from a cold IP. Your Mailcow is preconfigured with our gateway as its smart host, and every message relays out through MailChannels on reputation that is already established, while inbound arrives directly at your server and its own filtering. DKIM stays yours (Mailcow signs, the relay preserves it), and your domains add one SPF include, include:_spf.protectedserver.net, which stays valid even as we grow the gateway behind it. 10,000 external recipients per month are included; heavier senders upgrade the gateway package in the cart or later from the client area.

Stack it

Mailcow runs well with.

Same server, no extra bill. These are the companions our team installs next to Mailcow most often.

Uptime Kuma

+1 GB

The self-hosted uptime monitor everyone loves. Watch your sites from your own server.

WireGuard

+1 GB

The modern VPN protocol, deployed with client configs ready to import and the tunnel verified working.

Frequently asked questions

How much RAM does Mailcow need?

6 GB minimum per the Mailcow documentation, and the resource meter enforces it. Large mailbox counts or heavy filtering move you toward 16 GB.

Are mailboxes backed up?

Daily, twice offsite, the full stack: mailboxes, settings, and DKIM keys. A deleted mailbox is a restore, not a funeral.

Will you help with DNS?

Yes, all of it: MX, SPF, DKIM, DMARC, and reverse DNS are set with you at install, then verified with a real send through our own testing tools.

Does the gateway read or store my mail?

It relays and filters outbound in transit, the same as any reputable smart host; your mailboxes, archives, and inbound flow live entirely on your server. Newsletters and bulk campaigns are a different traffic class with their own rules, so keep those on a campaign platform rather than the mailbox relay.

Why a managed Mailcow instead of running it on a bare VPS?

Running mail alone means being your own sysadmin, deliverability engineer, and blacklist firefighter. Here the pairing does that work: humans patch, monitor, and back up the server, and MailChannels carries outbound reputation, so the part of self-hosted email that usually fails, getting your mail actually read, is handled from the first message. You keep everything that makes Mailcow worth it: your data, your domains, unlimited mailboxes, no per-user fees.

Sizing an app stack? The VPS sizing calculator recommends a plan from your apps and traffic, with the math shown.

Your server runs. You sleep.

Fully managed hosting from people who have been doing this since 2001.