Professional mail on your domain
CorporateEmail
Writing from a free address costs you credibility with every message you send. We set up mail on your own domain, migrate what you already have, and make sure your messages reach the inbox rather than the spam folder.
What is included
Mailboxes, sending and deliverability
Two different needs that are almost always confused: the mail your team writes by hand, and the mail your application sends on its own.
Mailboxes on your domain
Addresses like name@yourcompany.com for everyone on the team, with the storage each role actually needs.
Webmail and apps
Access from the browser and from the mail apps on your phone and desktop. Works with IMAP, SMTP and POP.
Antispam and antivirus
Incoming mail is filtered before it reaches your inbox, and attachments are scanned.
Sender authentication
SPF, DKIM and DMARC configured from day one. It is what separates mail that arrives from mail the recipient never sees.
Transactional sending
For the mail your application sends: confirmations, password resets, invoices. Delivered over an API, with delivery tracking.
Email campaigns
Newsletters and announcements to your lists, with subscription and unsubscribe handling. Kept separate from transactional mail, as it should be.
Migration from your provider
We bring over your mailboxes, your messages and your folders, and coordinate the record change so not a single mail is lost on the way.
Aliases and shared inboxes
Addresses like sales@ or support@ that fan out to several people, without paying a licence for each one.
How we work
From the first message to day-to-day operation
A few clear steps.
- Project
- Workload
- Budget
Before you decide
Frequently asked questions
What people usually ask before moving the company's mail.
Not here? Write to us
No. We bring your messages, your folders and your structure across as they are. The migration happens before the records change, so there is no window in which mail goes missing.
Almost always because SPF, DKIM and DMARC are missing or misconfigured. It is the first thing we check, and it usually solves the problem without touching anything else.
Yes, and it should be kept separate from your team's mail. Transactional sending goes over an API with its own reputation, so a campaign cannot drag your invoices into the spam folder, or the other way round.
How many accounts do you need?
Tell us how many people are on your team, whether you already have mail elsewhere, and whether your application needs to send mail of its own. We will come back with a firm proposal.
Ask about availability- 24/7 support
- Local engineers
- Cúcuta, Colombia