Pebercake gives every team one door to AI — in the browser, in Word and Outlook, in your own systems — with the counter, the till and the log that a serious business needs.
The same Pebercake — same memory, same rules, same log — wherever the work happens. No copy-paste into a chat window.
Pebercake reads the page you are on — CRM, case, mail — and crows when there is something new.
Draft, summarise and check documents against your own knowledge without leaving the file.
Reply drafts and case notes from the inbox — with masking on the way out.
Tables explained, decks drafted. Same assistant, same rules.
Your tools exposed over MCP with OAuth and a consent gate on every write.
REST and OpenAI-compatible endpoints behind bakesafe: keys, quotas, audit.
REST, MCP and OpenAI-compatible calls pass one gateway with keys, quotas, rate limits, reversible masking and a full audit log.
Baker is the document workshop: blocks, review, history as git, an AI coach. The mates are the small end-user apps — one job each, no training needed.
Every app writes to one memory: case index, documents, decisions. You navigate by object — the customer, the case, the contract — not by app.
Every part of Pebercake is named after the old bakery tales — the Rooster who reads the page, the Sparrow who carries the messages, the Baker's Wife who guards the door, Gretel who thinks. It is a way to make AI architecture explainable to everyone in the company, not just IT.
Pebercake is baked from Surdej — the Happy Mates starter. Fork it, add your flavour, and improvements flow back to everyone.
We run it in the EU. You get keys, dashboard and support. Live in a day.
Pebercake installs as modules in your own copy of Surdej. Full control, same release train.
Containers, documentation and an AI handover with slides. No connection to us, ever.
We put bakesafe in front of one app. You watch traffic, cost and masking in real time. Then we decide together how to run it.