Brimeo is a dynamic-interface SDK that lets vendors embed a chat-driven editor and AI-generated UI runtime directly into their software, enabling end users to reconfigure product interfaces using plain-language requests. The platform includes a governed Control Room with hash-chained audit logging, policy gates, and sandboxed execution, along with native MCP support for exposing or consuming tools. It integrates via a single SDK with a 16MB sandbox memory ceiling and 1,000ms hard timeout per execution, requiring no access to the vendor's source code.
Funding
Funding not disclosed
Founders
Product
Problem
Enterprise software vendors struggle to let end users customize their products without risking breakage, security vulnerabilities, or compliance violations. Most customization options require deep technical expertise or direct code access, while generative-AI interface changes can silently break on release and bypass governance controls.
Solution
Brimeo is a dynamic-interface SDK that embeds a chat composer and generated-UI runtime into any vendor software, allowing any user to describe an interface change in plain language and have it applied live. The platform abstracts declared Actions behind a single interface that maps to existing backends, with every mutation passing through an isolated sandbox, a hash-chained audit log, and an approval gate for high-impact changes. Brimeo's native MCP support works in both directions: it exposes a product's Actions as MCP tools and can pull in external MCP servers as new Actions. Overlays are reconciled against updated Manifests via a three-way merge, resolving conflicts cleanly without ever silently dropping a change.
Target Audience
Brimeo's primary customers are software product teams at B2B vendors, particularly those in regulated industries, who need to offer end-user customization—including voice-driven workflows—while maintaining strict governance and release safety.
Features
- Point-and-describe editing via a chat composer and generated-UI runtime that turns plain-language requests into live interface changes
- Governed Control Room with hash-chained audit logging and policy gates enforced on every mutation
- Native bidirectional MCP support for exposing Actions as tools or ingesting external MCP servers
- Durable, voice-ready automation that runs through the same sandboxed, audited execution path as manual changes
- Sandbox execution with a 16MB memory ceiling and a 1,000ms hard timeout per run
- Single SDK install covering 12 subsystems, implemented against declared Actions without ever reading or storing the vendor's source code
- Three-way merge reconciliation that either merges cleanly against new Manifests or surfaces typed conflicts