About

AI agents need the same rules as people.

Liaison is one system of record for a team's work and its agents' work: the same permissions, the same approvals, the same data, on a server the team controls.

Why Liaison exists

Agents can now read a support queue, draft the reply, issue the invoice and book the shipment. Most teams can't let them, for good reasons: in most tools an agent either sees everything or nothing, its actions leave no clear record of who allowed them, and the company's data ends up in someone else's cloud.

Liaison starts from the other end. An agent works for a person and gets that person's permissions, enforced by the database rather than by a prompt. Actions that matter wait for a human approval, and the request, the decision and the person who made it are kept. The data stays on the team's own server, and the team brings its own model key.

To make that work, the agent has to live where the work lives. So Liaison puts mail, tickets, knowledge, invoicing, shipping and the store in one workspace, and people and agents work on the same records.

How it is built

  • Self-hosted. One Docker image with Postgres, Redis, MeiliSearch and an S3-compatible object store, run with Docker Compose. Web app, plus desktop apps for macOS and Windows.
  • Permissions in Postgres. Row-level security isolates organisations and scopes what each person and agent can see. The app's runtime connection can't bypass it.
  • Approvals as a first-class step. Gated tools wait in an approvals tray, where a person can edit the request before approving it.
  • Modular. A kernel with apps on top. First-party apps (Shopify, invoicing, Boxtal shipping, Pennylane accounting and more) install through the same sandboxed path as anyone's app. MCP works in both directions.
  • Source-available. Under the Functional Source License 1.1 (FSL-1.1-ALv2): free to use, modify and self-host, including for internal commercial use, but not to offer as a competing product or service. Each release becomes Apache 2.0 two years after it ships.
Web, desktop, mobile and MCP clients connect over HTTPS, WebSocket and MCP to one app container (HTTP API, kernel, sandboxed apps and background workers), which uses PostgreSQL with row-level security, Redis, MeiliSearch and an S3-compatible object store.
One app container, four standard services, all on your server.

Where it stands

Liaison has run Embodme and Spaycial in production for months, and their teams' feedback shaped what shipped. Anyone can try it on the live demo, with a fictional company already running on it.

Business model

  • Self-hosting is free under the FSL. Customers pay their model provider directly.
  • Setup and support services: we deploy and configure Liaison for a company and support it after go-live. More on services.

Who is behind it

Mathieu Frohlich

Liaison is built by Mathieu Frohlich, in Paris. He has run Embodme for seven years, mostly in music tech, and alongside it has worked on B2B projects with large French industrial companies. The products he has built include Norand and Fine Line, and more recently he has done AI consultancy work.

Liaison started out of necessity. He had to find a way to run Embodme with four people; it wasn't really a choice. Then he did the same for Spaycial, a fintech he advises.

Contact

Customers, partners, press and investors: mathieu@liaison.sh.