For multidisciplinary engineering teams

Build the complete system together.Without losing the details that matter.

Bring software, cloud, data, network, DevOps, electrical, mechanical, and robotics specialists into one governed workspace. Co-edit live diagrams, link specifications and decisions to exact work, and keep every review in context.

  • Live diagrams + specs
  • Roles + restricted projects
  • SSO + MFA
  • Versions + audit
AURELIA-R1 · multidisciplinary systemSource-rendered project
Editable AURELIA-R1 multidisciplinary system connecting software, electrical, network, safety, robotics, and mechanical interfaces

Rendered from the checked-in AURELIA-R1 system project used by the application.

SoftwareAutonomy stackOwner · Morgan
ElectricalPower + safetyOwner · Alex
MechanicalJoint assemblyOwner · Priya
SystemsInterface controlReview · 3 comments
@
System spec synced12 linked diagrams

One organization, many engineering languages

Specialized work. Shared system context.

Struct avoids the two common extremes: isolated discipline tools with no common view, or generic canvases that strip away the meaning engineers need.

Use the right notation for every discipline

Each team works with focused libraries, connectors, metadata, starters, and checks designed for its discipline.

  • Eight engineering disciplines
  • 1,000+ editable symbols
  • 27 specification-backed connectors
@

Connect specifications across disciplines

Connect requirements and decisions to whole diagrams, exact nodes, relationships, or other specifications with a navigable way back.

  • Visual and Markdown authoring
  • Bidirectional references
  • Markdown, HTML, and Word export

Collaborate on one current system

Co-edit diagrams and specifications, preserve versions, and use expiring links for controlled asynchronous review.

  • Authenticated live sync
  • Conflict-aware versioning
  • Review links and audit events

Teamwork in Struct

One controlled project record across engineering disciplines.

Teams can work in focused diagram languages while shared interfaces, specifications, versions, reviews, and access controls stay connected.

  • 01Organization and project rolesOwner, admin, member, and viewer access with explicit grants for restricted projects.
  • 02Cloud synchronizationNodes, relationships, annotations, metadata, Specifications, and presentation order update together.
  • 03Review threads and versionsAnchor feedback, save named checkpoints, and preserve decisions beside the engineering state.
  • 04Controlled sharingCreate review and live links with project policy, expiration, and audit context.

From concept to controlled record

A collaboration model that scales with the work.

Start privately, invite the right specialists, and add governance as the system becomes a shared organizational asset.

01

Create the organization and project

Keep teams, seats, projects, retention, and policy isolated within the correct organizational boundary.

02

Invite each discipline

Assign owner, admin, member, or viewer roles and restrict sensitive projects to explicit grants.

03

Build diagrams and specifications live

Synchronize nodes, routes, annotations, metadata, and linked specifications as the team works.

04

Review, version, and present

Save durable versions, share expiring reviews, inspect audit events, and explain the system with animated walkthroughs.

Governance without ceremony

Control access. Preserve evidence. Keep moving.

Organization features are designed to make engineering work easier to trust without turning every change into an administrative workflow.

People and roles

Manage seats, expiring invitations, tenant switching, role assignments, and immediate suspension from one organization boundary.

  • Owner, admin, member, viewer
  • Seat reservations and invitations
  • Project-level restricted grants

Identity and security

Use Argon2id password sign-in, TOTP MFA with recovery codes, or enterprise OpenID Connect SSO with PKCE.

  • Verified email and domain allowlists
  • Just-in-time SSO provisioning
  • Revocable sessions and review links

History and evidence

Preserve project versions, organization audit events, retention settings, and the decision context attached to the architecture.

  • Conflict-safe version history
  • Reviewable organization events
  • Configurable retention