tofupilot
Start for free
NEW MCP: Connect TofuPilot to Claude, Cursor

Industrialize your hardware tests.

Keep your test code. Deploy it to your stations, trace every unit, and investigate production failures with AI.

Start for free Explore templates
procedure.yamlYAML
name: PCB functional testplugs:  - name: Power Supply    python: instruments.power_supply:PowerSupplymain:  - name: Reference check    python: phases.reference_check    measurements:      - name: Reference voltage        unit: V        validators:          - {operator: ">=", expected_value: 3.250}          - {operator: "<=", expected_value: 3.350}
phases/reference_check.pyPYTHON
def reference_check(    measurements, power_supply):    power_supply.set_voltage(3.300)    measurements.reference_voltage = (        power_supply.read_voltage()    )
PRODUCTION / PCBA FUNCTIONAL TEST
Production test station with a sky-blue board in its fixture, one rack-mounted power supply, and an operator screen showing FAIL at 3.3582 V
  1. Scan S/NComplete
  2. Run test3.3582 VFAIL
  3. Sync to dashboardComplete
  4. Alert email sentYield drop
  5. AI investigationPSU calibration drift

FROM ROBOT JOINTS TO SPACECRAFT

  1. 01Build or connect
  2. 02Deploy & run
  3. 03Trace
  4. 04Detect
  5. 05Investigate
01 / BUILD OR CONNECT

Connect existing tests.
Build new ones.

Keep your test code, or build with the tofupilot framework. Bring the results into one place.

Explore integrations
A laptop showing tofupilot Studio, connected to a sky-blue circuit board and a bench supply reading 3.30 volts

Keep your existing tests.

Building new tests?

The open-source tofupilot framework

Run phases and slots in parallel, connect instruments, validate measurements, and guide operators with rich, custom forms.

Explore the framework
Tofu pilot holding a GitHub star
02 / DEPLOY & RUN

Run on the line.

Push your test code to update stations automatically and give operators a clear UI to test each unit.

Explore deployment
An electric motor test station with a shaft coupling, one power supply, barcode scanner and a PASS operator screen
GitHubGitLabBitbucket
AUTO-PUSH ON
Push to main8f2c91a
Buildv1.4.2
DeployBetween runs
03 / TRACE

Trace the whole unit.

Navigate from the assembly to each component’s test results.

Explore traceability
A slim humanoid arm with a five-finger hand and a sky-blue control board seated inside the forearm
Unit genealogyARM-0042
  1. Humanoid armARM-0042
    🇫🇷In-house · Paris
    Arm functional testPASSStation: Arm EOL 01
    1. Shoulder jointJNT-0087
      🇫🇷In-house · Paris
      Joint motion testPASSStation: Motion bench 02
      1. Shoulder actuatorACT-0087
        🇺🇸Aster Motion · Austin, TX
        Torque calibrationPASSStation: Torque bench 01
      2. Joint encoderENC-0063
        🇨🇭Nova Sensors · Zurich
        Encoder calibrationPASSStation: Encoder bench 01
    2. Forearm moduleMOD-0124
      🇫🇷In-house · Paris
      Module testPASSStation: Module EOL 01
      1. Control boardSN-0251
        🇭🇺Circa Electronics · Budapest
        PCB functional testPASSStation: Bench 03
      2. Wrist actuatorACT-0124
        🇨🇳Jade Motion · Shenzhen
        Motion range testPASSStation: Motion bench 02
04 / DETECT

Catch the drift.

Spot measurement shifts before you set pass/fail limits. Find the affected units.

Explore alerts
Full laptop showing an Outlook drift alert, with the tofupilot mascot as the email sender avatar
PCB functional test5 STATIONS
BASELINE MEAN3.3072 V
LATEST 100 READINGS—.——— V
REFERENCE VOLTAGE · VCompared with baseline
Day 1Day 11 · retest driftDay 14
MEASUREMENT MONITORING

No active alerts

Measurements are tracking the baseline.

05 / INVESTIGATE

Find the probable cause.

Find probable causes with AI, then review the evidence with your team.

Explore AI analysis
A quality hold trolley with a forearm module, actuator, circuit boards and controller in separate foam trays, each bearing a hanging red HOLD tag
AI root cause analysis350 RUNS
INCIDENT

Why did reference voltage drift?

ManOperatorChecking…
MachineTest stationPending
MaterialComponent lotPending
MethodTest versionPending
MeasurementInstrumentPending
EnvironmentTemperaturePending
DRIFT
CHECKING 1 / 6 · MANOperator

The shift appears across operators.

INVESTIGATION SUMMARY

SECURITY & DEPLOYMENT

Control access. Choose your hosting.

Access controls

SSO & SCIMManage sign-in and membership from your company directory.
Roles & permissionsAssign Admin, Developer, Viewer, or Operator permissions to each member.
Access groupsGive suppliers and teams a station view scoped to their work.
API audit trailInvestigate API activity and trace each request to its source.

Deployment options

Managed cloudOperated and updated by tofupilot.
Dedicated cloudYour own cloud environment, managed by tofupilot.
Self-hostedDashboard, deployer, and database on your infrastructure.
Read the security guide

YOUR FIRST STATION

Start small.
Prove it on your hardware.

Connect one procedure and one station. See what changes for your engineers, operators, and quality team before a wider rollout.

START YOURSELF

Get started at your own pace.

Follow the docs to connect your first test and explore the results with your own hardware.

Open the docs
PLAN YOUR ROLLOUT

Plan your rollout with us.

Work with our engineers to connect your first test and define a rollout that fits your team.

Plan my rollout

Define success first. Measure test update effort, investigation time, and total rollout cost.

Build your business case

ENGINEERS IN YOUR CORNER

When the line is waiting,
don’t troubleshoot alone.

Two tofu characters wearing headsets, one wearing a pilot cap
COMMUNITY · DISCORD

Ask other hardware test engineers.

Join our team and community to solve test issues and share practical advice, and get the latest tofupilot news.

Join Discord
ENTERPRISE · PREMIUM SUPPORT

Get expert help when you need it.

Troubleshoot with our test engineers in your preferred chat app, by email, or by phone.

Discuss enterprise support

BEFORE YOU START

A few practical
questions.

Do I have to rewrite my tests?

No. Connect an existing framework, send results through an SDK or the REST API, or import completed reports. Use the tofupilot framework when you want to build a new procedure. Learn more.

What happens when a station goes offline?

The tofupilot CLI queues completed runs locally when uploads fail and retries when connectivity returns. Test steps that call online services still need a connection. Learn more.

What is open source, and what is paid?

The hardware test framework is open source and runs locally. The connected platform provides shared production data, deployment management, analytics, and alerts under separate plans. Learn more.

Does tofupilot scale for high-volume manufacturing?

Yes. tofupilot processes thousands of test runs daily and supports queries across millions of data points. For your rollout, review station count, measurements per run, attachment sizes, and retention with our team. Learn more.

Where does our data live? Can we self-host?

Choose managed cloud, dedicated cloud, or run the dashboard, deployer, and database on your own infrastructure. Confirm your cloud region, retention, and AI processing requirements during the security review. Learn more.

What can AI access, and can we check its reasoning?

Root cause analysis reads the test data permitted by the access of the person who launches it. It tests hypotheses against your runs and shows the supporting evidence and next checks. AI features are in preview. Learn more.

What implementation support is available?

For a supported rollout, scope the work with our team. Enterprise onboarding includes engineering help with procedure migration and MES integration. Learn more.

How do we estimate the cost?

Compare the plans using your expected users, stations, test runs, and storage. For a rollout, include integration effort and the implementation support you need. Learn more.