Studio
Studio overview
A guided starting point for projects, agents, teams, and tools makes the product approachable for people who want to build AI teams without wiring orchestration by hand.
Product dossier
ScaiCo
Create specialist agents, expert teams, and company-scale operating structures without programming the orchestration layer.
Shape blueprints in the studio, attach tools, set budgets, run public sessions, and let outside applications call the same team runtime through the public API. A2A and MCP coordinate specialist teams and tool access underneath the product surface.
No-programming startBlueprint-backed teamsPublic-session operationMCP-governed toolsBudget visibilityAPI reuse
What ScaiCo does
Easy setup, governed runtime, reusable sessions
Guided setup for agents and teams, public-session control, budget visibility, and an API layer that other applications can call.
Studio-guided start
Create projects, specialists, teams, and tool access without writing orchestration logic.
Public-session steering
Resume meetings, steer work, and export outcomes from a public operational surface.
Budget and API control
Keep spend visible and let other products call the same runtime through public endpoints.
Create the structure visually
Projects, agents, teams, and tool access are created in guided product surfaces instead of prompt glue or orchestration code.
Run public sessions with control
API-key users can choose a project or team, resume work, direct specialist agents, inspect nested work, and export the transcript.
Keep budgets concrete
Budget cards and cost views make spend limits and current usage visible inside the operating surface, not only in backend logs.
Product thesis
The easiest way into agentic teams should not require programming
ScaiCo helps operators build specialist agent teams, steer live sessions, and keep budgets visible — without assembling the orchestration layer themselves. The value is visible in how quickly people can shape and run the work.
Blueprints let teams reuse a working structure instead of re-describing the organization every time a new workflow begins.
Public-session operation means the runtime is not trapped behind admin setup screens. Users can enter the live system, direct work, and export the outcome.
Budgeting keeps orchestration usable at scale — spend is legible enough to govern.
Start in the studio
The getting-started flow makes the product approachable for people who want to build AI teams and company structures without becoming orchestration engineers.
Workflow
From blueprint to governed session
Shape the company structure, launch the team, steer the work, govern tools and budgets, then reuse the same runtime from other applications.
01
Create the workspace
Start from studio surfaces for projects, agents, teams, and tools so a non-programmer can model the operating structure without wiring orchestration code by hand.
02
Assemble specialist teams
Choose a team lead, add specialist roles, import or export blueprints, and shape whole company-like structures out of reusable expert units.
03
Run or resume the session
Use the public control center to select the project or team, start or resume a meeting, steer specialists, and keep the live session accessible beyond the admin studio.
04
Govern tools and spend
Attach MCP-governed tools to the right specialists and keep budgets visible, so capability assignment and cost exposure stay deliberate instead of hidden.
05
Reuse from other applications
Drive the same session lifecycle from the public API when another product needs ScaiCo teams, without embedding orchestration logic inside that external app.
Feature deep dive
Five surfaces that power the operating model
The visible operating surfaces and the governance layer beneath them — from guided setup to public API.
Guided setup
Blueprint-backed creation surfaces
ScaiCo works like a studio for composition. Concrete surfaces for projects, agents, teams, tools, and getting-started steps replace the need to assemble the organization in code.
- Projects, agents, teams, and tools are distinct setup surfaces.
- Team structures can be cloned, exported, and reused as blueprints.
- Guided flows make the product accessible to non-technical operators.
Live operations
Public control center for active sessions
The public control center goes beyond a private admin console. API-key users can enter the runtime, select context, continue work, and bring specialist teams into live sessions.
- Public-session entry is separate from the studio setup experience.
- Live work can be resumed instead of restarted from zero.
- Transcript export keeps the session outcome portable and reviewable.
Governed tools
MCP keeps capability access controlled
Tools are attached deliberately to the right agents and teams. Capability access stays governed rather than globally exposed.
- MCP servers are managed as first-class product entities.
- Tool access can stay role-specific instead of globally exposed.
- The governance layer supports usability rather than replacing it.
Budget visibility
Cost control built into the operating surface
Budgets and spend are part of the visible operating surface. Orchestration becomes governable when teams can set limits before runtime and inspect usage while sessions are active.
- Budget cards show limits, spend, and remaining headroom.
- Cost overview is exposed as a product surface, not an internal metric sink.
- Budget governance is a core capability, not an afterthought.
API reuse
External applications call the same team runtime
The public API lets another application create and use ScaiCo sessions directly. Orchestration stays centralized in ScaiCo while other products consume the result as a service.
- Public API docs make the integration surface inspectable.
- External systems can create sessions, send tasks, and read state.
- Reusable sessions without embedding orchestration logic in every consumer.
Product gallery
The operating surface in action
Screenshots from the live product — studio setup, team composition, and budget governance.
Teams
Team blueprint with budget context
Blueprint export, team composition, and budget surfaces appear together in the operating view — setup and governance in one place.
Budgets
Budget governance
Budget limits, spend, and remaining headroom are visible directly in the operating surface.
Product overview
Core capabilities, what's next, and where to explore
ScaiCo runs today's orchestration work and sets the course for local execution.
Core capabilities
- Studio surfaces for projects, agents, teams, and tools.
- Teams can be cloned, exported, and reused as blueprints.
- Public-session operation with resume, steering, and transcript export.
- Budget and cost views visible in the operating surface.
- Public API docs with an inspectable integration entry point.
What's next
- Satellite pairing.
- OpenClaw local runtime.
- Blueprint-controlled local tools.
- Local approvals and visibility.
Explore
- Open the public control center to start a session.
- View projects to see how workspaces and teams are organized.
- Read the public API docs to explore the integration layer.
Architecture and integration
The enabling stack beneath the product surface
A2A and MCP coordinate specialist teams and tool access underneath the operating surface. The public API extends that same model to external applications.
- Studio and managed workspace define the structure before runtime: projects, agents, teams, tools, and budget boundaries.
- A2A coordinates specialist agents within teams during active sessions.
- MCP keeps tool access explicit and governable for the right specialists.
- The public API exposes the session lifecycle so other applications can use ScaiCo without embedding orchestration logic.
Architecture overview
Blueprint hierarchy with governed tools
The architecture diagram shows how a project fans out into coordinated teams, specialist agents, and governed MCP tool access.
Next step
Use the entry point that matches how you want to start
Start from the public control center if you want to operate a session directly, open projects if you want to inspect the workspace layer, or read the public API docs if another application needs to call the ScaiCo runtime.