Hand your coding agent one prompt. It sets barua up end to end and can launch it, while barua writes every email in your voice. You don't build a thing.
Nothing to build and nothing to write. Your agent wires it and can launch it. barua writes every email.
Paste the prompt into Claude Code, Codex, Cursor, or whatever writes your code. It reads your repo and sends barua the facts your server knows: a signup, an order.
Welcome, nudges, win-back, receipts: proposed from your events, then written once in your voice and your brand.
Grant it a connection in Settings, and access to your DNS, and it confirms the brand, approves the plays, verifies your domain and turns sending on. Or keep any of those for yourself.
Each approved play starts for the people its rule matches and the consent check allows. Two things stay yours: accepting the terms, and confirming you have permission to email people.
The tag, optional. Add it and barua builds a masked profile of what each visitor did on your site (products viewed, searches, visits, the cart they left), the base for personalizing each email next, plus their time zone for the send window. Plays never need it.
Written once in your voice, filled in from what your server reported. Never from the pages someone looked at.
Once a play is approved, no model decides who gets an email or when. Each send records the rule revision and the event that started its play.
because created · rule v3 · consent yes · Thu 09:12Real renders and one yes per play, then it runs on its own. A changed word or rule waits for the same yes.
Quiet for 45 days · Approve once for the whole playLogo and accent color from your code, and the design from an email you forward. Sent from your own domain, as you. Receipts fall back to plain wording when your voice can't be written.
sends as post@northtrail.noA play runs only when its rule matches. Marketing email needs a recorded yes or the basis you attested, and a no always wins. Two marketing emails to one address are at least 20 hours apart.
Tue, opened the app and built nothing · nothing sentMarketing email waits for 09:00 to 11:00 in each person's time zone, unless you set another window, and for weekdays when you turn that on. If barua has no zone for someone it uses your workspace's, then UTC. Receipts go out within hours.
diego@… in Mexico City · Mon 09:31Links are tagged on your own URLs. Clicks come from the tag or the click beacon and purchases from your server's events, each credited to the latest touch for seven days. Opens aren't counted.
Fri · bought, credited heresigned_up is
required; activated, created, purchased and churned are declared if your
product has them; the order, trial and subscription events are simply sent.Plays run on events your own code sends when something becomes true. Deciding who gets an email makes no model call at all.
Your events, profiles, replays and pipeline runs all stay in London. Writing the words and delivering the mail cross to providers in the US; the privacy page lists every crossing.
Typing and personal text are masked in the browser before anything leaves the device, with the exceptions the privacy page lists. Replays expire after 30 days. The full data page →
Your agent can read the setup guide today. Tell us where to look.
Or write to chris@barua.ai. It's an inbox, and a person answers.