Busabase

Hey Product Hunt — Kelly here.

We kept seeing this with customers: a new project or a different agent often meant rebuilding context and instructions from scratch. Business users were juggling local files and agent setups, sometimes having to learn tools like Git just to keep things organized.

We believe agents should be stateless, with company knowledge and work kept in a shared base. Business users should be able to share that context across agents without becoming AI experts.

That's why we built Busabase — The Base for Agents — a shared workspace for data, docs, skills, and apps that people can see and manage.

Connect agents like Claude Code, Grok Bot, Muse, OpenClaw, Manus, Hermes, Buda or Codex via MCP, OpenAPI, or CLI. You decide what each agent can read or change, and which updates need review. You can also see what changed and who changed it.

With your agents and tools connected, you can automate workflows like:

• Software development — agents turn support feedback into tasks, write and test the code, deploy updates, and use new feedback to start the next cycle.
• SEO — agents monitor traffic and search trends, use the results to improve the content plan, write the next article in a shared CMS, and repeat.
• CRM — agents use product knowledge and shared business data to find relevant prospects, reach out, and follow up, keeping customer records, visit notes, and tasks up to date.

One customer keeps its company materials and project updates in Busabase. Now a manager can ask an agent for the latest status instead of going from teammate to teammate.

Try it with one project: add its updates and instructions, connect an agent, and ask, “What changed this week?”

Busabase is open source. You can self-host it, use Personal Desktop, or get started with Cloud.

If your team uses several agents, I'd love your feedback: what would Busabase need to handle for you to use it every day?

Congrats on Launch

Do Shared Playbooks hold both Skills and custom prompts? How would a teammate reuse the same working instructions with another supported agent?

Hey Product Hunt! 👋 I’m another maker on the Busabase team.

Kelly shared why we built Busabase. I’d like to highlight a few features that help teams put it into practice.

For us, sharing information is only part of the job. Teams also need to preserve how they work, understand what people and agents contributed, and turn accumulated knowledge into something useful day to day.

Here are four features I’m especially excited about:Shared Playbooks: Give your team’s Skills, procedures, coding conventions, and custom prompts a home in one browsable catalog. Connected agents can consult the relevant instructions, and teammates can copy saved prompts for their next task. A useful method developed by one person becomes something the team can reuse.Team Insights: See contributions recorded in Busabase Cloud, including changes, proposals, reviews, and activity trends. Owners and admins can view member contributions and their human and agent sources, helping them understand how shared work is being maintained.Instant AirApps: Ask an agent to turn workspace data into a dashboard, briefing, or internal business app. It runs directly inside Busabase and stays connected to the underlying records.Agent-ready Templates: Start with Bases, Docs, AirApps, sample data, prompts, and instructions packaged together, then adapt that setup to your team’s workflow.Which working method would you put into a shared Playbook first—a coding convention, a content process, or something else? I’d love to hear your examples.

honestly for dev teams I'd still keep that context in git, every coding agent already reads the repo. from my experience building Voiden that works well. is Busabase mostly for the business side, or do you see engineering teams moving it out of the repo too?

@seey @mrkelly Curious how this compares with existing databases and agent memory solutions ?

恭喜上线！我真的很喜欢你们所有人之间的协作，也很喜欢你们每个人都分享了做这个产品的理由。我觉得对于那些和自由职业者或承包商合作的企业来说，这是一个非常令人兴奋的工具。根据经验，我知道要把对的信息分享给对的人可能非常困难。