The Demo
Watch a row go from Medium to High.
Open the control plan, change how one check is performed, and the failure mode that depended on it flags before you have navigated away. This is that moment.
A working demo on seeded data, covering this one workflow rather than a whole product. Two parts to choose from, no login, nothing to install. Kamski itself is being built with its first design partners.
Open the live demoThe Problem
The FMEA is right on the day you sign it.
Then the process changes, the control plan follows it, and nobody goes back to the analysis the control plan came from.
The floor moves. The FMEA doesn't.
A check gets loosened because it was holding up the line. An operation moves to a different station. The control plan is edited that week. The FMEA it came from is still describing the process you ran at launch.
You find out when someone external asks.
A customer audit, an IATF surveillance visit, a warranty claim traced back to a control nobody was running any more. The gap has been open for months, and it opens in front of the customer you least want to explain it to.
A spreadsheet cannot tell you.
Two files, no link between them, versions on three drives and in somebody's inbox. Even a team that genuinely wants to keep them in step has no way of being told the moment they fall out of it.
How It Works
One link, and the gap cannot open quietly.
The Process FMEA and the control plan it produced are one connected document set, so the two of them cannot drift apart without saying so.
Linked, row by row.
Every detection control on the control plan is attached to the failure mode whose rating it earns. The link is the product itself, not a reconciliation report somebody runs once a quarter.
Flagged the moment they disagree.
Change how a check is performed or how often, and the failure mode that depended on it flags straight away. If the change costs you a Detection rating, the Action Priority moves with it, through the 2019 lookup rather than an RPN.
Reconciled, with the history attached.
One click brings the rating and the wording across from the control plan. What changed, when, and why is written into the change log, which is the part the auditor was going to ask for anyway.
Why Now
Two OEM deadlines, one direction.
Suppliers who have run on Excel for a decade now have a dated reason to move, and it is not a software preference.
The AIAG-VDA cutover.
AIAG's published OEM deployment plan has Honda expecting every PFMEA document in the AIAG-VDA format by January 2027. The first half already landed: since February 2022, new processes, new lines and new parts have had to use it. So most Honda suppliers have spent four years running two formats at once, the new one on new work and the old one on everything else, and 2027 is when the second pile has to be gone.
The living FMEA.
Ford's customer-specific requirements call for FMEA software that keeps linked documents in step, and Ford's criteria for evaluating that software include showing that an update to either the part control plan or the part PFMEA causes the other one to be updated. A spreadsheet cannot demonstrate that. It is the reason this product starts where it does.
Founding Design Partners
Three slots. All of them open.
Kamski is being built with three automotive suppliers. None of the three are taken yet, which is the honest state of things and also the reason to be one of them: the first partner shapes the most.
3 founding slots · 0 takenFree while it is being built
No licence fee during the build. You are not being asked to buy software that does not exist yet, and there is nothing to take to procurement.
Your workflow is the spec
Your parts, your processes, your customer-specific requirements. What your team does every week is what gets built, in the order you need it.
Founding pricing, kept
When Kamski goes paid you keep founding pricing. Terms are agreed on the call, in plain language, not buried in a renewal clause.
A direct line to the person building it
One founder, no account manager, no ticket queue. You describe the problem to the person who writes the code, and you see it in the product.
Common Questions