Loading Machine Mind
Machine Mind
Join the waitlist

Guided industrial diagnostics

The know-how of your best engineers, on every engineer’s screen.

When a machine breaks down, Machine Mind helps the person in front of it find out why. It works through the fault one check at a time, using that machine’s own manuals, and a person confirms the cause.

Try the demo Join the waitlist

The demo runs here on the page. No sign-up needed.

An engineer in a hard hat and face shield works at an open electrical panel, with a multimeter beside them.

Try the demo

Example machine, scripted case

You’re the engineer, and this machine has just stopped. Pick any answer and watch every cause get re-scored. These are the steps of a real investigation, on a machine we made up.

An industrial press in a dark workshop, lit by a single lamp.

When a line stops, judgement is the first thing to go.

It’s 2 a.m. The person who knows that machine is off shift, the answer is somewhere in a manual nobody has time to read, and someone presses reset to get the line moving.

Machine Mind gives the engineer in front of the machine the next check, the reason for it and the page it came from. When the checks run out, it brings in a senior with everything already on the table.

Capture evidence before reset

Record what the machine is showing now. Once a trip is reset, this evidence is gone.

Alarms / trip codes
417, servo amplifier
Status indications
Amplifier LED red, arm stopped mid-stroke
Time of fault
02:14

From the app, with example entries.

Our vision

Make downtime shorter. Make machine knowledge permanent.

Factories, ships and plants run on machines, and on a few experienced people who know how to fix them. When those people are off shift or move on, what they know goes with them.

We’re building the system that keeps that knowledge, on our own hypothesis and thinking engine. It sits beside the person at the machine, reasons through the fault with them, and learns from every solved case, so the next one is faster.

  • From alarm to answer, faster

    Less time searching manuals and phoning around, more time fixing the real cause.

  • The same standard on every shift

    Whoever is on site follows the same careful reasoning, one check at a time.

  • Knowledge that stays

    What a team learns is kept as verified procedures, not lost when people move on.

Our engine

Our edge is our own hypothesis and thinking engine.

Machine Mind runs on a proprietary algorithm we built for one job: finding out why a machine has stopped. General AI tools can talk about a fault. Ours is built to solve it.

How it works stays with us, but the demo above shows the kind of reasoning it does.

  • Built for machines

    Designed from the ground up for one thing: industrial fault-finding.

  • Reasons like your best engineer

    It thinks a fault through, so the person at the machine gets more than a quick guess.

  • Knows when to ask a person

    It’s built to bring in a senior when it matters, and it doesn’t bluff.

  • Gets stronger with every fix

    Each solved case can make the next one faster.

One case, from first alarm to signed-off repair.

A fault in Machine Mind becomes a case with a stage and a full record. It carries across shifts, and the system never closes it on its own.

  1. Find the machine by name, barcode or NFC tag. Type it, say it, or attach a photo, video or log file. Machine Mind reads what it can and asks you to check what it captured. Your original report is kept.

  2. Machine Mind works through the fault with the engineer, one check at a time, and gives the reason for each one.

  3. When the evidence points one way it says so and stops. An engineer confirms the root cause. Skipped causes are acknowledged and recorded in the case.

  4. The engineer records what was changed. If the manuals don’t describe the fix, Machine Mind says that and sends you to a senior instead of inventing one.

  5. Did the original fault clear? Where no approved procedure exists, a senior engineer signs off the repair before the case resolves.

  6. The solved case can be submitted as a reusable path. Once a senior certifies it, the next engineer who meets that fault gets the verified procedure.

Case ReportExample

Alarm 417: transfer arm stops mid-stroke

Awaiting senior sign-offFeeder 2
Root Cause
Machine version mismatch on the transfer arm drive
Corrective Action
Loaded the documented machine version and restarted the control
Verified By
With a senior engineer

Symptom

Arm stops mid-stroke with an error from the servo amplifier.

Alarm code: 417 · Fault time: 02:14
Media evidence: photo of the alarm screen

Checks

With the drive isolated and locked off, does transfer arm 1 move freely by hand over its full travel?Yes, it moves freely

Does the machine version set in the control match the documented version for this variant?No, they do not match

Timeline

  1. Report confirmed
  2. Root cause confirmed
  3. Repair note: the fault has cleared
  4. Asked a senior engineer to verify the repair
  5. Submitted as a reusable path
Print / save PDF

Every answer says how far to trust it.

General AI tools sound equally sure whether they know or not. In front of a live machine that is a safety problem and an expensive one.

Machine Mind grades each answer by where it came from and shows that grade on screen, so an engineer knows when to act and when to check.

Verified

From a senior-signed procedure.

The path is fixed and checked. The same fault gets the same steps every time.

High

Grounded in a cited manual reference.

The manual opens at the cited page, so the engineer can read it for themselves.

Medium

Grounded in the machine documentation, without a specific citation.

Useful direction, with no exact page to point to.

Low

AI reasoning with no manual reference found.

Flagged on screen as a starting point to verify.

When there is nothing to go on, it says so. These lines are from the product.

“No verified procedure matches that yet. We won’t guess a fix, but we can reason through it with you.”
When a fault has no procedure
“The manuals for this machine do not describe how to correct this cause. Ask a senior engineer before repairing.”
When the fix isn’t documented
“The evidence makes this branch eligible for review. Machine Mind will not close the case automatically.”
When one cause pulls ahead

Five tabs, built for the person standing at the machine.

Machine Mind is a diagnostic operating system for industrial machinery. That makes it a different thing from a chatbot, a manual search tool or a CMMS. It installs on a phone and goes where the fault is.

Start with what you can see.

Choose the machine, say what’s happening in your own words and attach whatever you have. Machine Mind turns that into a confirmed report and starts the investigation.

  • Find machines by name, barcode or NFC tag
  • Attach photos, video, voice notes, PDFs and log files
  • Guided mode for step-by-step detail, Expert mode for concise technical prompts
  • Open cases stay on the home screen, with reminders until they’re closed

Multi Mind

Put several AI models in a room and let them argue.

One AI can sound certain and still be wrong. Multi Mind is a brainstorming session for your hardest questions. Several top-tier AI models work on the same problem, challenge each other’s reasoning and push towards a resolution.

  • Ask anything about a machine

    Type it or say it, and add a photo, video or PDF. A fault nobody can crack, a repair you’re unsure of, an open case that has stalled.

  • With a machine, or without one

    Pick a machine or an open case for the models to work from, or leave the context empty and just ask.

  • Agreement and disagreement

    You see where the models agree and where they clash, what evidence is missing and any safety concerns, then a verdict and a next action.

Example sessionContext: Feeder 2

“Alarm 417 keeps coming back after a reset, and the arm moves freely by hand. What are we missing?”

  1. They start apart

    Model A

    It began after the control restore, so I’d check the parameter set first.

    Model B

    An alarm that returns after a reset can mean a damaged motor cable. I’d test that first.

    Model C

    Neither of you has asked what the amplifier’s fault flag says.

  2. They argue it out

    Model B

    A cable fault shows up on the motor side, whatever the parameters say.

    Model A

    Then why did it start the day the control was restored? A cable doesn’t care about that.

    Model C

    Timing is a clue, not proof. Read the fault flag before anyone opens the connector.

    Model B

    Fair. If the flag isn’t a motor fault, I’ll drop the cable.

  3. They land on a way forward

    Verified across top tier models
    Agreements
    A parameter mismatch fits the alarm and the recent control restore.
    Disagreements
    One model would test the motor cable before the parameters.
    Missing Evidence
    Nobody has read the amplifier’s fault flag yet.
    Safety Concerns
    Keep the drive locked off during the hand check.
    Verdict
    Parameter mismatch is the leading cause.
    Next action
    Read the fault flag, then compare the machine version with the documentation.

A scripted example to show the idea. In the app, the answer comes back under these six headings, with the models and sources behind it.

Join the waitlist

Every solved case can become the next engineer’s answer.

When a fault is solved, the engineer can submit the case as a reusable path. A senior reviews it in Drafts and certifies it in minutes, and it goes live as a verified procedure.

Coverage grows from real work instead of being written by hand forever, and the reasoning stays with the plant when people move on.

Drafts

Procedures drafted from solved cases, waiting for senior review. Try it.

Alarm 417: transfer arm stops mid-stroke
Feeder 2 · drafted by SamStructurally valid

Knowledge base

Verified procedures the system can run.

  • Clamp pressure drops during the cyclerun 9×, 8 resolvedVerified
  • Emergency stop with no button pressedrun 4×, 4 resolvedLearned

Example entries.

Some steps stay locked to the people authorised to take them.

  • Steps that defeat a safety function are senior-only, sit behind an explicit confirmation, and are recorded in the job report.
  • Guided and Expert modes change the amount of detail. Permissions and safety gates stay the same.
  • An engineer who feels unsafe or unsure can open a live handoff to a senior before starting, with the safety context attached.
What Machine Mind can’t do It cannot verify that equipment is isolated or safe to touch. Engineers should only carry out checks they are trained and authorised to perform, and follow their site’s safety procedures.

Senior authorisation required

Senior only

Bridge the door interlock to jog the arm

Built around how maintenance teams already work.

An engineer in a hard hat and ear defenders, seen from behind, walking through a factory hall.

Engineer

Reports the fault, runs the checks and records the repair, with guided detail for as long as it’s useful.

Can hand off to a live senior at any step, with the investigation attached.

An engineer in a hard hat holding up a printed drawing to check it.

Senior engineer

Picks up escalations with every step already visible, so the first question isn’t “what have you tried?”

Signs off repairs, certifies new paths and authorises restricted steps.

An engineer working on a laptop beside a test rig full of wiring.

Admin

Keeps the plant model current: lines, machines, parts, and the manuals assigned to them.

Invites people and sets their roles. Accounts are by invitation.

Where we are today

A working demo you can try on this page, with early access through the waitlist.

Built for

Manufacturing plants, marine and vessel operations, process facilities and heavy electromechanical fleets.

Join the waitlist.

The demo is open to everyone. Real machines come next. Join the list and we’ll tell you when places open.

What it will take to start on a machine

  • Its manuals and drawings, as PDFs with selectable text
  • A senior engineer to approve them and sign off repairs
  • A list of the lines, machines and parts you want covered

We’ll only use this to tell you about Machine Mind. Reply to any of our emails to come off the list.

Talk to us.

Questions about the demo, the engine or working together? We’d like to hear from you.

+44 7426 517752