Book a demo

For hardware test & systems teams

Build hardware at the speed of software.

AI agents keep requirements, designs and tests in sync as you iterate.

Book a demo
Ø 493 mm 1.26 m REQ-031Chamber pressure ≤ 205 bar REQ-020Throat wall ≤ 900 K REQ-044Specific impulse ≥ 315 s TC-031.2Hot-fire at maximum pressure TC-020.1Throat wall thermal survey TC-044.1Specific impulse hot-fire TE-2 ENGINEPROGRAM TERNREV D1/17

Tensol traces requirements to the code, CAD and test evidence that proves them, then shows exactly what a design change invalidates.

  1. 01

    Trace

    Link every requirement to the design, code and tests behind it.

  2. 02

    Impact

    Change anything and see what it touches, upstream and downstream.

  3. 03

    Evidence

    Know which results still count and exactly what to re-run.

  4. 04

    Compliance

    Stay review-ready against FAA Parts 23, 25 and 450.

Built by founders and operators from Y Combinator, Carnegie Mellon, Rivian, MagnaBacked by Afore Capital, Carnegie Mellon, Graham Neubig

Software finds out in minutes. Hardware finds out in weeks.

Change a line of code and CI tells you what broke. Change one requirement and it takes weeks of spreadsheets and review meetings to find out.

Software

Change a line of code
CI says what broke

Minutes

Hardware today

Change one requirement
Spreadsheets Emails to owners Review meetings Re-test everything to be safe

Weeks

With Tensol

Change anything
Tensol says what the change invalidated

Minutes

HoursDaysWeeks

One change touches the whole V.
Nothing connects it.

Each step lives in a different tool, so the links between them live in people’s heads.

Which design was this? Did the build change since? Does this result still count? System requirementsSpreadsheet Subsystem requirementsWord and PDF Detailed designCAD and PDM ImplementationFirmware in git Component testRig logs Integration and HILBench files System validationShared drive Chamber pressure 180 → 250 bar Which firmware went on the rig? Traced by hand, if at all
  1. System requirementsSpreadsheetWhich limit is current?
  2. Subsystem requirementsWord and PDFWho owns this now?
  3. Detailed designCAD and PDMIs this the released model?
  4. ImplementationFirmware in gitWhich firmware went on the rig?
  5. Component testRig logsWhich design was this run on?
  6. Integration and HILBench filesDid the build change since?
  7. System validationShared driveDoes this result still count?

Tensol connects what you already use, then keeps it in sync.

Agents read across your tools and keep one live trace, so a change anywhere shows up everywhere it matters.

  • RequirementsExcelGoogle SheetsSharePoint
  • CADDassault SystèmesSiemensAutodeskOnshape
  • CodeGitHubGitLab
  • SimulationAnsys
  • TestLabVIEWTestRailtracetronic
  • Work and chatJiraLinearConfluenceSlackMicrosoft Teams

One live trace of your whole program

  • TraceEvery link, at a specific revision
  • AnalyzeAgents follow each change
  • FlagStale evidence, gaps, new tests
  • What goes staleRequirements, sign-offs and runs
  • What to test againAnd what you can leave alone
  • Who needs to knowIn the tools they already use
  • What’s ready for reviewThe package for PDR or CDR

Requirements live in Tensol. The conversations, tickets, CAD and code around them stay where they are.

Every requirement, traced to its proof.

Open any result and follow it through the requirement, system boundary, test case and run behind it. This is program Tern, a made-up upper stage.

L0 Mission

REQ-001Deliver 430 kg to low Earth orbitby decompositionJW

L1 Vehicle

REQ-002Upper-stage delta-v ≥ 4.1 km/sby decompositionAR
REQ-003Stage dry mass ≤ 410 kgby decompositionJW

L2 Propulsion

REQ-031Chamber pressure ≤ 205 bar180 bar at Rev DVerifiedRM
REQ-010Vacuum thrust ≥ 20 kN22.1 kN at Rev DVerifiedRM
REQ-044Specific impulse ≥ 315 s339 s at Rev DVerifiedRM

Proof, at exact revisions

CADTE-2 chamber v14
Simulationthroat_thermal r22
Codepc_control.c a3f9e2c
Test runHF-0412 hot-fire

An agent traces the impact across the whole system.

Chamber pressure goes from 180 to 250 bar for more thrust. In minutes, you see what goes stale, what to test again and who needs to know.

Impact analysisChamber pressure, 180 to 250 bar

Analysis agent3 of 6 requirements affected, 5 test cases to re-run

Changed

TE-2 chamberChamber pressure180 → 250 barTE-2 chamber v15

First order

REQ-031Chamber pressure ≤ 205 barFails, 250 bar
REQ-020Throat wall temperature ≤ 900 KFails, 990 K
REQ-012Engine dry mass ≤ 95 kgAt risk, 91.5 kg

Second order

REQ-007Shutdown valve qualified to 230 barBelow new pressure
REQ-022Regen coolant flow marginthroat_thermal r22Re-check
REQ-004Stage mass marginRe-check

Program level

REQ-001Mission performanceStill holds
§ 450.143Safety-critical system qualificationEvidence stale
Unaffected: REQ-010 thrust, REQ-044 specific impulse, REQ-030 engine lengthMaya, Sam and Dana notified in Slack

Work on a copy of everything.
The approved design stays untouched.

Tensol makes a working copy of the whole program, like a branch in software. It replaces the approved design only after it’s re-tested and approved.

Approved design

Rev D, signed off

Nothing here changes while the team works on the copy

Approved design

Updated to Rev E

Working copy includes

  • Docs
  • Requirements
  • Tests
  • Every link between them
1

Change it

Chamber pressure limit

205 260 bar

2

Re-test it

Only the tests this change touched

5 of 5 passed

3

Approve it

Nobody approves their own change

2 of 2 reviewers

Start from the rule you’re certifying to.

Tensol maps FAA regulations onto your requirements, then shows which sections have evidence and exactly where the gaps are.

Also DO-178C, ISO 26262, ASPICE and your own program templates.

Certification evidence stays current.

As the design evolves, Tensol regenerates the evidence trail and exposes anything that needs fresh review. Evidence shouldn’t be rebuilt the week before an audit.

  1. Requirement changedRevision captured
  2. Impact tracedUpstream + downstream
  3. Evidence regeneratedStale items flagged
  4. Review package currentPDR / CDR ready
Compliance checklistBy CFR section
Traceability matrixRequirement to run
Verification reportRuns at exact revisions
Change historyWho, when, which rev

Requirements in your language.
Tests as rigorous as you want.

AI writes requirements the way your team writes them, then generates test cases based on how rigorous you want testing to be.

REQ-031

The TE-2 engine shall keep chamber pressure at or below 260 bar.

Written in your team’s language

How rigorous should testing be?

5 test cases generated

  • Steady hot-fire at maximum pressureDoes the limit hold in normal running?Included
  • Proof pressure at ambient temperatureDoes the chamber survive above the limit?Included
  • Start transient overshoot above steady-state pressureRecords the first 400 ms of every start.Included
  • Hot restart after a shutdown at maximum pressureRestart is required, never tested hot.Included
  • Cold propellant inlet at end of burnThe boundary nobody wrote down.Included

Nothing goes in until an engineer approves it.

Agents suggest. Engineers decide.

Our agents trace, flag and assemble the busywork. The engineering judgement stays with your team, and every action stays on the record.

Agents can

  • Trace impact across the system
  • Flag stale evidence and coverage gaps
  • Work on a copy and draft requirements and tests
  • Assemble the review package
People only past this line

Only your team can

  • Approve a change
  • Update the approved design
  • Sign off a design review
  • Close a compliance finding
  1. flight-agentFlagged TC-007.1 as stale after TE-2 chamber v15Asked by Ravi Mehta
  2. flight-agentTried to approve REQ-007Refused
  3. Ana ReyesApproved REQ-007 on the working copyApproved

Built to run where your data has to live.

Tensol deploys inside your boundary, for export-controlled programs from day one.

Your boundary
Tensol app and APIyour VPC
Requirements and evidenceyour database
Agentsscoped by you
AWS GovCloud, your VPC or air-gapped

Self-hosted or GovCloud

Your VPC, AWS GovCloud, or fully self-hosted for air-gapped programs.

ITAR / EAR compatible

Architecture and deployment options designed for export-controlled programs.

Permission-scoped agents

Agents act only within the permissions you grant them.

Every action on the record

Ownership, change history and review controls stay intact.

What will your next design change break?

See how Tensol finds the answer in minutes, before it reaches the test stand.

Book a demopratik@tensol.ai