Noukan Industries GmbH · Günsberg, Switzerland
A factory that runs in the dark still has to be patched, maintained and proven.
Three things stop manufacturers from going lights-out: security obligations they can show but not evidence, maintenance that depends on somebody standing there, and integration work that cannot be priced twice. Noukan Industries is building those three layers — in that order.
- Status
- Phase 00 — building
- Next gate
- Design partners, H1 2027
- Documentation deadline
- 11 Dec 2027, EU/EEA market
The gap
Lights-out manufacturing is a maintenance problem, not a robot problem
The robots already work. What is missing is everything around them: the evidence that the software is safe, the warning before a spindle dies, and a unit of capacity a bank will finance.
What we are building
Three layers, sequenced so each one pays for the next
Nothing here has shipped except the company itself. Each layer below is dated, and the roadmap states the condition under which we stop.
Position, stated plainly
Aegis is a development tool. The file is what it leaves behind.
You do not buy Aegis in order to be certified. You buy it because every merge tells you where the product is weak — a dependency nobody is patching, an interface nobody documented, a support period nobody has declared — while the fix costs an hour rather than a recall. Most products with digital elements reach conformity through internal control without a notified body, and what an assessor asks for there is not a logo on a datasheet.
So the conformity file is a byproduct of developing this way, not the product. A certificate records that somebody paid for an assessment in March; a pipeline that regenerates the file on every merge records that the process ran, which is the thing the regulation actually asks for. Where a product genuinely falls into an important or critical category, that same evidence is what makes a notified-body assessment survivable, so the work is never either/or.
The obligation bites when a product is placed on the EU or EEA market, which includes products built in Switzerland and shipped north. Product category then determines the conformity procedure: check Annex III and Annex IV of Regulation (EU) 2024/2847 before assuming self-assessment applies. This is our reading of the regulation as a software vendor, not legal advice.
How we work
Four rules we would rather be judged on
01
Find the flaw at the merge
A defect found in the commit that introduced costs an hour; found in the field it costs a recall, and found at an audit it costs a market. We optimise for the first one, and the conformity file is what that habit leaves behind.
02
Evidence over slides
Every claim on this site that is not dated has a phase, a price and a stated reason we would stop building it. Nothing is offered as a photograph of a process on the day it was taken.
03
Standardise or stop
The first unit is engineering. Anything we cannot quote twice from a sheet we do not sell as a product, however good the project is.
04
Measure before automating
Dark factories fail on unplanned downtime, not on robotics. We instrument the cell before we propose removing the person watching it.
The company
Registered, small, and honest about which parts are future
- Legal form
- GmbH (limited liability company) under Swiss law
- Registered
- 12 June 2026
- Seat
- 4524 Günsberg SO, Switzerland
- UID
- CHE-130.523.906
- Register number
- CH-241.4.027.046-6
- Share capital
- CHF 25,000.00
Building something that has to run unattended?
We are taking a small number of design partners for the compliance pipeline in the first half of 2027. Bring a real product and a real CI system.