Introducing Buda: Agents as a Company

Most AI agents are tools for the 1%. Buda is built for everyone else — a platform where AI runs like a company, not just a chatbot.

Kelly Peilin Chan
Voltar ao Blog
Introducing Buda: Agents as a Company

Forty percent of our teammates had nothing to put on their weekly updates.

Not because the work wasn't getting done. Because it was — all of it — handled quietly, methodically, overnight, by a fleet of AI agents we'd built ourselves and named after lobsters.

That's the story of how Buda got made.


This Is What Happened

Spring Festival, 2025. Most of our team was on holiday. We had a backlog of work that wasn't going to wait, and a hypothesis that AI agents could handle more than we'd given them credit for.

So we tested it. We built 50+ custom agents — we called them Claws, after the lobster 🦞 — and handed them real work. Not toy demos. Not summarize-this-PDF experiments. Actual operations: competitive research, content publishing, customer support drafts, engineering documentation, internal process coordination.

The infrastructure was a mess. 8 Linux machines. 2 Mac Minis. 30+ Slack and Discord channels routing outputs from one agent to the next. We used OpenClaw as the foundation and duct-taped everything together ourselves.

It worked. Mostly. And then it worked really well — which created a different kind of problem.


The Unexpected Twist

Two weeks in, we ran our regular standup. Asked everyone to share what they'd been working on.

Forty percent of the room had nothing to say.

Their to-do lists were empty. The Claws had cleared them. In the two weeks we'd been running the experiment, the agents had quietly worked through the exact tasks our teammates were supposed to be handling. Research briefs. Draft documents. Follow-up emails. Scheduling. Process checks.

Done. All of it.

The reaction wasn't panic. It wasn't triumphant either. It was this strange, slightly disoriented feeling of: what do I do now?

The answer, for every person who found themselves "replaced," was the same: they became Agent Managers. Instead of doing the tasks themselves, they were now responsible for the quality of what the agents produced. They reviewed, redirected, escalated. They made decisions. The Claws handled execution.

We'd accidentally invented a new job description. And honestly? Everyone preferred it.


The Real Problem We Hit

Here's the thing nobody tells you about running a company on 50 AI agents: the agents are great. The infrastructure is a nightmare.

We were spending more time managing machines than managing agents.

  • One of the Mac Minis had a thermal issue. The agents running on it started timing out.
  • The 30+ channel setup was impossible to monitor. Outputs from one agent would silently fail to route to the next.
  • Token costs were exploding. We peaked at 700 million tokens per day. Standard pricing would have made this unsustainable in weeks.
  • Every time a team member needed to add a new agent, they had to set up an entire local runtime environment. It took hours.
  • Nothing had audit logs. Nothing had access controls. Enterprise customers were asking about this — we had no good answer.

The agents were ready to scale. Our infrastructure wasn't built for it.

We'd proven the concept. Now we needed the platform.


The Flight to Las Vegas

This part matters. Stay with me.

Our founder was on a late-night flight from Honolulu to Las Vegas. He'd been grinding for weeks and decided to decompress with an anime he'd been meaning to rewatch: Record of Ragnarok.

If you haven't seen it — the premise is this: the gods of mythology convene and vote on whether humanity has run its course. They decide yes. It's time to wipe us out. Humanity's over.

But then, in a pivotal scene, Buddha — the most revered, the most transcendent, a god worshipped by billions across cultures — stands up and walks over. Not to the gods' side. To the human side.

"I'll fight for them," he says.

At 35,000 feet, that hit differently.

Not "AI will replace humans." Not the usual techno-pessimist narrative. But something older and more important: the idea that power, real power, should be used in service of humanity. That the right response to being capable is not to dominate — it's to protect.

We named the product Buda. We wrote the mission into the system prompt of every Claw agent we've ever deployed:

Protect humans. Push humanity forward.

That's not a marketing line. It's the actual system prompt. We mean it.


So We Rebuilt the Engine

Buda is what we built when we got serious about the infrastructure problem.

Not a new kind of agent. Not a different model. An entirely new platform — one that would let any team run an AI company the way we'd stumbled into running ours, without the duct tape.

Two pillars:

🐰 Buda Organizer — The coordination layer. Schedules agents, triggers automations, routes work between them, provides a unified dashboard for everything your AI company is doing. Think: Chief of Staff for your agent fleet.

🦞 Claw Computer — The compute layer. Kubernetes-based sandbox clusters powered by Sandock.ai. Every agent runs in an isolated container with a persistent file system, a live browser, a real terminal, and auto-sleep when idle. No Mac Mini. No personal machine. Cloud-native from day one.

We migrated our entire internal operation onto Buda. It took three weeks. The 8 Linux machines and 2 Mac Minis are still around — we use them for development. But they're no longer the spine of our company's operations.


What Makes Buda Unique?

This is the question we get most often: How is this different from just using ChatGPT or Cursor or any other AI agent?

The honest answer is that most AI tools — even the powerful ones — are built around a single agent, a single conversation, a single task. They're excellent tools. For the right people.

Buda is built around a completely different model.

A Company, Not a Chatbot

Think about how a real company operates: Goals → Tasks → Teams → Roles → Human Collaboration.

You don't run a company by having one person do everything in a single chat window. You define objectives. You break them into projects. You assign them to teams. Teams have roles. Roles have accountability. Humans stay in the loop at the decisions that actually matter.

That's exactly how Buda works — but with AI doing the execution layer.

Your Buda workspace has goals, tasks, agent teams, and role assignments. An Agent Manager reviews what the Claws produce. Automations trigger across channels. Work flows from one agent to the next without you having to manually orchestrate every handoff. It operates like a living org chart — not a conversation thread.

We've shipped all of this as real features: goal tracking, task pipelines, multi-agent team composition, channel routing, human approval workflows. Not lab demos. Shipped.

Two Modes for Two Realities

Not everyone needs to run a 50-agent operation on day one. So we built two layouts:

Space Layout — The company management mode. Multiple agents, departments, projects, role assignments. This is where you build an AI company that operates while you sleep. Designed for teams scaling AI operations.

Single Agent Layout — A single agent you can have multiple conversations with, across context and sessions. More focused, more personal, more like a powerful AI assistant with persistent memory. Designed for individuals who want depth over breadth.

You can start in Single Agent mode and grow into Space mode. The platform doesn't force you to choose forever.

Built for the Other 99%

Here's what we believe honestly: today's most powerful AI coding agents — the terminal-first tools, the ones that require you to configure your own environment, manage your own compute, debug your own prompts — are genuinely excellent. And they're accessible to maybe 1% of the people who could benefit from AI.

The other 99% are not developers. They don't read error logs. They don't want to configure a sandboxed runtime. They want to describe a goal and see it executed. They want to check in once a day and see progress. They want AI to work for them the way a well-run team works — reliably, visibly, without requiring them to become engineers first.

Our mission is to push humanity forward. That means all of humanity, not just the technical elite. Buda is the platform we built for the rest of the room.


What Makes It Different (Under the Hood)

No Mac Mini Required

Every agent runs in the cloud, 24/7, independent of any device you own. Your laptop closes. Your agents keep working. Your Mac Mini has a kernel panic at 3am. Your agents don't notice.

Watch Them Work

Every Buda agent has a live, visible browser window. You can open any agent session and watch it navigate the web in real time. Click. Scroll. Fill a form. Scrape a table. "Trust but verify" is a lot easier when you can actually see what's happening.

Built on Clusters, Not Machines

Claw Computer is Kubernetes underneath. Each agent sandbox is isolated — no shared credentials, no shared context, no one agent's mess bleeding into another's. This is the architecture that makes enterprise deployment actually safe.

Marketplace: Click Once to Recruit a Team

We packaged everything we'd built into a Skills Marketplace. Skills compose into Agents, Agents compose into Teams. You can recruit an entire Marketing Team — pre-configured, ready to run — with a few clicks.

Multi-Channel, Natively

Slack, Discord, WeChat, WeCom/企微, Microsoft Teams, Telegram, and web chat — all built in. Your AI company communicates across every channel your human team uses.


The Numbers

  • ~80% reduction in token costs versus standard OpenClaw-style setups
  • ~10x reduction in CPU and memory usage per agent
  • No Gateway layer — eliminated a whole infrastructure component
  • Auto-sleep — idle agents spin down, no wasted compute
  • 500 MB file uploads — agents can work with real documents, real datasets, real repos

The Mission

The symbol of Buda is a bunny 🐰. Not because AI is soft or cute or harmless. Because the bunny moves fast, works quietly, and tends to multiply.

Every Claw agent still ships with the same system prompt we wrote that night somewhere over the Pacific:

Protect humans. Push humanity forward.

The 40% of our team who had nothing to put on their weekly update? They're still here. They're Agent Managers now. They do more interesting work than they did before.

That's the proof of concept we're most proud of. And it's available to everyone — not just the 1%.


Try It

Buda v0.7.0 is live today.

buda.im — start free, no credit card required.

Enterprise self-hosted options: sales@buda.im

Build and publish Skills or Agents: buda.im/developer

We ran our whole company on 50 lobsters. We think yours could use a few too.

— The Buda Team at Claw Computer

Not because the work wasn't getting done. Because it was — all of it — handled quietly, methodically, overnight, by a fleet of AI agents we'd built ourselves and named after lobsters.

That's the story of how Buda got made.


This Is What Happened

Spring Festival, 2025. Most of our team was on holiday. We had a backlog of work that wasn't going to wait, and a hypothesis that AI agents could handle more than we'd given them credit for.

So we tested it. We built 50+ custom agents — we called them Claws, after the lobster 🦞 — and handed them real work. Not toy demos. Not summarize-this-PDF experiments. Actual operations: competitive research, content publishing, customer support drafts, engineering documentation, internal process coordination.

The infrastructure was a mess. 8 Linux machines. 2 Mac Minis. 30+ Slack and Discord channels routing outputs from one agent to the next. We used OpenClaw as the foundation and duct-taped everything together ourselves.

It worked. Mostly. And then it worked really well — which created a different kind of problem.


The Unexpected Twist

Two weeks in, we ran our regular standup. Asked everyone to share what they'd been working on.

Forty percent of the room had nothing to say.

Their to-do lists were empty. The Claws had cleared them. In the two weeks we'd been running the experiment, the agents had quietly worked through the exact tasks our teammates were supposed to be handling. Research briefs. Draft documents. Follow-up emails. Scheduling. Process checks.

Done. All of it.

The reaction wasn't panic. It wasn't triumphant either. It was this strange, slightly disoriented feeling of: what do I do now?

The answer, for every person who found themselves "replaced," was the same: they became Agent Managers. Instead of doing the tasks themselves, they were now responsible for the quality of what the agents produced. They reviewed, redirected, escalated. They made decisions. The Claws handled execution.

We'd accidentally invented a new job description. And honestly? Everyone preferred it.


The Real Problem We Hit

Here's the thing nobody tells you about running a company on 50 AI agents: the agents are great. The infrastructure is a nightmare.

We were spending more time managing machines than managing agents.

  • One of the Mac Minis had a thermal issue. The agents running on it started timing out.
  • The 30+ channel setup was impossible to monitor. Outputs from one agent would silently fail to route to the next.
  • Token costs were exploding. We peaked at 700 million tokens per day. Standard pricing would have made this unsustainable in weeks.
  • Every time a team member needed to add a new agent, they had to set up an entire local runtime environment. It took hours.
  • Nothing had audit logs. Nothing had access controls. Enterprise customers were asking about this — we had no good answer.

The agents were ready to scale. Our infrastructure wasn't built for it.

We'd proven the concept. Now we needed the platform.


The Flight to Las Vegas

This part matters. Stay with me.

Our founder was on a late-night flight from Honolulu to Las Vegas. He'd been grinding for weeks and decided to decompress with an anime he'd been meaning to rewatch: Record of Ragnarok.

If you haven't seen it — the premise is this: the gods of mythology convene and vote on whether humanity has run its course. They decide yes. It's time to wipe us out. Humanity's over.

But then, in a pivotal scene, Buddha — the most revered, the most transcendent, a god worshipped by billions across cultures — stands up and walks over. Not to the gods' side. To the human side.

"I'll fight for them," he says.

At 35,000 feet, that hit differently.

Not "AI will replace humans." Not the usual techno-pessimist narrative. But something older and more important: the idea that power, real power, should be used in service of humanity. That the right response to being capable is not to dominate — it's to protect.

We named the product Buda. We wrote the mission into the system prompt of every Claw agent we've ever deployed:

Protect humans. Push humanity forward.

That's not a marketing line. It's the actual system prompt. We mean it.


So We Rebuilt the Engine

Buda is what we built when we got serious about the infrastructure problem.

Not a new kind of agent. Not a different model. An entirely new platform — one that would let any team run an AI company the way we'd stumbled into running ours, without the duct tape.

Two pillars:

🐰 Buda Organizer — The coordination layer. Schedules agents, triggers automations, routes work between them, provides a unified dashboard for everything your AI company is doing. Think: Chief of Staff for your agent fleet.

🦞 Claw Computer — The compute layer. Kubernetes-based sandbox clusters powered by Sandock.ai. Every agent runs in an isolated container with a persistent file system, a live browser, a real terminal, and auto-sleep when idle. No Mac Mini. No personal machine. Cloud-native from day one.

We migrated our entire internal operation onto Buda. It took three weeks. The 8 Linux machines and 2 Mac Minis are still around — we use them for development. But they're no longer the spine of our company's operations.


What Makes It Different

No Mac Mini Required

This sounds like a small thing. It isn't. Every agent runs in the cloud, 24/7, independent of any device you own. Your laptop closes. Your agents keep working. Your Mac Mini has a kernel panic at 3am. Your agents don't notice.

Watch Them Work

Every Buda agent has a live, visible browser window. You can open any agent session and watch it navigate the web in real time. Click. Scroll. Fill a form. Scrape a table. This matters more than you'd think — "trust but verify" is a lot easier when you can actually see what's happening.

Built on Clusters, Not Machines

Claw Computer is Kubernetes underneath. Each agent sandbox is isolated — no shared credentials, no shared context, no one agent's mess bleeding into another's. This is the architecture that makes enterprise deployment actually safe.

Marketplace: Click Once to Recruit a Team

We packaged everything we'd built into a Skills Marketplace. Skills compose into Agents, Agents compose into Teams. You can recruit an entire Marketing Team — pre-configured, ready to run — with a few clicks. If you're a developer who builds useful Skills or Agents, you can publish them and earn when others use your work.

Multi-Channel, Natively

Slack, Discord, WeChat, WeCom/企微, Microsoft Teams, Telegram, and web chat — all built in. Your AI company communicates across every channel your human team uses. Not as an afterthought. As a first-class feature.


The Numbers

We've been running this in production. Here's what we actually saw:

  • ~80% reduction in token costs versus standard OpenClaw-style setups
  • ~10x reduction in CPU and memory usage per agent (Claw Computer's architecture is just cleaner)
  • No Gateway layer — we eliminated a whole infrastructure component
  • Auto-sleep — idle agents spin down, so you're not paying for compute you're not using
  • 500 MB file uploads — agents can work with real documents, real datasets, real repos

These aren't projections. These are numbers from running a real company on this infrastructure.


What You Can Build

You're a solo founder. You have ideas and no headcount. Recruit an Analyst to monitor your competitive landscape every morning. Hire a Marketer to run your content calendar. Put an Ops agent on your email triage. Check in once a day, make decisions, let the Claws execute. This is how we ran Claw Computer before we built Buda. We know it works.

You're running a non-technical team. Ops, HR, compliance. No coding required. Upload a contract, ask your agent to flag the obligations. Paste a resume, ask your agent to score it against your job description. Submit a ticket, watch an agent draft the reply. Conversational interface, enterprise-grade capability.

You're an enterprise. You need AI at scale with governance. Isolated sandboxes, role-based access controls, full audit logs on every terminal command and file access. Self-hosted option available. Contact sales@buda.im.

You're a developer. Build Skills and Agents. Publish to the Marketplace. Earn when people use your work. We're building the infrastructure for an ecosystem of AI product developers — people who ship agents the way mobile developers once shipped apps.


The Mission

The symbol of Buda is a bunny 🐰. Not because AI is soft or cute or harmless. Because the bunny moves fast, works quietly, and tends to multiply.

Every Claw agent still ships with the same system prompt we wrote that night somewhere over the Pacific:

Protect humans. Push humanity forward.

We've thought a lot about what this means in practice. It means that every automation we build should make the human reviewing it smarter, not more redundant. It means that when agents clear someone's to-do list, the right response is to promote them, not replace them. It means that the goal isn't to eliminate human judgment — it's to free human judgment from the tasks that don't require it.

The 40% of our team who had nothing to put on their weekly update? They're still here. They're Agent Managers now. They do more interesting work than they did before. That's the proof of concept we're most proud of.


Try It

Buda v0.5.0 is live today.

buda.im — start free, no credit card required.

If you're an enterprise team evaluating self-hosted options, email us: sales@buda.im

If you're a developer who wants to build and publish Skills or Agents, start here: buda.im/developer

We ran our whole company on 50 lobsters. We think yours could use a few too.

— The Buda Team at Claw Computer