A New Chapter for Bika, and a Separate Path for Buda

For a long time, Bika was never just a product name to us.

It carried many of our beliefs about the future of work software, and it also carried a very real chapter of our company story.

We wanted software to do more than record work.
We wanted automation to do more than connect steps.
We wanted AI to do more than chat.

That is why this post is not easy to write.

Today we are making a difficult announcement:

First, Bika is not disappearing, but it is entering limited maintenance.

Second, Buda is the new product direction we are investing in, but Buda and Bika are completely independent products. Buda is not a Bika rebrand, not a Bika upgrade, not a new Bika plan, and not an extension of any Bika.ai or AITable.ai LTD benefit.

This is not a product migration announcement.

It is not a plan-name change announcement.

It is an explanation of Bika's next stage, and why Buda will move forward on a separate product path.

A difficult decision

We need to state the product boundary at the beginning.

Bika and Buda are completely independent products. They have different functionality, use cases, product architecture, data models, billing systems, and service boundaries.

Bika is a work system organized around spreadsheets and databases, automation, dashboards, docs, agents, and template packages.

Buda is a separate product designed around cloud-based agent runtime, Browser, Terminal, Drive, Git, cloud sandboxes, and long-running task execution.

This means:

• Buda is not a renamed Bika.ai
• Buda is not an upgraded Bika.ai
• Buda is not a new Bika.ai plan
• Buda is not a plan-name change for AITable.ai or Bika.ai AppSumo LTD
• Buda is not automatically included in any AITable.ai or Bika.ai LTD benefit
• Bika.ai data, automations, templates, agents, or workspace content do not automatically migrate to Buda

We did learn a lot from building Bika over time. But product learnings do not create continuity of product rights, account plans, or data structures.

So if you are an existing Bika.ai or AITable.ai user, especially an LTD user, please understand Buda as a new product built by the same team, but completely independent from Bika.ai and AITable.ai.

What Bika taught us

Bika was not a meaningless attempt.

On the contrary, it helped us go deep on many important questions and understand the boundaries of a complex work system.

While building Bika, we became increasingly certain about several things.

1. Complex work can be integrated into one powerful system

Bika was an ambitious product.

It did not try to solve one tiny workflow. It tried to bring multiple layers of work into one integrated system:

• spreadsheet / database
• agent
• docs
• automation
• dashboard
• template package

Our belief was simple: many difficult business problems cannot be solved by a single isolated tool.

Real work usually spans:

• data structures
• workflows
• documents
• automation
• AI reasoning and generation

So Bika tried to merge them into one template package, so users would not just get separate features. They would get a full working solution.

We still believe that instinct was right.

And to be direct: Bika is powerful.

If you really go deep into it, it can solve complicated work problems that many traditional SaaS products cannot hold together in one place.

But that is also where the problem began.

2. Bika's power also created its own complexity

Once you merge spreadsheets, agents, docs, and automation into one system, and then wrap that into reusable template packages, you gain a lot of capability.

But you also create a very real cost:

the interaction model becomes more complex.

A new user is no longer learning one product. They are trying to understand an entire work system.

That creates real friction:

• onboarding becomes harder
• the mental model becomes heavier
• the product becomes less immediately intuitive
• the philosophy of the product loses some of its original charm

This was the tradeoff we kept feeling inside Bika.

The capability was real.

But the entry point was not simple.

And once a product starts feeling like "a very complete and very powerful system that needs to be learned," rather than "an exciting and clear new way to work," something important gets diluted.

3. The deeper limitation was in the agent engine itself

There was also a more fundamental issue underneath the product surface.

Bika's agent layer was still largely built around API orchestration.

That works for many useful workflows. It is enough to build a lot of valuable features.

But if you really want an agent to behave more like a long-running employee than a triggered function, you start to hit a wall.

A real agent cannot just be a chain of API calls scheduled from the outside.

It needs its own working environment.

It needs:

• its own independent drive
• persistent context
• its own file system
• isolation
• a long-running sandbox
• a runtime that can actually execute real tasks

Bika was not designed around that underlying assumption.

It could connect many capabilities, but it was not built from day one around the principle that an agent should own a persistent place to work.

More specifically, Bika did not treat an agent's independent sandbox drive as a first principle.

Over time, we came to believe this was not a nice-to-have.

It was foundational.

Without an independent workspace, an isolated sandbox, and a persistent drive where files, context, and execution traces can accumulate over time, an agent feels less like a real worker and more like a repeatedly invoked capability.

4. We do not want to keep expanding Bika into a heavier system

As Bika evolved, it became clear that if we kept putting every new product direction into Bika, the product would become heavier and heavier.

That would not necessarily be better for existing users.

For users who already understand Bika, stability, availability, and reliability are more important than continuously adding large new directions.

So we decided that Bika will enter limited maintenance. We will continue to prioritize basic availability, stability, security, and necessary operational maintenance, but Bika will no longer be our main direction for expanding new core features.

That was not easy to accept emotionally.

Once you have already spent years building something, you naturally keep asking:

• can we just add one more capability?
• can we improve the onboarding one more time?
• can we finish one more module?
• can we postpone admitting that the resource focus has changed?

We asked ourselves those questions for a long time.

Why Buda needs a separate path

Put simply: continuing to put every new product direction into Bika was no longer the most honest choice.

Not because Bika had no value.

But because the direction behind Buda requires a different product boundary, technical architecture, and commercial system.

That separate path is Buda.

If we had to summarize the difference in one line:

• Bika is a work system that integrates spreadsheets, databases, docs, automation, dashboards, agents, and template packages
• Buda is an independent product designed around cloud-based agent runtime, sandboxes, Drive, Browser, Terminal, Git, and long-running task execution

This is not a simple brand upgrade.

It is not Bika renamed as Buda.

It is not a migration of Bika LTD users into another plan.

It is an independent product line.

What Buda is

Buda is a completely independent new product.

It does not start from helping users configure workflows inside a spreadsheet / database work system. It starts from helping agents execute tasks inside cloud environments.

Buda emphasizes:

• multi-agent collaboration instead of a single assistant
• persistent workspaces instead of disposable sessions
• real execution environments like Browser, Terminal, Drive, and Git
• team-level orchestration instead of personal experimentation
• infrastructure designed for long-running, isolated, manageable agent work

More concretely, Buda is different because:

• agents run inside a cloud sandbox
• each agent has its own independent Drive
• workspaces are isolated, so agent contexts do not bleed into each other
• agents can operate in real execution environments instead of only returning text
• the system is built around stronger Coding Agents and Agent Skills

These capabilities are not the same as Bika's functionality, data structure, or use cases.

So we need to say this again: Buda is not a replacement plan for Bika, not a new name for Bika, and not Bika's natural upgrade path.

What this means for Bika users

We do not want to be vague about it.

From this point forward:

• Bika is entering limited maintenance
• we will prioritize basic availability, stability, security, and necessary operational maintenance
• Bika will no longer be the main direction for new core feature expansion
• Buda will move forward as a separate product path

This does not mean Bika disappears tomorrow.

It does not mean existing users are suddenly cut off.

Existing Bika users can continue using Bika.

If you have a Bika.ai LTD benefit, that LTD benefit continues to apply to Bika.ai.

If you have an AITable.ai LTD benefit, that LTD benefit continues to apply to AITable.ai.

If you previously received a Bika.ai benefit from AITable.ai, that benefit continues to apply to Bika.ai.

But those benefits do not automatically extend to Buda.

For LTD, AppSumo, and AITable.ai users

Will existing Bika.ai LTD users receive Buda?

No.

Buda is an independent product and is not included in Bika.ai LTD, AITable.ai LTD, or any previously granted Bika.ai benefit.

Will Bika.ai Tier 4 or AITable.ai AppSumo Tier 5 map to Buda?

No.

Because Buda is not a renamed plan or upgraded version of Bika.ai or AITable.ai, there is no mapping of seats, credits, storage, agents, usage limits, or plan level.

Do AppSumo future plan updates or plan-name change terms apply to Buda?

No.

Those terms apply to the specific product and plan a user purchased or received. Buda is an independent product, not a plan-name change for Bika.ai or AITable.ai.

Can Bika.ai users migrate to Buda?

There is currently no migration path.

Bika and Buda have different functionality, use cases, underlying architecture, and data models. Bika data, automations, templates, agents, or workspace content cannot be directly migrated into a Buda workspace.

Will Bika.ai and AITable.ai continue to be maintained?

Yes.

Bika.ai and AITable.ai will continue to be maintained to support basic availability, stability, security, and necessary operational performance.

But Bika.ai will no longer be the main direction for new core feature expansion.

Is there a refund, credit, grandfathered plan, or Buda conversion option?

No.

Existing LTD benefits remain attached to the original product the user purchased or received. Buda is an independent product and is not an automatic extension of Bika.ai or AITable.ai LTD benefits.

Why we wanted to say this publicly

We do not want users to guess what happened through vague copy.

If the resource direction has changed, we should explain why.

If Buda is an independent product, we should clearly explain the boundary between Buda and Bika.

Users deserve that honesty.

And frankly, we needed to write this for ourselves too.

This is not just a product introduction.

It is a checkpoint.

It is our attempt to:

• summarize the past honestly
• explain today's tradeoffs clearly
• clarify the boundaries of existing user benefits
• explain why Buda is moving forward as a separate product path

This post is not about making Bika look worse so Buda can look better.

If anything, the opposite is true.

Bika mattered enough that we felt we owed it a real explanation.

If this resonates, come look at Buda

If you followed Bika all the way here, thank you.

Your feedback, your criticism, and the ways you actually used the product have all been important to how we think about products.

And if you care about these questions:

• can AI actually do work for a team?
• can agents become more than demos?
• can future software include working environments built specifically for AI agents?

then we genuinely invite you to take a look at Buda.

Visit Buda

But please understand clearly: Buda is an independent product and is not included in Bika.ai, AITable.ai, or AppSumo LTD benefits.

Bika will continue to be maintained.

And Buda will move forward as a separate product path.

• HR Workflow Automation: Definition, Examples, and Implementation
• Top 11 Low‑Code AI Workflow Automation Tools for 2026
• How Is AI Different from Automation? Key Features Compared
• Sales AI Workflow Automation: A Practical Guide From Lead to Close
• What Are Agentic Workflows? How AI Agents Power Smarter Automation