First commit on a rainy Saturday
A focused build to make API mail, direct SMTP delivery, domain verification, logs, and webhooks live in one managed platform.
Sendix exists because password resets, invoice receipts, webhooks, and delivery logs should be dependable infrastructure, not a daily support queue.
Sendix is built around a simple idea: the platform should own the difficult parts of email delivery instead of passing that complexity to customers.
I am building it as a managed SaaS product with native SMTP delivery, domain verification, webhooks, and operator tooling in one place.
Four operating values we've held since the first commit. Each comes with the receipts.
We pick the dependency that has been quiet for ten years over the one trending this week. Email is plumbing; plumbing should not break.
DKIM, SPF, DMARC, FBL, suppression, warmup — the rails so your messages reach the inbox, not a junk folder.
Metrics, traces, runbooks, chaos drills. The platform you call at 3 AM should look the same as the one you onboarded on at 3 PM.
No per-seat fees, no usage tiers buried behind a sales call. The number on the pricing page is the number on the invoice.
From one commit to a managed Sendix platform with API, SMTP engine, webhooks, DNS verification, and operator controls.
A focused build to make API mail, direct SMTP delivery, domain verification, logs, and webhooks live in one managed platform.
The product shape became clear: verified domains, queue-backed sending, DKIM signing, webhooks, and admin operations before marketing claims.
The platform is being tightened around real DNS, real status checks, admin controls, and native SMTP delivery without third-party SMTP providers.
Sendix is built and operated by a solo founder. Every line of code, every deliverability tweak, and every support reply comes from the same person.

Quietly built on tools that have been quiet for years
Sendix is a one-person company today. These are the product areas getting the most attention.
Own the reputation engine, ISP feedback loops, suppression policy, and the warmup curves that decide whether a customer’s first send lands.
Scale the send pipeline, queue topology, and storage layer past the next 100× without anybody noticing. Touch Postgres, Redis, BullMQ, Fastify.
Run the docs, the SDK guides, the conference talks. Equally happy in a Notion brief, a CI pipeline, or a keynote rehearsal at 2 AM.
Sendix is not hiring at the moment. The best way to reach the founder is still a direct note through the contact page.
The product is open, the principles are public, and the team is one email away. Start with the docs, finish with a deployment.