MuninEvery exchange your business has with a customer — support, CRM, content, follow-up — runs continuously on shared memory. You set which workflows run unattended, which escalate, and which wait for a person to approve.
Email, chat, SMS and voice land in the same place, against the same customer. The agent answers where they wrote, and the record behind it updates itself.
Your own address. Threads stay together, signatures are stripped, opens are counted.
See the channelA widget on your site. Answers straight away, escalates when it should.
See the channelTwo-way SMS from your own number, in the same thread as everything else.
See the channelCalls become text in the same thread, with a summary and a follow-up.
See the channel
The work that’s left.
The judgement, not the typing.
Every workflow is an MCP tool on one endpoint. Bring any model — Claude, ChatGPT, Cursor, your own — and shape it into whatever agent your business needs.
One Postgres schema, one identity model, an MIT licence. Your engineers can read all of it before you sign anything.
Munin does not automate a few tasks around the edges. Every exchange your business has with a customer — the answer, the record it updates, the follow-up it earns, the article that stops the question recurring — runs continuously against one shared memory. Four of them look like this.
These four are illustrations, not the boundary. Anything your team does across CRM, conversations, knowledge, content, and outreach composes the same way — you describe the job, the agents run it, and you decide where a person steps in.
Before it ships.
You have the final say.
Munin gives you more than one operating mode. Some workflows are autonomous. Some escalate to a teammate. Some create reviewable drafts for approval. The common thread is that access is scoped, actions are visible, and riskier AI work stays reviewable.
The agent gathers, drafts, and proposes. The human does the judgment. Edit a draft and the model learns the diff. Reject and the activity history records why.
winback-prospects-q2. Consent and compliance checks ran clean. Awaiting approval to schedule.Set up a chat widget, a CMS blog, and analytics in a single Lovable prompt. Lovable builds the frontend — Munin spins up the operations behind it.
One contact, one Tuesday. Every module wrote to the same record, so each step already knew what the step before it had learned.
No integration ran between those steps. There was nothing to integrate — it was one record the whole time.
Threll.ai runs the complete customer platform in production — the chat widget, email, voice, analytics, and the CMS behind their site, all on the same Munin every account gets.
Before, every question about a customer meant joining three systems by hand and hoping the email addresses matched. Now it’s one query. The agent answers from the whole record instead of whichever slice it happened to be pointed at.
Same code. Same MCP endpoint. Same Postgres schema. Pick the path that matches what your team can take on — switch any time, your data follows you.
Real OSS. The whole suite, running on your hardware, your cloud, your terms.
docker compose up — the whole stack on one hostReady in five minutes, EU-hosted, no card. The whole suite — for solo builders, small teams, and proofs-of-concept.
For teams running real customer work on Munin. Higher caps, priority support — metered overage instead of hard cliffs.
Same code, same protocol — you choose where it runs.
A single article that exercises every typed block the journal renderer supports — lead, prose, callouts, quotes, editorial lists, definitions, figures, stats, takeaways and more. Use it on dev to eyeball rendering after a change.
The medium bucket of the masthead type scale — 35 to 64 characters. One step down from the display size, which keeps a listicle-shaped headline at three lines instead of five.
The long bucket — the smallest step of the scale, with looser leading and text-wrap: pretty instead of balance. No display_title is set here, so the H1 falls back to this full title.
Seventy-seven characters in title, thirty in display_title. The masthead reads the short form; the browser tab, OG tags, and journal cards all keep the long one.
Stop running your customer operation.
Start supervising it.
Free tier, no card. Self-host instead if you would rather.