Now in private beta

Let your users customize their own experience

Brimeo makes it safe: every change runs in an isolated sandbox, gets logged automatically, and can be undone — without ever exposing your source code.

Book a call See how it works

Brimeo is our dynamic-interface SDK, letting any user reconfigure vendor software in the agent-first era.

Editor

Point-and-describe editing

A chat composer and a generated-UI runtime that turn a plain-language request into a live interface change.

Control Room

Governed by default

A hash-chained audit log and policy gate sit in front of every mutation, high-impact or not.

Connect

Native MCP, both ways

Expose your product's Actions as MCP tools, or pull in external MCP servers as new Actions.

Automate

Durable, voice-ready

Standing automations and governed voice sessions run through the same sandboxed, audited path.

The Editor

Point at any screen, describe the change, and Brimeo rewrites the interface live — no source code ever exposed to the user.

            vendor-app
            components
            LoginButton.tsx
          
1import { useState } from "react";
2
3export function LoginButton() {
4  // agent-editable region
5}

📁checkout-flow⌄

Ask anything, @ to mention, / for actions

The Control Room

Every request runs inside a regulated environment — scoped permissions, full audit trail, and rollback on demand.

16MB sandbox memory ceiling, per execution

1,000ms hard timeout on every sandboxed run

12 subsystems, one SDK install

MCP native, both inbound and outbound

Built for regulated teams in the agent-first era

Brimeo is built for trust — whether you are an IT admin governing a large enterprise deployment, an ops lead customizing a vendor tool, or a builder shipping changes without engineering.

Enterprise IT admin

Regulated environment

Ops lead, no engineering

Forward-deployed builder

"No source code ever leaves our repo. Brimeo only ever calls the Actions we declared."

SaaS platform team

Vendor integrating brimeo-sdk

"Every agent action is in the audit log before it ever reaches our backend."

Compliance lead

Regulated finance ops

Does Brimeo need our source code?

No. You implement one interface that maps declared Actions to your existing backend — Brimeo never reads or stores your codebase.

What stops a customization from breaking on our next release?

Every overlay reconciles against your new Manifest through a three-way merge. It either merges cleanly or surfaces a typed conflict — it never silently drops a change.

Is this safe to run against a regulated product?

Every action passes through an isolated sandbox and a hash-chained audit log before it reaches your backend, with an approval gate in front of high-impact actions.