Infrastructure, not templates
Every item below is running in production on this domain right now — not a mockup, not a roadmap. We built them because we needed them. You can run the same checks we run, on your own site, before you decide.
01 — 03
Three components, each solving a problem that cost us real money to discover. Buy one, or take the suite.
Receipt, delivery, and notification templates authored to the constraints Outlook and Gmail impose. Table layout, fully inline styles, zero external assets. Includes the send-channel wiring with automatic failover between providers — and, unlike most implementations, it records every delivery that fails instead of swallowing the error.
22 checks across four separate profiles, run against any URL you give it. It reports what it could not determine as UNKNOWN rather than counting it against you — because a scanner that guesses is worse than no scanner. The self-serve version is public and free; the paid tier adds the crawler-directive and indexing analysis that took us three separate incidents to get right.
Detects the visitor's language and offers the page in it — in their language, phrased natively, never machine-stitched. Two script tags, no build step, no framework requirement. Respects an explicit choice permanently and never overrides a returning visitor. The suggestion bar you may have just seen on this page is this product.
The same combination running on this domain: audit finds the problem, language layer widens the reach, mail studio confirms the sale. Installed and verified on your site by us, with the deployment gates we use ourselves.
04 — not ready
Listed because people keep asking for it, not because we can deliver it today. It cannot be bought from this page and nothing here takes payment.
Mailboxes on your own domain, on the stack we are standing up for ourselves rather than a tenancy resold from someone else. SPF, DKIM and DMARC verified by measurement instead of by a dashboard checkbox, and every delivery result recorded — the failures included, because a send that returns an error is not a send. Outbound sending is not open yet, so this is a waitlist, not a purchase. Registering costs nothing and asks for no payment details.
Why us
Each of these is a rule we now enforce automatically, because we got it wrong first.
A config listing showed our mail key was set. It was an empty string. Now every credential is verified by the code that reads it, reporting from production.
A .bak left beside a worker file is served publicly. Our deploy refuses to run when it finds one.
Client-supplied totals are only ever compared, never trusted. Mismatch is rejected before payment.
A send that returns 401 is not a send. Every delivery result is checked and recorded, so a customer who paid and got nothing is findable.