A story stays
yours to carry.
The local owner prototype keeps stories and their sources in an encrypted, portable .emma file. You choose the context an invited agent can access.
A companion with continuity
Keep the stories that matter.
Choose what comes with you.
“We planted the bulbs before the first frost, then marked the rows with little wooden spoons.”
Selected context, by your choiceEmma began as a family memory companion. Its next chapter connects carefully chosen context with the work people want to do.
The local owner prototype keeps stories and their sources in an encrypted, portable .emma file. You choose the context an invited agent can access.
Emma Enterprise explores how a customer’s dot could operate an existing app through bounded tools, owner approvals, and receipts.
Explore Emma EnterpriseWhere things stand
As of October 6, 2026. This public site introduces the product; it does not open a private vault or connect your dot.
A working local prototype supports memories, selected context, encrypted backups, and owner-controlled access. It is separate from this public page.
Private workspace, property, and experience create/edit, save, reload, and private-preview workflows have been verified.
Reusable app MCP access for actual Dots, complete CRUD, native cross-Dot wake-ups, and a hosted private-memory vault are not operational.
No. This is a public product introduction with fictional illustrations. It does not read a vault, authenticate an owner, or access a private workspace.
Your dot is the assistant you work with. The Enterprise proposal is to give that assistant a bounded way to use your app, with your permission and a result you can inspect.
No. The app remains the source of truth for its business records. Emma’s selected memory and task coordination are separate.
Not yet. There is no public connection or signup flow on this page. For an integration pilot, bring one concrete workflow to your existing conversation with the Emma team.
Give your customers
a new way into your app.