About Dataembed
Dataembed is a CRM you can rebuild. A CRM is a view on a database, and Dataembed is that view: your Postgres, an AI that can do anything you can, and views, layouts and plugins you rearrange by asking.
It exists because most CRMs make you choose between owning your data and having good tools on top of it. Here every customer record stays a row in your database, and the grid, the SQL console, Dataembed's own agent and any agent you bring all work on it through one API that checks permissions and logs who changed what.
What you get
- Your database — connect a Postgres and every table is browsable, editable and queryable in place, read-write by default, with schema changes behind their own grant; rows are never copied
- A database client — inline edits, a side panel that follows foreign keys, CSV import with a dry run, CSV and JSON export, a read-only SQL console, aggregates and charts, and typed schema changes that show their SQL first
- One agent — the side-panel copilot, AI fill over a column, web-search imports and plugin building run on one agent on Claude Managed Agents; your own agent gets the same tools over MCP by signing in or with a read, write or admin key
- Undo first — record edits and view, layout and plugin changes run at once and can be undone from the activity log; what can't be undone, such as a delete or a schema change, waits for a person's approval when an agent asks for it
- Your views, or everyone's — every view and page layout has an Everyone layer and a Just-me layer; ask the agent for a change and it applies live to yours
- Plugins — the core ships as plugins on the same API; plugins built inside the app are a UI spec, with a sandboxed frame as the escape hatch
Who makes it
Dataembed is built by Kaiyu Hsu, an independent software engineer. It is a small project, not a company with a sales team: questions and bug reports reach the person who wrote the code.