Bokimo

Platform

Everything around the send, already built.

Delivery is the easy part. Bokimo adds the templates, flows, logs and inbound handling that teams otherwise rebuild in every product.

Start for freeRead the docs

Templates

Copy changes without a deploy.

Templates live in Bokimo, not your repository. Edit them in the block editor or HTML, preview with real data, and promote from staging when they are ready.

  • Version history with rollback
  • Variables with preview data
  • Company header and footer applied automatically
  • Generate a first draft with AI, then refine it
templates / welcome
ContentVariablesPreviewVersions

Subject

Welcome to Acme, Ana

Get started
Edited by Sara · 3 min agoPromote to production

Sequences and events

Lifecycle flows without cron jobs.

Link product events to templates and define onboarding flows with timing and conditions. Pause or change them while they run.

  • Trigger templates from product events
  • Timing and conditions per step
  • Every triggered email visible in the event log
sequences / onboarding
  1. 1

    Welcome

    Day 0

    on user.created

  2. 2

    Connect your data

    Day 1

    if setup incomplete

  3. 3

    Invite your team

    Day 3

    if seats = 1

  4. 4

    Tips from power users

    Day 7

    always

Logs

Answer “did they get it?” in seconds.

Every email is searchable by recipient, template and time, with its payload and the full trail of delivery events that followed.

  • Sent, delivered, opened, clicked, bounced and complained
  • Bounce and complaint reasons from SES
  • API request log for every call
logs
[email protected]delivered
[email protected]opened
[email protected]sent
[email protected]bounced

[email protected] · bounced

Permanent / General — smtp; 550 5.1.1 user unknown

Inbound

Receive email like an API request.

Point your MX record at SES and Bokimo turns each message into structured data: sender, recipients, text, HTML, headers and attachments, delivered to your webhook.

Raw message
Return-Path: <[email protected]>
Received: from mail-ej1 (inbound-smtp.us-east-1)
From: Jon Park <[email protected]>
To: Acme Support <[email protected]>
Subject: Question about my order
Message-ID: <[email protected]>
Content-Type: multipart/mixed; boundary="b1"

--b1
Content-Type: text/plain; charset=utf-8

Hi, order #1042 arrived damaged...
--b1
Content-Type: application/pdf; name="receipt.pdf"
Content-Transfer-Encoding: base64

JVBERi0xLjcKJcfsj6IKNSAwIG9iago8PC9MZW5n...
--b1--
Parsed · GET /emails/receiving/:id

{

"from": "Jon Park <[email protected]>",

"to": ["[email protected]"],

"subject": "Question about my order",

"message_id": "<[email protected]>",

"text": "Hi, order #1042 arrived damaged...",

"attachments": [{ "filename": "receipt.pdf" }]

}

webhook email.received→ https://acme.co/hooks/mail

Foundations

The details that keep email boring.

01

Staging and production

Separate environments with their own keys, so tests never reach real customers.

02

Retries and idempotency

Failed sends are retried, and idempotency keys stop duplicate sends for 24 hours.

03

Scheduling

Schedule up to 30 days ahead with a date or “in 2 hours”, then reschedule or cancel.

04

Signed webhooks

Every event is signed with the Svix scheme, verifiable with standard libraries.

05

Domain authentication

DKIM, SPF and a custom return path set up for each domain you add.

06

Contacts and segments

Store contacts with properties and group them into segments for campaigns.

Send your first email in minutes.

Free to start. Verify a domain, create an API key, and send through the SDK you already use.

Start for freeTalk to us