Build a complete engineering specification
Connect architecture, interfaces, requirements, decisions, and implementation details with precise references between specs, diagrams, nodes, and connectors.
Connect · Design · Build
Architect, Design and engineer systems together—from concept to deployment.
Structured thinking. Connected systems. Built forward.
Full-stack engineering collaboration
Software, infrastructure, electrical, mechanical, and robotics teams can work in the same organization while keeping the notation and detail their work requires. Diagrams, specifications, decisions, and reviews stay connected as the design evolves.
Connect architecture, interfaces, requirements, decisions, and implementation details with precise references between specs, diagrams, nodes, and connectors.
Co-edit the system in real time, preserve version history, and share expiring review links so subject-matter experts can contribute without losing the thread.
Organize people into role-based workspaces, restrict sensitive projects, require SSO or MFA, and retain an audit trail of important changes.
A connected engineering workflow
Turn an early concept into a reviewable engineering record without separating the visual system from the decisions that shaped it.
Use focused libraries, professional connectors, engineering metadata, smart routing, and quality checks on one unbounded canvas.
Create first-class specifications and type @{name} to reference diagrams, nodes, connectors, or other specs with backlinks.
Share a governed review or turn routes into an animated walkthrough that explains complex behavior without redrawing the architecture.
Living engineering specifications
Write requirements and decisions beside the engineering work they explain. Reference a diagram, another specification, an exact component, bundle, or connector—then follow the relationship in either direction.
Keep power, EtherCAT, and safety routing traceable. The controlled requirements reference @{Harness and cable topology}.
BOM lines, bundle lengths, coverings, and release checks stay tied to the active Harness configuration.
Built for technical clarity
Struct agent
Ask for a custom diagram or a precise edit. The signed-in agent inspects the current project, changes the canvas directly, updates linked engineering records, and checks the result before reporting completion.
Private by design
Use governed organization sync for team projects or keep sensitive drafts in private offline mode. Product analytics never receives diagram or specification content.
Purpose-built canvas
Browse 56 semantic shapes, 338 AWS and Kubernetes icons, 184 professional engineering symbols, six agentic patterns, and 27 specification-backed connector presets with standards provenance.
Open interchange
Import Mermaid, PlantUML, images, or editable projects. Export full-fidelity SVG, PNG, PDF, Struct JSON, Mermaid, Word, Markdown, HTML, or text.
Quality built in
Hierarchical, radial, and grid layouts; tidy spacing; architecture checks; named layers; checkpoints; reusable libraries; and 12 nondestructive visual themes.
A library that speaks your discipline
Move between focused libraries instead of hunting through one endless list. Every item places as an editable, connectable node and can be pinned to the main toolbar.
Solutions by engineering discipline
Each discipline gets the symbols, connector semantics, starters, metadata, and checks it needs. The organization still has one connected place to review the system.
Model system context, services, data stores, APIs, classes, sequences, states, ER models, and trust boundaries with editable semantic shapes.
Use recognizable provider artwork for deployed technology while keeping every cloud service and Kubernetes resource movable, connectable, and exportable.
Explain RAG, agents, model serving, data pipelines, experiments, evaluation, governance, drift, and human review without flattening them into vague boxes.
Document devices, subnets, trust boundaries, secure access, traffic management, wireless links, failover paths, and packet observability.
Map source, CI, quality gates, artifacts, environments, deployment governance, operations, incidents, recovery, and rollback.
Create unboxed ANSI/IEC-style circuits, mixed-signal chips, and microcontroller references with terminal-aware conductors and editable engineering metadata.
Build ISO-oriented technical drawings and system schematics with proportioned features, dimensions, datums, GD&T, surface finish, piping, and motion.
Separate the functional stack from detailed robot wiring while preserving power, independent safety, deterministic control, perception, feedback, and physical motion.
Feature matrix
Every visual library uses the same local-first canvas, linked specifications, presentation tools, agent handoff, and full-fidelity export pipeline.
| Capability | Software | Cloud | Data & AI | Network | DevOps | Electrical | Mechanical | Robotics |
|---|---|---|---|---|---|---|---|---|
| Focused visual library | 56 semantic shapes | 338 provider symbols | Agentic + ML vocabulary | 18 symbols | 18 symbols | 56 symbols | 33 symbols | 24 symbols |
| Professional relationships | 7 core choices | Core + verified network | Labeled core flows | 4 cited presets | 2 cited presets | 11 cited presets | 6 cited presets | 3 cited presets |
| Starter projects | Context to ER model | Focused cloud canvas | Data pipeline + patterns | Focused network canvas | Focused DevOps canvas | Circuits, chips, MCU | Technical drawing | System stack + wiring |
| Engineering metadata | Owner, technology, status | Provider + resource identity | Model, data, governance | Protocol + boundary | Stage + environment | Ref, value, part, pin | Size, datum, tolerance | Ref, bus, frame, safety |
| Quality checks | Architecture diagnostics | Architecture diagnostics | Architecture diagnostics | Architecture diagnostics | Architecture diagnostics | Electrical design checks | Drafting conventions | Robot completeness checks |
| Linked specifications | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Agent skill + validated patches | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Animated presentation | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| SVG, PNG, PDF, project export | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Visual and versionable
Start from a template, draw by hand, import Mermaid, or ask an external agent for a first pass. However the diagram begins, the result stays editable.
1flowchart TD
2client["Web client"]
3
4gateway["API gateway"]
5
6service["Payment service"]
7
8client -- "HTTPS" --> gateway
9gateway -- "charge" --> service
Private local multiplayer
Invite a teammate on the same network and collaborate in real time—no account, hosted room, or cloud relay. Diagram changes travel directly between verified peers and remain available when the internet is not.
One connected system
Keep software, infrastructure, electronics, mechanics, and robotics aligned around the interfaces and decisions they share. Struct preserves each field’s visual language without splitting the system into separate stories.
Explore Struct resources
Questions, answered
Start with a private diagram or a shared organization, and choose how much process the work needs.
Yes. Create a hobby organization for synchronized projects or choose private offline mode without an account.
Signed-in projects synchronize to the selected organization. Private offline projects remain in the current browser profile. Optional analytics measures visits, editor activity, and download clicks, but never receives diagram or specification content, names, files, or review-link secrets.
Organizations isolate members, seats, projects, grants, versions, retention, and audit history. Authenticated WebSockets exchange collection-keyed changes by stable node, connector, stroke, and specification ID, while optimistic version checks reject conflicting writes for retry.
Yes. Enterprise organizations can require OpenID Connect SSO with PKCE, verified email, domain allowlists, and just-in-time provisioning. Password accounts can enable TOTP authenticator codes and receive eight one-time recovery codes.
Struct supports Mermaid flowcharts, class diagrams, sequence diagrams, state diagrams, and entity-relationship diagrams, with export back to Mermaid where the format can preserve the model.
Struct provides focused libraries and workflows for software architecture and UML, AWS and Kubernetes cloud architecture, data and AI, networking, DevOps, electrical engineering, mechanical engineering, and robotics. Each discipline includes relevant starters, symbols, connector semantics, metadata, and shared specification, presentation, agent, and export workflows.
Yes. Cloud contains 307 AWS Architecture Icons plus the Kubernetes logo and 30 resource symbols. Engineering provides 184 symbols and 27 connector presets tied to named IEEE, IETF, SLSA, OCI, IEC, IPC/WHMA, ISO, EtherCAT, ROS 2, or OMG specifications, including electrical schematic parts, harness/device matings, ISO-oriented mechanical drafting, and robotics communication relationships.
Signed-in users can ask the project-aware agent to create or edit the current diagram, update linked Specifications, prepare engineering deliverables, and run deterministic functional and visual checks. Free accounts receive 5 prompts per UTC day and entitled paid accounts receive 50. For external coding-agent workflows, the downloadable agent kit can still produce validated Struct results without placing model credentials in the editor.
Type an @ reference in a specification to find another specification, a diagram, an exact node, or a connector. Struct renders a preview and adds a backlink to the referenced diagram item, so readers can move from the decision to the visual context and back again.
Yes. The web shell is offline-capable after its first successful load. Desktop peers can also sync canvas changes, specifications, metadata, and presentation order directly over encrypted LAN, an offline hotspot, or Bluetooth on macOS—without a cloud relay.
Any discipline