System Topology Studio
Prototype C4-style canvas that shows a built-in sample system (Acme Petshop). Backstage import and C4 export return canned results.
packages/topology-manager
System Topology Studio is a prototype. The window shows one hard-coded example system, “Acme Petshop Platform”, so you can see how a topology canvas could look. It does not discover your architecture.
What you see
- Header: the view switch L1 Context, L2 Containers, L3 Components and Live OTel, plus the buttons Add Data Source, Import Backstage and Export C4.
- AI Architecture & C4 Topology Synthesis: a prompt box and a short two-question form. Completing it loads the six sample nodes (web client, REST API, shared library, vaccine gateway, Kafka event bus, PostgreSQL) and their links. The answers do not change the result.
- Backstage Catalog: a list of the nodes, searchable.
- Canvas and Node & Contract Inspector: click a node to see its fields. The “live traffic” numbers on the canvas are random values generated in the browser, not telemetry.
What the buttons do
| Button | Behavior today |
|---|---|
| Import Backstage | Ignores any catalog-info.yaml and adds one fixed sample node (“Acme Tax Calculation API”). |
| Export C4 | Shows a fixed PlantUML C4 container diagram of the sample system, not a diagram of the current canvas. |
| Add Data Source | Writes packages/kube-studio/manifests/petshop-baseline/04-analytics-postgres.yaml (a Deployment and Service for postgres:16-alpine with a default postgres password) and adds a sample entry to ~/.config/robos/db-manager-connections.json. Both use fixed example values. |
When the sample topology is loaded it is saved as JSON text to ~/.robos/projects/acme-petshop-platform/.robos/topology.yaml, and read back from there the next time. The path is fixed in main.js.
The Add Data Source button changes files in the repository checkout and in your RobOS config folder. It generates plain Kubernetes YAML, not a Helm chart.
Run it
The package has no .desktop launcher. Run npm start in packages/topology-manager.
More in Architecture & Planning
Automation Studio
Editor for event rules and cron-style scheduled jobs, plus a viewer for the daily event log.
Issue Manager
Opens one GitHub issue, shows it with its workflow state, moves it between states by changing labels, and sets up a branch workspace for it.
Knowledge Graph Explorer
Browse, search, edit and validate the knowledge graph of your software, compare main with a branch, and import or refine graph data from source repositories.
People Directory
Searchable list of people with contact and org fields, stored as JSON files on your machine.
People Manager
Prototype roster screen for teams of people and AI agents, grouped by Team Topologies type. It shows built-in sample data.
RobOS Create Project & App Wizard
Scaffold a new project from an archetype, or import an existing folder, and register it in the RobOS project files.
RobOS Documentation
Lists the components in the knowledge graph, shows which have a documentation page, and lets you generate, edit and export those pages.
RobOS Group Manager
Create and edit developer groups (members, repositories, software, onboarding steps, secrets, CI) and set up a sample company identity.
Schema Studio & Registry
Browse the bundled Schema.org vocabulary, generate JSON-LD, TypeSpec, SHACL and code stubs for a new entity, and validate JSON-LD against RobOS shapes.
Task Board
Read-only board and list view of the issues in the active GitHub task server, grouped by status.
Task Servers
Settings screen where you add Jira and GitHub issue trackers, store a pass path for the token, and test the connection.
Workflow Studio
Define issue types, states and transitions for a GitHub task server, move an issue between states, and run a script or AI prompt when it enters a state.