Begins with one developer. Indispensable for a team.
A solo developer can watch one agent. A team runs many — across many products — and that's where orchestration and observability stop being a nicety and become the job. Fragua is built so more than one person can share a workspace without stepping on each other.
Many people, many products, one workspace each.
The hard part of multi-agent work isn't running the agents — it's two people touching the same repository at the same time. Fragua serializes the dangerous parts and isolates the rest.
Authorization lives on the models as plain predicates — who can edit, delete, or drive a phase. No scattered permission checks.
A per-workspace lock serializes the git operations that can't safely overlap, so concurrent runs never corrupt the tree.
Each feature executes in its own git worktree on its own branch, so work on different features runs side by side.
While a phase is being drafted through its interview, only its creator can answer — two people don't fight over one conversation.
Execution runs are bounded per workspace, so a burst of starts queues cleanly instead of stampeding the host.
Spend rolls up per workspace, per account, and per month — the budget owner sees the whole picture, not one person's runs.
Context lives in the system, not in someone's head.
Every workspace accumulates a shared memory: the Knowledge Base you upload, the durable artifacts each phase produces, and the complete history of every run. When someone onboards, hands off, or leaves, the context the agents work from doesn't leave with them.
That's the difference between a team's tooling and a personal one. The plan, the references, the decisions, and the receipts are all in the workspace — readable by the next person and the next agent alike.
Your uploaded references — design docs, API contracts, house conventions.
Research, MVP plan, brand and technical guides, specs — each persisted and reusable.
Every agent run, with its cost and its audit trail, kept for the whole workspace.
Finer-grained team controls are coming.
A read-only viewer role and per-person cost and run attribution — who triggered which run, and what their share of the spend was — are on the way. We'd rather ship them honestly than claim them early. Today, roles are member and admin, and cost is attributed to the workspace and account.
Bring the team.
Fragua is in private beta. Tell us about the team and the products you're building.