Martin Šíl Mail
ČeskySign in

Private service · no public sign-up

Transactional email from your own applications. Invite only.

Sign-in codes, password resets, order confirmations. They're sent by my own applications, my clients' applications and those of a few people I know personally. Always from a domain they have verified.

Sign inHow it works
Domainsemails this month

  • mujprojekt.cz

    Verified

    1,204

  • kavarna-u-lipy.cz

    Verified

    318

  • todo-appka.dev

    Verified

    57

  • portfolio-jan.cz

    Waiting for DNS

    0
  • Add a domainverified by DKIM

The emails no application can do without

Sign-up, password reset, order confirmation, a reply to a contact form. These emails aren't the main part of what I build, but no application works without them.

So I built a small service of my own on Amazon SES. I use it for my projects, my clients' applications and a few people I know personally. That way I always know who sends from which domain and how delivery went.

Transactional email only

Every email is triggered by the recipient's own action. Nothing else is sent from here.

  • Sign-in codes and password resets
  • Invitations and account verification
  • Order and booking confirmations
  • Receipts and invoices

Rules for every account

The service is small and private. To keep it that way, the same rules apply to everyone.

  • Invite only

    There is no public sign-up. I create every account myself, and only for people I know personally.

  • Transactional email only

    Only email the recipient expects may be sent. Marketing, newsletters and purchased or scraped address lists don't belong here.

  • Bounces and complaints

    Addresses that hard-bounce or mark an email as spam are blocked automatically, and no further email is sent to them. If an account's bounces go over 5% or its complaints over 0.1% of its email, its sending is paused automatically until I've looked into it.

  • Verified domains only

    Every sending domain is verified with DKIM by the person who controls it, who adds the records to its DNS. Nothing is sent from a domain that isn't verified.

  • Sending limits

    Each account can send at most 60 emails a minute and to 300 recipients a day, more only by arrangement. So even a leaked API key can't do much damage.

  • Deliberately missing

    • Campaigns and newsletters
    • Bulk sending
    • Open and click tracking
    • Template editor
    • Public sign-up

From a domain to the first email in minutes

  1. Add a domain

    Enter the domain and add three CNAME records for DKIM to its DNS. Verification finishes on its own.

  2. Create an API key

    You see the key only once. We keep only its hash, never the key itself.

  3. Send an email

    One API call from your application, for example after a sign-up or an order.

  4. Track delivery

    Delivered, bounced, marked as spam. You see every event in the overview.

Everything transactional email needs. Nothing more.

  • A simple REST API

    One POST request with the sender, recipient and content. Errors have clear names and messages.

  • SDKs for Node.js and .NET

    Libraries for TypeScript and C#, so you don't have to write fetch over and over.

  • Attachments

    Send invoices and PDFs right in the request, larger files up to 25 MB.

  • Overview and logs

    Every email and API request is in the overview, including its delivery history.

Invite only

There is no public sign-up. I create every account myself, and only for people I know personally. If you know me and need to send email from your application, get in touch.

  • You know me personally
  • You send transactional email only
  • You have your own verified domain
I have an invite, sign in