Noukan Industries — homeNoukan IndustriesGmbH · Günsberg CH

Roadmap · Phase 00 building

What you can buy, what you can join, and what is still a plan.

Four things matter before you hand a young company your production line: what you actually receive, what it costs to be early, when you can have it, and what you are exposed to if we stop. Every phase below answers all four — including the ones you cannot buy yet.

The order is yours, not ours: software first because it is the fastest route to a deadline you already have, hardware after, because instrumenting a cell is only useful once something acts on the readings, and pods last, because a pod that cannot be quoted twice is your project with our margin on it.

Your deadlines

The dates that bind you, not us

Regulation (EU) 2024/2847, the Cyber Resilience Act. These are published legal dates under Art. 71, not our estimates. Three of the four are already behind you: if you place a product with digital elements on the EU or EEA market today, the reporting and vulnerability-handling duty is live now, and December 2027 only adds the documentation that has to exist alongside it. The first two phases exist to put that documentation in your hands in front of the date, not after it.

  1. 10 Dec 2024

    In force

    Cyber Resilience Act in force

    Regulation (EU) 2024/2847 enters into force. Products with digital elements sold in the EU are now regulated for security across their lifecycle.

  2. 11 Jun 2026

    Applied

    Conformity-assessment bodies

    The chapters on notified bodies and market surveillance apply, so the assessors who will read your file and the authorities who can demand it are already in place.

  3. 11 Sep 2026

    Binds you today

    Reporting and vulnerability handling

    Manufacturers must report actively exploited vulnerabilities and severe incidents, and handle vulnerabilities in supported products. If you place a supported product on the EU market this quarter, this obligation is already live — the December date below concerns your documentation, not your duty to report.

  4. 11 Dec 2027

    Still ahead of you

    Full application

    The remaining obligations apply, including the technical documentation that has to exist before a product is placed on the market.

One caveat for a Swiss buyer: the obligation attaches to placing a product on the EU or EEA market, not to where your factory stands. A manufacturer selling only into Switzerland has no CRA deadline, and every one of them arrives the moment you start shipping north.

Phases

What each phase does for you

Read the last row of every phase first. A date is a promise we have to keep; an exposure is one you have to accept.

Phase 00

Building now

Q2 2026 — Q4 2026

Not on sale yet.

We are the first customer

Aegis is being built against our own code first, and it has not produced an evidence file for any product yet — ours included. That is the point of doing it this way: the plumbing faults, the false alarms and the awkward release conventions get found on code we own, so your first week is not spent debugging our tooling.

What you get

  • A pipeline that has produced conformity evidence for a shipping product before it ever runs against yours
  • A written map of which Cyber Resilience Act obligations touch your stack, and which do not
  • An honest answer about whether you need a notified body at all

What we ask of you

Nothing yet. This phase is us working on our own code.

What it costs

No cost to you. Phase 00 is work we are paying for ourselves, which is the point: the assumptions nobody pays to test are the ones that fail in your factory.

When you can have it

Not on sale yet, and there is no artefact to show you this quarter. What is open today is fixed-scope engineering and integration work under our registered company purpose.

Your exposure

If we cannot produce the evidence file for our own software, we will not ask you to run the pipeline on yours. That is the condition we set ourselves before charging anyone, and we would rather tell you here than on a call.

Phase 01

Scheduled

H1 2027

Open for conversations now.

Aegis design partners — three places

Aegis runs against your real repository and your real release cadence and tells you, on every merge, where the product is exposed: an unpatched dependency, an undocumented interface, a support period nobody has declared. The file an assessor reads is what that leaves behind at the end of each build.

What you get

  • A build that fails on the security flaw you would otherwise have found in the field
  • SBOM, dependency inventory and licence record produced by each build
  • Vulnerability-handling policy and a coordinated-disclosure record that exists as evidence, not as an intention
  • Technical documentation generated from the release itself instead of written after the fact
  • A declared support period and patch policy per product, which is what the regulation actually demands
  • A file that has been walked through by somebody outside this company

What we ask of you

One product with digital elements, a CI system you control, and roughly one review cycle a month while the pipeline learns your build.

What it costs

Fixed, and published here rather than negotiated: no licence fee and no participation fee for the pilot period. In this phase we are buying your production reality, so you pay in review time and in being told where your documentation was already thin — and the evidence bundle your builds produced stays yours whichever way you decide.

When you can have it

Three places, allocation from January 2027. When they are gone, the next entry point is general availability.

Your exposure

A pilot that flatters us is worthless to both of us. A phase is only called finished when an external walkthrough of the file holds up — if two of the three places do not become paying customers, we say so and change the offer rather than pretend it is a product.

Phase 02

Scheduled

Q3 2027 — Q1 2028

Open for conversations now.

Aegis generally available, ahead of your deadline

You did not need to be early. Onboarding for a product line takes days, and the evidence is there before 11 December 2027 rather than in the scramble after it.

What you get

  • Self-serve onboarding for one product line
  • A licence per product, with the support period you are prepared to defend
  • Evidence export in a format an assessor accepts
  • The same file regenerated on every release, so the next one costs nothing extra

What we ask of you

Your repository, your build secrets, and the release cadence you already have.

What it costs

One published price per product line, fixed and printed on this page before the phase opens — not a number quoted per conversation. No percentage of your revenue, and no per-seat pricing on a pipeline that runs unattended.

When you can have it

Orderable from Q3 2027, priced for the people still buying in 2028 after the deadline panic passes.

Your exposure

Demand for conformity evidence spikes into the deadline and falls away after it. We would rather tell you now that a product built only for December 2027 is a product we would have to abandon, and you would be left maintaining it.

Phase 03

Conditional

2028

Conditional — say so if you want it sooner.

See the failure before the line stops

The cells you already own start telling you when they are degrading, so maintenance lands in a planned window instead of during a night shift. Nothing is replaced and no robot vendor has to co-operate.

What you get

  • Current, vibration, temperature and duty-cycle capture per axis
  • A retrofit mount that survives a full service interval
  • An edge buffer that keeps recording through a network loss
  • A degradation baseline for your machine class, with a stated prediction horizon and a measured false-alarm rate

What we ask of you

Cells you are willing to instrument, and the downtime history you already keep, including the stops nobody wrote down.

What it costs

Hardware plus installation per cell, then a data subscription. Quoted per cell, because a four-axis cell and a palletiser are not the same job.

When you can have it

Field units from 2028. This phase is funded from software revenue instead of a funding round, which is why it is marked conditional: we would rather be a year late than sell you instruments that outlive the company that supports them.

Your exposure

We publish the prediction horizon and the false-alarm rate for the machine class you actually run. If the warning arrives less than two weeks ahead, the schedule does not change and we will not sell it to you as predictive maintenance.

Phase 04

Conditional

2029

Conditional — say so if you want it sooner.

Somebody is accountable for uptime

Unattended running becomes something you can contract for. The maintenance queue fills itself ahead of the failure, and there is a named response time behind it rather than a dashboard.

What you get

  • One view across cells, sites and shift patterns
  • A maintenance queue ordered by measured degradation, not by the calendar
  • An uptime commitment per cell with a response time behind it
  • Firmware and patch state per unit, fed back into the same conformity file as the rest

What we ask of you

A shift pattern where an unplanned stop genuinely costs something, and agreement on what counts as downtime.

What it costs

Subscription per cell or per site. The uptime commitment is the thing you are paying for, and it is the number we are liable against — capped at the annual fee for that cell, with the exclusions named in the contract rather than found later in it.

When you can have it

Two installations running unattended shifts first, with the response time written into the contract before it is offered generally.

Your exposure

If you still keep someone on site for reassurance, the software has only reported the risk rather than removed it. That counts against us, not against you, and we would rather lose the renewal than argue about it.

Phase 05

Direction

2030 and beyond

Direction, not an offer.

Lights-out capacity you can order twice

Unattended production becomes a purchasable unit instead of a capital project. You get a price, a lead time and an uptime figure before you sign, and your bank can read all three.

What you get

  • A pod: cell, robot, capture kit, fleet software and maintenance in one line item
  • A standard interface for power, air, network and material handling
  • Maintenance priced against measured uptime rather than a time-and-materials guess
  • A second unit that costs less than the first, by design

What we ask of you

A part you intend to make for longer than a product cycle, and the floor space.

What it costs

One quoted price per pod, financed as equipment. Maintenance is a subscription, so the cost of keeping it running is visible at the moment you decide to buy it.

When you can have it

This is direction, not an offer. Nothing here should be load-bearing in a 2027 investment decision.

Your exposure

The first pod is engineering and we will price it like that. We only claim a pod product once the second one can be quoted from a sheet — if it cannot, buy the project from an integrator instead and pay less.

Before you plan around this

What a roadmap like this does not promise

Dates move. The regulatory dates are fixed and published. The phase windows are estimates from a small company that has never shipped hardware, and Phase 03 onward is conditional by design rather than scheduled.

The order can fail, in a way that matters to you. If the compliance pipeline ends up a service business, the capture kit still makes sense and the pods probably do not. Do not write a 2027 capacity plan that assumes a 2030 pod exists.

There are no references yet. No customer logos, and no funding round behind us either. Phase 00 is our own money; from Phase 01 onward every phase is paid for by a customer before the next one gets built, so nothing above is a speculative roadmap. It makes us slower than a funded competitor and it is the reason we will not sell you a phase we cannot support.

Ask about a phase