Bokimo
NewResend-compatible API and inbound email

Send and receive email without the plumbing.

Bokimo is email infrastructure for product teams: a Resend-compatible API on Amazon SES, templates anyone on the team can edit without a deploy, and inbound mail delivered straight to your webhooks.

Start for freeRead the docs
acme-production
illustrative traffic

Outbound

Your app

POST /emails

Bokimo

template · queue · retry

Amazon SES

DKIM · SPF

Inbox

[email protected]

Inbound

Sender

reply to support@

Amazon SES

receipt rule

Bokimo

parse · route · store

Your app

webhook email.received

Webhook events

Developer API

Already on Resend? Change one line.

Bokimo speaks the Resend API. Keep your SDK, your code and your types. Point the base URL at Bokimo and your email runs on Amazon SES with everything else included.

  • Send, batch, schedule, reschedule and cancel
  • Idempotency keys and Resend-style error codes
  • Domains, API keys, contacts and segments
  • Svix-signed webhooks that resend.webhooks.verify() accepts

$ RESEND_BASE_URL=https://bokimo.ai/api/resend

send.ts · npm i resend
import { Resend } from 'resend';

// RESEND_BASE_URL=https://bokimo.ai/api/resend
const bokimo = new Resend(process.env.BOKIMO_API_KEY);

await bokimo.emails.send({
  from: 'Acme <[email protected]>',
  to: ['[email protected]'],
  subject: 'Your invoice is ready',
  html: '<p>Thanks for your order.</p>',
  tags: [{ name: 'category', value: 'billing' }],
});

Press Run to see the response.

Platform

One system for every email your product sends.

Templates, sequences, logs and environments live next to the API, so email stops being scattered across services, cron jobs and dashboards.

01

Templates outside your codebase

Edit, preview with real data and roll back versions. Copy changes ship without a deploy, and engineers keep a clean API.

02

Sequences without cron jobs

Define onboarding and lifecycle flows with timing and conditions. Pause or change them safely while they run.

03

Inbound email

Receive mail on your own domain. Messages are parsed, stored and pushed to your webhook with attachments.

04

Logs you can actually search

Find any email by recipient, template or time. See the payload, delivery status and every event that followed.

05

Staging and production

Separate environments so you can test with real data, share previews and promote changes when they are ready.

06

Reliability by default

Queued sends with retries, idempotency keys, scheduled delivery and signed webhooks for every event.

Inbound email

Replies are product data too.

Route support@, replies and forwarded receipts into your app. Bokimo parses every message, keeps the attachments and tells your webhook the moment it lands.

  • Works with SES receipt rules, including large messages via S3
  • Routed to the organization that owns the domain
  • Attachments served from signed, expiring links
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

Teams

Clear ownership, fewer handoffs.

Engineering

Keeps control of infrastructure.

  • One API instead of email logic in every service
  • Drop-in for existing Resend SDKs
  • Less code to maintain

Product and growth

Owns timing and messaging.

  • Changes sequences without backend work
  • Ships copy updates the same day
  • Experiments without waiting on a sprint

Operations and support

Sees exactly what was sent.

  • Updates templates safely
  • Answers “did they get it?” in seconds
  • Routes inbound mail to the right place

How it works

Live in an afternoon.

  1. 1

    Connect a domain

    Add your domain and publish the DKIM, SPF and MX records Bokimo gives you. Existing SES identities keep working.

  2. 2

    Move email out of your backend

    Point your SDK at Bokimo and manage templates, sequences and conditions from one place.

  3. 3

    Ship and observe

    Test in staging, promote to production, and debug any message from its event trail in seconds.

Without Bokimo

  • Templates buried in code
  • Sequences spread across services
  • Every copy change needs a deploy
  • Debugging means grepping logs
  • Inbound mail goes to a shared inbox

With Bokimo

  • One system for templates, sequences and logs
  • Changes ship without redeploys
  • Clear ownership across teams
  • Every message traceable in seconds
  • Inbound mail arrives as structured events

Pricing

Pay for emails sent. Not for seats.

No per-seat pricing, no feature gating, no sales call to get started.

Compare plans →

Free

$0

per month

For prototypes and side projects.

  • Template management
  • Sequence builder
  • Sending and inbound API
  • Email search and debugging
  • Email support
Start for free

Pay as you go

Recommended

$0.50

per 1,000 emails

For products in production. No seats, no minimums.

  • Everything in Free
  • Unlimited emails
  • Staging environments
  • Webhook events
  • Priority support
Get started

Enterprise

Custom

volume pricing

For high volume and stricter requirements.

  • Dedicated IP addresses
  • Volume discounts
  • SLA guarantees
  • SSO and advanced security
  • Dedicated support
Talk to us

Why we built it

Built because we needed it.

Every product we worked on ended up with the same mess: templates in code, sequences in backend jobs, and debugging that meant stitching together logs from three services.

SES was great at delivery and nothing else. So we built the layer around it that we kept rebuilding: an API developers already know, tools the rest of the team can use, and a clear record of every email in and out.

FAQ

Questions, answered.

Something else? Get in touch.

Yes. Bokimo exposes a Resend-compatible API, so the official Resend SDKs work by pointing RESEND_BASE_URL at Bokimo. Sending, batch sends, scheduling, domains, API keys, webhooks, contacts, segments and inbound email are supported. Broadcasts are not yet available, and React emails should be rendered to HTML before sending.

Bokimo delivers through Amazon SES and adds templates, sequences, logs, webhooks and inbound email on top. You move sending to Bokimo, verify your domains once, and keep the deliverability benefits of SES without building the surrounding tooling yourself.

Yes. Point your domain’s MX record at SES, and inbound messages are parsed, stored and delivered to your webhook as email.received events. You can fetch the full message, headers and attachments through the API.

No. Product emails, onboarding flows and campaigns live in one system, so you do not need separate tools for transactional and marketing email.

Yes. Templates and sequences can be edited without code, previewed with real data, and promoted from staging to production. Routine copy changes no longer need an engineering deploy.

Sends are queued with retry handling and idempotency keys, delivery events are tracked from SES, and webhooks are signed so you can verify every event. SPF and DKIM are set up when you add a domain.

Yes. If you already use a Resend SDK, migration is a base URL and an API key. Templates and flows can be recreated in Bokimo, and your sending domains are configured during setup.

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