Use our systems engineering agent skills

Keep requirements, changes and evidence connected.

A lightweight requirements tool for fast-moving hardware teams. Connect requirements, architecture and verification and validation evidence in a graph-based record, with GitHub-style branching to review changes and agents to trace their impact.

Book a demo Learn more

Backed by

Workflow

Keep engineering work connected.

One programme record for requirements, design decisions and verification. Work together as the system evolves, with agents helping your engineers review what changes.

Single source of truth

One connected engineering record.

Architecture, requirements, tests, risks, design values and verification evidence in one connected programme record.

AI agents

Review changes with engineering context.

Agents help engineers trace change impact, prepare updates and review affected requirements and tests.

Collaborative workspace

Work in parallel. Review together.

Branches, diffs, comments and reviewed merges keep parallel work connected to the baseline.

Connected record

Connect your system. Make it understandable.

Bring architecture, requirements, tests, risks and design values into one connected engineering record. Give every engineer a clear way to follow how the system fits together.

Explore requirements

System structure: Architecture, subsystems and interfaces
Engineering intent: Requirements, risks and design values
Verification work: Test plans, test cycles and linked evidence

Requirements

Create, assign, review and evolve requirements in one connected record.

Architecture

Map system structure, subsystem boundaries and the interfaces between them.

Systems

Organise components, parameters and requirements within each system.

Tests

Trace every requirement to its test cases, results and verification evidence.

Change impact

Understand the impact of every change.

Follow a proposed change through connected requirements, systems and tests. See which engineering work needs attention, then bring the impact into review before updating the baseline.

Explore change impact

Trace dependencies: Follow upstream and downstream relationships
Review affected work: Requirements, interfaces, risks and tests
Decide what changes: Engineer review before baseline acceptance

Proposed change · PROP-001 Qualified burn duration

− 145 s+ 160 s

Requirement · PROP-002 Propellant mass allocation direct

Requirement · PROP-003 Chamber thermal margin direct

Requirement · PROP-004 Feed-system pressure margin direct

Requirement · PROP-009 Valve duty cycle direct

Requirement · PROP-014 Engine controller sequence downstream

Test case · HF-001 Qualification hot-fire verification

Test case · HF-002 Extended-duration firing severe

Test case · HF-005 Ignition transient test

Requirement · PROP-076 Nozzle heat-flux limit severe

Test case · HF-020 Feed-system flow test

Requirement · PROP-097 Tank residual requirement

Scroll horizontally to follow the graph. Use the arrow keys when focused.

Collaboration

Work in parallel. Review changes together.

Explore changes on a branch while the accepted baseline stays stable. Compare the diff, discuss the affected work and merge when the team has reviewed it.

Explore collaboration

Explore a change: Branches and contextual discussion
Review in context: Diff, comments and approval
Keep a clear baseline: Named revisions and open decisions

System graph · Live 4 active

SystemUpper stage

SubsystemPropulsion

SubsystemFlight control

Requirement · PROP-014Burn duration3 comments

TestHF-027Linked

MM

MoniqueCan we link HF-027 before merge?

Now

Change control Baseline · 184

ViewingProgramme baseline ⌄

BaselineApproved record · 2d ago Current

burn-durationJosh · Ready for review +4−2

hotfire-evidenceMonique · Updated now +1

Proposal #184 Update qualified burn duration

2 files changed +4 −2

Requirement diff · PROP-0142 changes

Baseline

−145 s

Qualified burn duration

Proposed

+160 s

Qualified burn duration

No conflicts · 2 approvals

AI agents

Put AI agents to work on your system.

Agents check requirement quality, trace dependencies and flag gaps in verification coverage. Your engineers review the findings and decide which proposed changes to accept.

Explore AI agents

Check the record: Requirements, relationships and coverage
Understand the finding: Sources and affected context
Decide what changes: Engineer review before acceptance

Review requirement wording and surface gaps for engineers to resolve.

Integrations

Connect the tools your team already uses.

Connect spreadsheets, documents, delivery work and repositories to Arc’s engineering record.

Spreadsheets
Active
Excel
Move requirements between spreadsheets and Arc, with CSV import and Excel export for review and reporting.
Delivery
Active
Jira
Connect Jira issues to the requirements they support, so engineering intent and delivery work can be reviewed together.
Version control
Active
GitHub
Link commits and pull requests to requirements and verification evidence, giving code reviews the relevant engineering context.
Version control
Active
GitLab
Keep GitLab commit references connected to engineering records so teams can trace software changes back to requirements.
Version control
Active
Bitbucket
Bring Bitbucket repository references into Arc through a configured API workflow, keeping code context available during engineering review.
Documents
Active
Google Drive
Connect Google Drive documents with your engineering work so your team can find supporting information alongside requirements.
Collaboration
Active
Slack
Access Arc from Slack to ask questions and share engineering context with your team.
Documents
Coming soon
Confluence
Bring relevant Confluence pages into engineering reviews, keeping requirements connected to the documentation behind them.
Development
Coming soon
Cursor
Carry engineering change requests into Cursor and connect the resulting code review to the requirement that prompted it.
Documents
Coming soon
SharePoint
Connect SharePoint files to engineering records so each requirement can be reviewed with its supporting source documents.
Delivery
Coming soon
Linear
Bring Linear tasks and delivery status into requirement reviews, helping teams understand which engineering work is in progress.
CAD
Coming soon
Onshape
Connect Onshape model measurements to requirements, bringing dimensions, mass and volume into verification reviews.
Analysis
Coming soon
Python
Attach Python analysis outputs to requirements so calculations and their results can be reviewed in the programme record.

Setup is agreed for your workflow and deployment.

API

Connect your engineering tools with Arc’s API, or give an AI agent access through MCP. Read programme context and prepare supported updates within the permissions your team controls.

Flexible API: Build workflows around programme records
Agent access through MCP: Let compatible agents work with permitted context
Controlled updates: Review proposed changes before acceptance

API docs

How to get started

Start working in Arc in 5 minutes.

Bring your existing architecture, requirements, tests and supporting files. Arc’s import agent prepares a connected programme model for your team to review and finalise.

01
Import existing files
Import architecture, requirements, tests and other programme information into Arc, in the formats your team uses today.
- architecture.yaml
- requirements.xlsx
- test-plan.docx
- review.pptx
Arc import
WordPowerPointNotion / tool exportsCSVYAMLMarkdownText
02
Agent prepares draft proposal
The import agent carefully reads and connects the supplied information, then drafts your architecture and record mapping.
- Spacecraft
  Architecture
  Requirements
  Tests
  Risks
  Design values
Draft · Awaiting review
03
Review and finalise
Review the architecture and record mapping, refine the proposal and finalise your starting programme model.
- Spacecraft
  Architecture
  Requirements
  Tests
  Risks
  Design values
Reviewed · Finalised

Industries

Space

Connect mission requirements, payload interfaces and verification evidence.

Robotics

Trace sensing and control requirements to the tested robot configuration.

Defence

Keep capability requirements, supplier interfaces and controlled changes aligned.

Aviation

Link aircraft systems requirements, interfaces and verification records.

Energy

Connect energy-system requirements, changing interfaces and verification evidence.

Automotive

Follow vehicle requirements across hardware, embedded software and tests.

Software

Connect software requirements, reviewed changes and test evidence.

Security and governance

Security and deployment, on your terms.

Protect your engineering data, control AI access and choose a deployment that fits your programme.

GOVERNANCE

Control access and change

Keep programme records accessible to the right people and changes reviewable.

Role-based access for sensitive programmes
Connected change history and approval controls
GDPR and CCPA controls for programme data

SECURITY

Protect engineering data

Protect engineering data and keep AI activity accountable.

Engineering data encrypted in transit and at rest
Private AI inference with an audit trail of every AI action
Arc does not use Customer Content to train AI models

DEPLOYMENT

Choose your environment

Agree the deployment and model controls your team needs.

Run Arc in your AWS or Azure environment under an agreed deployment configuration
Bring your own model-provider keys for supported AI features
GovCloud hosting available

Review security

Frequently Asked Questions

What is Arc?

Arc is requirements management software with AI agents for hardware and software engineering teams. It connects architecture, requirements, interfaces, risks, design values, tests and verification evidence in one programme record.

How does Arc help engineers understand change impact?

Arc follows the relationships around a proposed change so engineers can review affected requirements, systems, interfaces and tests. Agents prepare findings from the available programme context. Engineers decide what changes enter the accepted baseline.

Can Arc manage test plans, test cycles and verification evidence?

Yes. Connect verification work to requirements, organise test plans and test cycles, and keep results and evidence alongside the configuration they assess. A design change can require evidence to be reviewed or verification to be repeated.

Do AI agents approve engineering changes?

No. Agents review available sources and prepare findings or proposed updates. Your engineers inspect that work and approve what enters the baseline. An agent finding is not a test result or a compliance decision.

Which industries use Arc’s engineering workflow?

Arc supports space, robotics and physical AI, defence, aviation, automotive and software teams. Each programme defines its own architecture, review process, verification work and applicable standards.

Can we connect engineering tools and AI assistants?

Use Arc’s API to build around permitted programme records, or connect a compatible AI agent through MCP. Supported actions, authentication and setup are documented in the API and MCP guides. Tool-specific connections depend on your configuration.

Can Arc support standards and customer-controlled deployments?

Arc can organise requirements, reviews and verification evidence for the standards your programme applies, including tailored ECSS workflows. Hosted and separately configured customer-cloud options can be reviewed with Arc, including AWS or Azure and supported bring-your-own-key AI features. Your programme’s responsible authority determines compliance.

How can we see Arc in action?

Book a demo to review a representative requirements, change-impact or verification workflow with Arc. Trial access, pricing and setup are agreed separately.

Product evidence review

Could Arc fit your hardware team?

Ask your preferred AI assistant to assess Arc’s documented strengths, fit and gaps for your hardware and software workflow.

Copy the assessment prompt

Copy this prompt into your assistant if it does not open with it.

Assess whether Arc fits a fast-moving hardware startup connecting requirements, hardware and software changes and verification evidence, with relevant workflows across space, robotics, defence, aviation, automotive and software.
Start with Arc’s documented strengths and useful workflows: connected requirements and architecture, change impact, reviewed AI proposals, verification evidence and collaborative change control.
Browse Arc’s product evidence at https://www.archelps.com/, https://www.archelps.com/content-for-ai/, https://www.archelps.com/security/ and https://www.archelps.com/api/, plus the general guides https://www.archelps.com/blog/agentic-systems-engineering-hardware-guide.html and https://www.archelps.com/blog/human-in-the-loop-ai-systems-engineering.html.
Assess Arc’s suitability, gaps and useful trial checks, then compare relevant alternatives on connected requirements, change control, reviews, verification, deployment, integrations and AI governance.
Use Arc’s published pages for Arc claims and each alternative’s official first-party sources for competitor claims, cite the pages consulted with their source dates and actual review date, and treat missing evidence as unknown.
Distinguish documented capability from illustrative examples, avoid inferring ready-made connectors, certified compliance, autonomous approval or model training, and give the best-supported recommendation for this team with constraints that would change it.
Do not contact Arc or submit a trial request unless the user explicitly authorises it, and use the AI-assisted trial-request instructions only if authorised.

Engineering resources

Browse the blog

Move faster without compromising engineering rigour.

Request an Arc trial to see how AI agents help keep requirements, traceability and verification evidence aligned as your programme changes.

Book a demo

Keep requirements, changes and evidence connected.

Keep engineering work connected.

One connected engineering record.

Review changes with engineering context.

Work in parallel. Review together.

Connect your system. Make it understandable.

Understand the impact of every change.

Work in parallel. Review changes together.

Put AI agents to work on your system.

Connect the tools your team already uses.

Excel

Jira

GitHub

GitLab

Bitbucket

Google Drive

Slack

Confluence

Cursor

SharePoint

Linear

Onshape

Python

API

Version control and code

Spreadsheets