Products

Three products, one shop.

Buy any one on its own, any two, or all three.

Why one company builds all three

Two instruments and an interface

MoldVision and QualRun are instruments. They measure something your shop was not measuring before — the condition of a tool surface, and whether a process actually did what the validation says it did.

Phil is the interface. It answers questions out of what your shop already wrote down. The instruments produce evidence; the interface makes it askable. That is the whole reason they belong together, and it is why none of them needs the other two to be useful.

Interface

Phil

Ready to install

Troubleshooting and process questions, answered from your own SOPs, spec sheets and resin data, with the source document cited. Runs on your PC or on a server we host.

For: process techs, on every shift.

How Phil works

Instrument

MoldVision

Available for pilot

Photograph a mold surface and get a recorded, comparable observation of its condition instead of an opinion that changes with whoever is looking.

For: toolmakers and tooling managers.

How MoldVision works

Instrument

QualRun

Prototype

Reads validation and capability data and assembles the evidence package a review needs — while your QMS stays the system of record.

For: quality managers and process engineers.

How QualRun works

No sales gloss

Where each one actually stands

One of these is ready to install. The other two are ready for a pilot with someone who wants to be first. We are saying which up front because you would work it out in week two anyway, and finding out then is worse for both of us.

Phil — ready to install. The relay it depends on runs in production and the Windows installer is packaged. It has no paying customer yet, and the installer has not been run on a clean PC that we did not build ourselves. Everything else about it works.

MoldVision — available for pilot. Validated against synthetic imagery only. It has never been pointed at a real tool, and there is no pilot site yet.

QualRun — prototype. A finished piece of R&D rather than a shipped product. Validated on synthetic data, with no design partner yet.

Why we don't publish accuracy numbers

Both instruments have been tested, and both perform well on the test data we built for them. That test data is synthetic — generated, with the right answer known in advance, because that is how you check whether a method works at all.

A number from a synthetic test tells you the method is sound. It does not tell you what the tool will do on your steel, your lighting, your parts. Publishing it on a marketing page as though it did would be the most useful lie we could tell you, so we don't.

The first pilot is where real numbers come from. If you run that pilot, you will see them before we do.

Which one fits your shop?

Tell us how many presses you run and what's costing you time. We will say which of the three helps, or that none of them does.