Dataembed

The CRM you can rebuild. Your Postgres, agent, views and plugins.

A CRM is a view on a database. Every table in your Postgres is browsable and editable in place, an agent can do anything you can (or bring your own over MCP), and views, layouts and plugins change when you ask, for you or for everyone.

A CRM on your database, not a copy of it.

  • Tools any member's agent can call, in the app or over MCP

    46

  • Plugins the product is built from, on the same API yours get

    12

  • Rows copied out of your Postgres: values live only in its columns

    0

A database client, an agent and a view layer. Whatever a person can do, an agent can too.

Every table, on connect Read-write by default

Connect a Postgres over verified TLS and every table opens as an object, read-write by default. Values stay real columns: edit cells inline, follow foreign keys in a side panel, import CSV after a dry run, export CSV or JSON.

Query it, chart it, change it SQL shown before it runs

A read-only SQL console, typed aggregates (count, sum, group by) and charts built on them. Schema changes are typed operations, like adding a column or creating a table, that show their SQL before they run.

One agent for every AI job On the model you pick

The side-panel copilot, AI fill over a column, imports found on the web and plugin building all run on one agent, on the model your workspace picks, with web search, web fetch and a sandbox for code.

Change it by asking. Undo it, or keep it to yourself.

Ask the agent or click it yourself: changes land at once, for you or for everyone, in one activity log under whoever made them.

  • Undo first

    Record edits and view, layout and plugin changes run at once and show Undo, whoever makes them. When an agent asks for what can't be undone, like a delete or a schema change, it waits for a person's approval.

  • Everyone, or just me

    Every view and page layout has an Everyone layer and a Just-me layer. Your tweaks save to Just me and Save for everyone promotes them. Ask the agent for a change and it lands in Just me, live.

  • Plugins all the way down

    The core ships as plugins on the same API. Plugins built inside Dataembed are a UI spec rendered with the app's own components, with a sandboxed frame as the escape hatch, and no server code.

How it works. Connect, shape, enrich, operate.

Connect your Postgres and every table is browsable at once. Dataembed keeps your views, layouts, plugins and an activity log, never a copy of your rows.

The grid, the copilot, MCP clients and the REST API all call one record service, which reads and writes your Postgres and runs plugins.
  1. 01

    Connect

  2. 02

    Shape

    Views, layouts and plugins, for you or for everyone. Ask the agent to change them.

  3. 03

    Enrich

    AI fill and imports from the web run as jobs you can watch and cancel.

  4. 04

    Operate

    Work in the grid or the SQL console, ask the copilot, or point your agent at /api/mcp.

Bring your own agent. It gets the same tools as ours.

Everything you can do in the app is a tool, built from the API contract. Sign your agent in, or give it a read, write or admin key. What can't be undone waits for a person's approval, whichever agent asks, and every change lands in the activity log under the agent's name.

claude mcp add --transport http dataembed https://<your-dataembed>/api/mcp

> Which deals closing this month have no next step?

● dataembed - records_list (object: deals)

● dataembed - records_update (object: deals, recordId: 18)

Two deals had no next step; I added one to Globex renewal.

46 tools for every member's agent

  • activity_comment
  • activity_list
  • activity_undo
  • ai_models
  • approvals_get
  • approvals_list
  • attributes_reorder
  • attributes_update
  • connected_apps_list
  • connected_apps_revoke
  • data_sources_get
  • data_sources_list
  • jobs_cancel
  • jobs_get
  • jobs_list
  • layouts_get
  • layouts_update
  • objects_get
  • objects_list
  • objects_reorder
  • objects_update
  • plugins_create
  • plugins_get
  • plugins_list
  • plugins_list_actions
  • plugins_manifest_schema
  • plugins_reset
  • plugins_run_action
  • plugins_update
  • records_aggregate
  • records_create
  • records_delete
  • records_get
  • records_import
  • records_list
  • records_related
  • records_search
  • records_update
  • records_update_many
  • schema_preview
  • sql_query
  • views_update
  • workspace_describe
  • workspace_get
  • workspace_leave
  • workspace_members
Connect an agentThe REST API