Busabase

Busabase is an open-source (MIT) database and workspace for AI agents, described in its own words as the general system of record for AI agents. It gives people and AI agents one shared base where business records, docs, skills, and apps live in the same place, so the next task can build on whatever the previous one produced. Instead of letting agent output sit in a chat window, Busabase keeps it as data, docs, skills, and apps that a team can reuse. It is aimed at teams that already work with agents such as Claude Code, Codex, Cursor, Hermes, OpenClaw, WorkBuddy, and Buda AI, and it can be run on your own machine, self-hosted inside your network, or used through Busabase Cloud. The problem Busabase addresses is that agent work keeps evaporating. A team already uses AI and the work does get done, but it scatters across personal chat windows: one person drafts a quote in ChatGPT, another cleans up a customer list in Claude, a third finishes a data cleanup script in Cursor, and someone else records a pricing decision in Gemini. The site states the consequences plainly: results stay in a chat log nobody finds again, every session starts from zero, and when someone leaves the company, their work goes too. Busabase takes the opposite position: the work lands in one workspace and stays after people leave, so the next agent reads what the last one wrote and the work stays with the company. Busabase organizes that shared work into bases. The Data Base holds customers, projects, and inventory in tables with fixed columns, and because the columns are typed, every agent reads and writes the same fields rather than inventing its own shape for the data. The Knowledge Base is described as the team's shared memory: answers you can find, with a source, that someone checked. A record there carries its body, its sources, and its review history, so a fact can be traced back to where it came from and to whoever verified it. Together these two bases give agents a stable place to read from and write to, and give people a place to check the result. Three more bases extend the same idea. The Apps Base holds internal tools, called AirApps, built on the same data, so every screen shows the latest version — the site shows Busa CRM, a pipeline with deals and follow-ups that reads the same records. The Skills Base lets you save a workflow once as a skill, and any agent can run it next time. Playbooks are where a team writes down how it does things: agents check the playbook before every task and follow it instead of improvising. The site's summary of the workspace is Data, Knowledge, Apps, Skills, Playbooks, and External Agents, all in one place for people and agents. Agents connect to Busabase from wherever they already run. You can talk to a connected agent right inside Busabase, or connect 40+ external agents over Agent Skills, MCP, and more — Claude Code, Codex, and OpenClaw are named. Either way, those agents read and write the same workspace. The connection options listed are Agent Skills, MCP, OpenAPI, and the CLI, and the FAQ broadens this to any agent that can call a REST API, naming Claude Code, Codex, Gemini CLI, n8n, Zapier, LangChain, or your own agent; for that route the instruction is to paste the SKILL.md and go. Because the same structured data sits underneath, an agent does not have to be told the shape of the business each time it starts. The workflow Busabase describes has three steps. First, connect your agents: nothing to switch, your agents keep working the way they do today and simply write here. Second, every write is on the record: each change carries who made it, what changed, and a full history, and for the writes that matter you can hold the change for a person to review. Third, reuse it next time: the next agent, a teammate, or an AirApp reads the same data, so nobody starts from zero. Underneath, Busabase is open source under the MIT license, and the same engine runs on your laptop, on your own server, or in Busabase Cloud. Busabase Desktop keeps data in a folder on your computer with no usage tracking and keeps working offline; the Docker image is deployed inside your company network so data never has to leave it; Cloud needs nothing installed. The benefits the site claims follow from that structure. Work that would otherwise sit in personal chat windows lands in tables, docs, and apps you can open tomorrow, and it stays with the company after people leave. Knowledge comes with a source that someone checked, rather than as an unsourced answer. Every change keeps its history, so the record remains explainable later — approve, request changes, and reject decisions all stay attached, and rejected work never enters the canonical data. And because the same data feeds agents, people, and internal apps, a new session does not begin from nothing. For teams with a security review coming up, Busabase points to its self-hosting documentation about keeping data inside your network. The website lists eight kinds of work you can start keeping today. Customer support stores Q&A and product facts so agents draft the reply and a person approves it. Marketing keeps CRM contacts, campaign records, social posts, and creative assets in one place. Content moves briefs, drafts, and published pieces through a single pipeline. Team memory captures decisions, meeting notes, and context the next agent can read. Operations tracks projects, to-dos, and supplier details. Research collects market signals and monitored sources, verified and adding up over time. Product catalog holds SKUs, specs, pricing, and relations, searchable and managed in one place. Compliance covers access reviews, vendor checks, and a complete audit log. A demo on the site shows a content board where scheduled posts carry visual, platform, copy, scheduled status, and read-from relations, with the price pulled from the Products base. Busabase is built for teams and individuals who want agent output to accumulate somewhere shared. Named agent integrations are Claude Code, Codex, Cursor, Hermes, OpenClaw, WorkBuddy, and Buda AI, with n8n, Zapier, LangChain, and Gemini CLI mentioned in the FAQ, and connection surfaces including Agent Skills, MCP, OpenAPI, webhooks, a CLI, and REST APIs. Pricing has three tiers. Free costs $0 for one person keeping what their agents produce, with 1 space you own, 3 seats per space, 5,000 records per space, 1 GB of attachment storage, and 1 self-hosted connection online. Plus is $10 per seat per month, billed $120 per seat annually, with 3 spaces you own, 10 seats per space, 20 GB of attachment storage, and OpenAPI, webhooks, and MCP. Pro is $20 per seat per month, billed $240 per seat annually, with unlimited spaces you own, unlimited seats, 100 GB of attachment storage, and priority support over WhatsApp, WeChat, or email. The open source engine is free forever, and Cloud starts free and grows per seat. Taken together, Busabase's value proposition is simple: give your agents a workspace worth building in. The work they produce becomes typed data, sourced docs, saved skills, and internal apps that the next agent, the next teammate, or an AirApp can read; every change keeps its source and its full history; and sensitive work can stay on your machine, on your own server, or in Busabase Cloud. You can start local for free and add Cloud when your team is ready.