CALLIOPE AI · TECH SHEET · DWG CAL-SURF-001-B

Build STAGE 1 OF 5 · THE AI SURFACE

SHT B The build machine · exploded view DIMETRIC 2:1 · PARTS SEPARATED
the artifactships with its manifestthe spawnera pod per tool, per usertool benchesIDE, notebooks, SQL, chatthe hubsessions, auth, spawningbuildersdevs, analysts, business

Build

Compose apps and agents

Compose apps and agents on the Calliope AI Workbench: the tool stack your builders already reach for, on one governed bench. Everything is assembled and installed through the Workbench Installer, inside your perimeter, on your compute. What leaves this station is an artifact the rest of the line can trust.

  • Devs, analysts and business users on one browser bench: IDE, notebooks, SQL, app and agent builders, deep research, chat
  • Ships to Astrolift with an integrated CLI and one manifest
  • Installed by the Workbench Installer on K8s, ECS or Cloud Run
Calliope AI Workbenchowns the stage
LicensingWorkbench proprietary
SubstrateYour compute: K8s, ECS, Cloud Run, on-prem
EgressNone required

calliope.ai ↗ Back to the assembly

01 · The problem ask for more

Every team vibe-codes its own stack: notebooks here, a chat wrapper there, agents in a repo nobody governs. The work is real, but none of it is repeatable, and IT finds out last.

02 · How build answers it ask for more

The Workbench puts every builder, dev, analyst and business user alike, on one governed bench inside your perimeter. Same tools, same identity, same data plane. What leaves the bench is an artifact with a manifest, not a screenshot of a notebook.

03 · Go deeper ask for more

The whole surface is one drawing: the framework is BROCS, and this machine is one stage of it.

calliope.ai ↗ Download the PDF Book a demo

Crown · layer 2the work, leaving the bench in plates
Works · layer 1hub, corner posts and tool blocks
Base · layer 0users and benches, spoked into one hub
DrawingThe build machine
NoCAL-SURF-001-B
RevA
Part ofThe Private-AI Deployment Blueprint