Relentia
Email marketing, running on sending infrastructure we have operated since January 2024.
View companyEmail marketing, running on sending infrastructure we have operated since January 2024.
View companyEmail sending infrastructure, run remotely from Morocco since January 2025.
View companyA bilingual marketing site and the CMS behind it — designed, built and hosted since November 2025.
View companyThe sending operation where Mailflow was first built, 2023 to 2025.
View companyCordytech builds and runs the systems other companies depend on: the sending infrastructure behind operations whose revenue turns on where their email lands, and the software behind businesses that need something built and kept running. These are clients we work for, not companies we own — four engagements, one discipline: build it properly, measure it honestly, and leave the team that has to live with it able to run it.
Mobicentrum came first, from September 2023 to June 2025. It is the engagement where Mailflow was born — we were the software side of their sending operation, writing the scripts and then the application their teams used daily, and we turned that custom build into the product the rest of our work now leans on. One year and ten months, described in the past tense on purpose: finished work hides nothing behind the word ongoing.
Relentia has run on our stack since January 2024 and is the deepest of the three — two and a half years and counting. We operate their servers, addresses and PowerMTA configuration through Mailflow, read their sponsor and affiliate revenue through Revline, hold their files in Storebridge, and built three separate per-ISP reporting applications because Yahoo, Outlook and Gmail do not agree on what a report is. We also built Creator, a private tool that keeps the seed mailboxes their placement testing depends on alive, and trained the whole team on PowerMTA 5.
EMG has run the same programme remotely since January 2025, delivered from Morocco without an on-site week to bootstrap it. That constraint turned out to be the useful part: everything has to live in an application both sides can read rather than in one engineer's shell history, so EMG leaves an install log instead of a memory and a team that can run the thing when the person who built it is offline.
CM Metrology is the newest and the one that is not email at all. They are an industrial metrology and calibration laboratory in Tangier — 3D measurement and inspection, digitisation and reverse engineering, calibration — and since November 2025 we have designed, built, hosted and maintained their public site and the CMS behind it. It is a server-rendered Laravel and Inertia application in English and French, and the point of it is the back office: their team edits every service, product, client logo, testimonial and interface string without us. A marketing site that needs a developer to change a price is a liability, not an asset.
The common thread is that none of these are three-month projects. The per-ISP applications, the seed-mailbox tool, the long tail of custom scripts — none of that arrives in a scoping document. It arrives in month nine, from running a system through a full cycle of good and bad weeks. That is the case for staying rather than parachuting in: the observations that change how an operation runs are the ones you can only make by living with it. If you send at volume and your reporting is one averaged number, that is usually the first thing worth fixing, and it is where each of these engagements started. Tell us what you are sending and where it is landing, and we will look at the actual logs rather than a summary.