Orbweaver does not try to replace mature diagramming tools. It establishes a specific boundary: turn accepted semantic structure into a deterministic artifact that remains connected to its identity and origin.
Where it sits
CategoryExamplesPrimary purposeOrbweaver's position
Diagram as codeMermaid · D2People author diagram syntaxConsume structured system meaning
Graph renderingGraphvizAutomatic layout and broad exportAdd semantic identity, inspection and provenance
Visual editorsReact FlowBuild editable node canvasesProvide a read-oriented artifact viewer
Architecture modelingStructurizrModel C4 workspaces and viewsRemain domain-neutral across structured systems
The intended boundary
Structured sourceSchema · compiler · analyzer · configuration↓Semantic adapterEntities · relationships · provenance↓OrbweaverValidate · derive · render · inspect↓Portable artifactSVG · interaction · publishing
Choose Orbweaver when
- Your system already has structured entities and relationships.
- Visual geometry should be derived rather than maintained.
- Readers need to inspect identity, neighbors, metadata, or provenance.
- The same accepted input should reproduce the same artifact.
- You need a small library rather than a hosted modeling platform.
Choose another tool when
- You want people to sketch or manually arrange a diagram.
- You need a complete collaborative whiteboard or node editor.
- You primarily need an established sequence, Gantt, or mind-map syntax.
- Your architecture practice is explicitly organized around the C4 model.
Make structured technical meaning visible, inspectable, and publishable.