← Lab
Showcase · Email and page editor

Design the mailer here. Send it from anything.

Webby is the editor I built for mailers and microsites. Designs are saved as JSON in your own GitHub repo, the email HTML holds up in Outlook, and any mail platform can pull a message ready to send. Webby never sees your contact list. It's wired into the 2nth CRM and listmonk: I design in Webby, the CRM makes the draft, and listmonk sends it.

MITlicence, free for clients
2block kits: web and email
1API call for a send-ready message
0contacts stored in Webby
01 · The problem

Good editors want your list. Good senders have bad editors.

Mailchimp and HubSpot design well, but only if your contacts live with them, at their prices. Open-source senders like listmonk keep the list on your own server, but their editors are bare, and a hand-built HTML email that looks right in Gmail often falls apart in Outlook.

So I split the job. Webby does the design and formatting; the platform that holds the contacts does the sending. The two meet at a small, documented interface, and only design crosses it.

02 · From design to inbox

Webby, the CRM and listmonk, each doing one job.

Webby

Design

  1. Build the email from blocks, with the 2nth brand kit applied.
  2. Personalise with fields like {contact.first_name}, previewed with sample names.
  3. Webby checks Gmail's size limit, missing image descriptions and placeholder links.
Integration API

The package

  1. One call returns the subject, preview text, HTML, plain text and the fields used.
  2. A read-only token, limited to one workspace.
  3. Nothing about a recipient goes the other way.
2nth CRM

The draft

  1. The Mailing tab lists each mailer with a preview and whether it's ready.
  2. Fields become listmonk's own; an unknown field or a missing unsubscribe link is refused, with the reason.
  3. It creates a draft on the opt-in list, and never starts it.
listmonk

The send

  1. I review it and send tests to Outlook and Gmail.
  2. I press Start. Only opted-in, confirmed subscribers receive it.
  3. Sent, opens, clicks and bounces show back in the CRM.
03 · What Webby does

An editor that keeps your work in your hands.

Editor

Drag and drop, two kits

A web block kit for microsites and an email block kit for mailers, with preview at desktop and phone widths. Copy or download the HTML for any host or mail platform.

Brand kits

Read from your website

Colours, fonts, logo and images proposed from an existing site or a CSS or design-token file, confirmed by a person, then applied to a whole project.

Git

Your repo, both ways

Each page and email is a JSON file in your own GitHub repository, synced both ways. When both sides changed, a person chooses.

Email

Outlook-safe output

Table-based HTML with a plain-text version and the Outlook layout fixes built in. The checks run before anything is handed to a sender.

Publishing

Hosted previews, or your host

One click publishes a microsite to sites.2nth.app for review, with history, restore and unpublish. The rendered HTML is also committed to a branch you can serve from anywhere.

Teams

Workspaces and roles

Owner, admin, editor and viewer roles, email invites that expire, and an audit log of who changed what. Sign-in is an emailed code, checked by Cloudflare Turnstile.

04 · The handover

What crosses from Webby to the CRM.

Design only. The CRM asks Webby for a mailer and gets back a package. It never sends Webby an address, a count or a send result. Anything the CRM can't fill per person is refused rather than sent blank, and every mailer must carry an unsubscribe link before it can become a draft.

  • Contacts and consent stay in the CRM, in Postgres in South Africa.
  • Sending stays in listmonk, opt-in list only, started by a person.
  • Outlook fixes survive: listmonk's template engine strips HTML comments, which is where Outlook's layout rules live, so the CRM carries them through intact.
  • Changes are flagged: edit a mailer after drafting and the CRM marks it "Changed since the draft".
GET /api/v1/docs/{id}/package subject November news for {contact.first_name} previewText Three builds from this month html <!DOCTYPE html> … 41 KB, table layout text Hi {contact.first_name}, … mergeFields {contact.first_name} {contact.unsubscribe_url} issues none In the CRM {contact.first_name} → {{ .Subscriber.FirstName }} {contact.unsubscribe_url} → {{ UnsubscribeURL . }} → draft campaign on the opt-in list

Illustrative and shortened.

05 · Your version

Keep your sender. Add the editor.

The interface is plain HTTPS and JSON, with an OpenAPI description, so Webby isn't tied to my CRM or to listmonk.

LayerAs builtAlso works with
Sendinglistmonk, opt-in onlyResend, Cloudflare Email, Mailchimp, Brevo or HubSpot, or download the HTML or a standard .eml file
Contacts2nth CRMAny CRM, event or registration system: it registers the fields it can fill, with sample values
DesignsJSON in a GitHub repoYour organisation's own repo, with private or shared template libraries
HostingCloudflare Workers, D1, KV and R2Your own Cloudflare account, under the MIT licence; published sites from any static host
NextThe editor and the APIAI models and MCP clients working through the same operations a person uses
Cloudflare WorkersD1R2HonoReactPuckTypeScriptGitHub ApplistmonkOpenAPI 3.1
Your version

Design in the open, send from what you own.

Webby is free to try at webby.2nth.app, and free for clients to run. Code access on request. If you're moving off HubSpot or Mailchimp, a stack audit maps where your contacts, consent and sending should live.