Koltrix
Customers
One customer so far, and we are it.
Koltrix is new. Rather than fill this page with logos of companies that have never heard of us, here is the one real deployment, in detail, including the parts that were awkward.
ReminderIt
ReminderIt places reminder phone calls. It sends receipts, reminders and password resets, it answers support mail, and people reply to all of it. Every one of those runs on Koltrix.
What is true, and how you can check it
ReminderIt runs its transactional email through the Koltrix API.
Launch plan §3 and §21.1: ReminderIt sends production mail through /api/v2 and the SMTP relay, which is why the public API is contract-tested against regressions.
Its team inbox is on reminderit.com, hosted on Koltrix.
Launch plan §3, 'what you actually use it for'.
Every workspace, ReminderIt's included, lives in its own isolated PostgreSQL schema.
The tenant provisioning path in the API; a test asserts no connection is handed to one tenant pointed at another's schema.
Outbound mail is DKIM-signed at the mail server, so the application does not sign anything itself.
The rspamd milter signs all outbound mail; the DKIM signer health check is in internal/domain.
We are not publishing volume, bounce-rate or time-saved figures until they are measured from production and we can show the query behind each one. A case study with invented numbers is worth less than a short one that is true.
“I built Koltrix because ReminderIt needed to send email and receive replies to it, and nothing I could buy did both. We are customer number one, which is a conflict of interest and also the reason the boring parts work.”
Want to be the second one?
If you move a domain onto Koltrix and it goes well, we would like to write it up — with your numbers, your words and your approval before anything is published.