Busabase

Busabase is an open-source (MIT) database and workspace built for AI agents and the people who work alongside them. It keeps business records, documents, skills, and apps in one shared place so that what an agent produces stays as data your team can reuse, instead of disappearing into a chat window. The product calls itself the general system of record for AI agents, and it is aimed at teams and individuals who already run agents such as Claude Code, Codex, Cursor, or their own custom agent and want the output of that work to land somewhere durable. Busabase can run on your own machine as Busabase Desktop, on your own server through Docker, or in Busabase Cloud. The problem Busabase addresses is that agent work keeps evaporating. Teams already use AI, and the work gets done, but it scatters across personal chat windows and leaves when people do. The site contrasts a scenario without Busabase — Amy drafting a quote in ChatGPT, Ben cleaning a customer list in Claude, Chris finishing a data cleanup script in Cursor before leaving the company, Dana recording a meeting decision in Gemini — with a scenario where the same output lands in one team workspace as customers, quotes, meeting notes, an app, and a skill. The stated consequences of the scattered approach are that results stay in a chat log nobody finds again, every session starts from zero, and when someone leaves, their work goes too. Busabase's answer is to keep AI work in the company rather than in chat histories, so the next task can build on the previous one. Busabase organises work into Bases. The Data Base holds customers, projects, and inventory in tables with fixed columns, so every agent reads and writes the same fields rather than free-form text. The Knowledge Base is described as the team's shared memory: answers you can find, with a source, that someone checked. A record in Busabase carries its body, its sources, and its review history, which is what separates it from a pile of unstructured notes accumulating in different tools. Because the structure is fixed, an agent writing into a Data Base produces something a person can open tomorrow, and a person editing a record produces something the next agent can read. The Apps Base collects your internal tools, called AirApps, in one place and builds them on the same data, so every screen shows the latest version — the Busa CRM template, for example, presents pipeline, deals, and follow-ups from the same underlying records. The Skills Base lets you save a workflow once as a skill, and any agent can run it next time, which turns a single successful run into a repeatable capability. Playbooks are written-down descriptions of how your team does things; agents check them before every task and follow them instead of improvising. Layered together, these Bases turn isolated agent output into assets the whole workspace shares. Busabase does not ask teams to switch tools. You connect the agents you already use — Claude Code, Codex, Cursor, n8n, or your own agent — through Agent Skills, MCP, OpenAPI, or the CLI, and any agent that can call a REST API can work with it; the documentation suggests pasting the SKILL.md file and going. You can also talk to a connected agent right inside Busabase, or connect 40+ external agents over Agent Skills, MCP, and more, with Claude Code, Codex, and OpenClaw named as examples. Either way, they read and write the same workspace. 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. Rejected work never enters your canonical data, and every decision — approve, request changes, or reject — stays attached so the record remains explainable later. The mechanics are described in three steps. First, connect your agents: an agent like Claude Code, Codex, Cursor, n8n, or your own connects through Agent Skills, MCP, OpenAPI, or the CLI, then runs a task such as logging today's customer calls and updating the CRM. Second, every write is on the record, with the change carrying who made it, what changed, and a full history, and important writes held for human review. Third, reuse it next time: the Data Base, Knowledge Base, Apps Base, and Skills Base are read by the next agent, a teammate, or an AirApp, so nobody starts from zero. This loop — connect, record, reuse — is the product's core methodology, and it applies whether Busabase runs on a laptop, a company server, or in the cloud. The benefits follow from that loop. Agent output stops being ephemeral and becomes typed data, documents, skills, and apps that survive sessions and staff changes. Because every change keeps its source and its full history, teams can explain later what happened and why, and because review is built in, the writes that matter can wait for a person. Individuals get a private, local place where data stays in a folder on their computer, with no usage tracking and continued offline operation. Teams get one workspace where the rules agents follow, the data they touch, and the agents themselves all live together. And because every screen reads the same data, internal tools built as AirApps always show the latest version rather than a stale export. Use cases are grouped into eight kinds of work you can start keeping today. Customer support keeps Q&A and product facts, where agents draft the reply and a person approves it. Marketing holds CRM contacts, campaign records, social posts, and creative assets in one place. Content manages briefs, drafts, and published pieces moving through one pipeline. Team memory stores decisions, meeting notes, and context the next agent can read. Operations tracks projects, to-dos, and supplier details in one place. Research gathers market signals and monitored sources, verified and adding up over time. Product catalog keeps SKUs, specs, pricing, and relations searchable and managed in one place. Compliance covers access reviews, vendor checks, and a complete audit log. A worked example on the site shows a content calendar of scheduled social posts with visuals, platform, copy, and status, read from a Products base and written to a Content base. Deployment is a deliberate choice rather than a default. Busabase Desktop runs on your machine with data staying in a folder on your computer, no usage tracking, and offline operation. Self-hosting via a Docker image deploys the same engine inside your company network so data never has to leave it, and the project offers a security page for teams heading into a security review. Busabase Cloud is for teams that want to work together right away with nothing to install. Pricing follows: the open-source engine is free forever, and Cloud starts free with one space you own, three seats per space, 5,000 records per space, 1 GB of attachment storage, and one self-hosted connection online. Plus costs $10 per seat per month billed $120 per seat annually and adds three spaces you own, ten seats per space, 20 GB of attachment storage, and OpenAPI, webhooks, and MCP. Pro costs $20 per seat per month billed $240 per seat annually and adds unlimited spaces, unlimited seats, 100 GB of attachment storage, and priority support over WhatsApp, WeChat, or email. In summary, Busabase is an open-source, local-first database and workspace that gives AI agents somewhere to put their work. Data, docs, skills, playbooks, and apps share one structure with a full history behind every change, agents connect through the tools they already speak, and important writes can wait for a human. Start local for free, and add Cloud when the team is ready.