Handoff-first orchestration
Bring your own AI coding tool. bbasata coordinates the team.
bbasata is the shared coordination layer for teams working with multiple AI coding assistants. Tasks, handoffs, agents and permissions live in one place — without imposing an editor or a provider.
No lock-in · Works with your CLI · Accounts free · 7-day trial · No card
Fullstack-developer hands off to QA-engineer and Code-reviewer in parallel; QA-engineer hands off to Content-engineer; Content-engineer hands off to Human Approval gate; failed verdicts return to rework.
The packet stays in your team's queue — anyone picks it up from their own tool, and the verdict returns to the shared board.
Coordinates work across opencode, Kilo, Claude Code, Antigravity, Devin and Goose
BYO AI
Use the tools your team already chose
Don't force everyone to work the same way. bbasata lets each member use their favorite AI CLI or editor while the team keeps a shared layer of tasks, permissions and handoffs.
- 01
Each member picks their tool
opencode, Kilo, Claude Code (+ Antigravity, Devin or Goose where available) or others via the MCP protocol. bbasata does not force the team onto one editor or provider.
- 02
The shared layer stays shared
Tasks, permissions and handoffs live in bbasata, not inside one vendor's session, model API or chat thread.
- 03
Ready for your team's tools
bbasata prepares a ready-to-use setup for opencode, Kilo, Claude Code, Antigravity, Devin and Goose, so each member starts from their preferred tool.
Handoffs
Continue the work from any AI
bbasata turns every task into a portable work packet: context, objective, relevant files and state. Any teammate can pick it up from their preferred tool.
- 01
A task becomes a packet
bbasata packages the task: what to do, which files matter, what was decided and what's missing — no context left in a chat thread.
- 02
It lands in the inbox
The packet waits in the team's handoff queue until a member takes it. Nothing is executed invisibly.
- 03
Anyone picks it up
From opencode, Kilo, Claude Code, Antigravity, Devin or Goose — the tool is your choice, the role (dev, QA, review) comes from the workflow.
- What to do
- Refactor the billing webhook to retry with exponential backoff.
- Which files matter
- billing service · billing tests
- What was decided
- Retry with exponential backoff, up to 5 attempts · Idempotency key derived from the event id
- What's missing
- The retry cap on the payment gateway is unverified — the vendor sandbox has no failure endpoint yet.
real packet · tool-agnostic · role comes from workflow, tool is yours
Governance
Control without slowing the team down
Define roles, permissions and shared rules so agents work inside clear limits. AI gains autonomy; the team keeps control.
- ROLES
Role-based access & specialized agents
Give each member and each AI role clear limits across your projects, so everyone works inside the same rules.
- PERMS
You decide how each agent acts
For each agent you decide: it can act on its own, it must ask for permission first, or it stays blocked. Org admins can adjust this at any time.
- AUDIT
Every action leaves a trace
A shared audit trail shows who did what, with which tool, under which permission — so the team always knows what happened.
Agile
AI connected to the real project flow
Plans, phases, sprints, boards and tasks live next to agent work. bbasata doesn't just generate code: it coordinates execution, review and close. From idea to sprint, from sprint to handoff, from handoff to close.
- PLANStrategic plan
- PHASEPhase
- SPRINTSprint
- BOARDBoard / tasks
- HANDOFFHandoff
- CLOSEReview & close
- ✓Visual editor — the workflow is an interactive graph you can adjust
- ✓State is preserved — a teammate resumes from the same packet after review
- ✓Human approval built in — nothing moves forward without review
Inside the product
Not a diagram — the actual product
The board, the workflow editor and the audit trail your team coordinates through — captured from the running product.
The shared board
Every task with its state — nothing moves forward without a visible handoff.
The visual workflow editor
The workflow is an interactive graph: roles, parallel verdicts and human gates you can adjust.
The audit trail
Who did what, with which tool, under which permission — recorded for the whole team.
Getting started
Get started in 2 minutes
Three commands to start coordinating the team.
Install
bbasata initOne command. Creates a config file for your team.
Connect
bbasata loginPaste your API key to link your team — sign in, done.
Sync agents
bbasata agents syncYour team's agents are ready to pick up work from the shared board.
No lock-in
Your tools can change. Your process doesn't.
If the team moves from opencode to Claude Code, or adopts a brand-new tool, bbasata keeps the work continuous.
- 01
Switch agents, keep the workflow
Move to the next tool without starting over. Tasks, handoffs and permissions stay in bbasata — they never lived in the editor.
- 02
Handoffs, not sessions
Work is a portable packet, not a chat thread. Move a task from opencode to Claude Code, or hand it to another dev, without losing context.
- 03
Your code stays on your machine
Your code stays on your machine. bbasata cloud coordinates only — execution happens in your environment; cloud only stores board, queue and audit.
Pricing
Simple, predictable plans
| StarterRecommended | Enterprise | |
|---|---|---|
| Price | €0/mo | Custom |
| Agents | 5 | 100 |
| Calls/month | 500 | 100,000 |
| Workflows | 1 | 25 |
| API keys | 1 | 50 |
| Team members | 2 | 100 |
| Organizations | 1 | Custom |
| Support | Community | Custom SLA |
| Get started free | Contact sales |
Billed annually you pay 10 months — 2 months free versus monthly. Switch the toggle to compare.
You can upgrade anytime — changes apply immediately. Downgrade at the end of your billing cycle.
FAQ
Questions & Answers
What is bbasata?
bbasata is the shared coordination layer for teams working with multiple AI coding assistants. It keeps tasks, handoffs, agents and permissions in one place, so each member can keep using their preferred tool — opencode, Kilo, Claude Code, Antigravity, Devin or Goose.
Does bbasata run my AI tools automatically?
No — there is no invisible execution. Work waits in the shared queue until a member picks it up explicitly from their preferred tool, and every step moves forward only through approval gates. If coordination itself stumbles, the system only retries the coordination — it never skips an approval.
Which clients are supported?
opencode, Kilo, Claude Code, Antigravity, Devin and Goose — plus other tools via the MCP protocol. bbasata prepares a ready-to-use setup for each, so your whole team can coordinate through the tools they already use.
Handoff-first orchestration
Bring your own AI coding tool. bbasata coordinates the team.
Accounts free · 7-day trial · No card · Your workflow stays yours