One site, ninety days, no connection out.
Run Kernwall OS on your own hardware before general availability. You bring one site and one workload, and Kernwall builds the first release against your rules. Five sites, EU fabs and manufacturers first.
Who it's for
Your data can't leave. Your auditor will ask.
Three profiles for the first cohort. Fabs and factories come first, where the founder has built before. Defense suppliers join where the timeline allows.
- 01 · First cohort focus
Semiconductor fab
- Network
- Isolated fab and OT zones; engineering data stays on site
- First workload
- Engineering copilot over SOPs, recipes and equipment manuals
- SEMI E187
- IEC 62443
- NIS2
- 02 · First cohort focus
Tier-1 manufacturer or machine builder
- Network
- Segmented OT network, often with no route to the internet
- First workload
- Visual inspection at the line, or a shop-floor voice agent
- IEC 62443
- Machinery Reg.
- CRA
- NIS2
- 03 · Case by case
Defense supplier in a NATO country
- Network
- Fully air-gapped or classified, e.g. VS-NfD
- First workload
- Document and procurement analysis on a restricted network
- BSI VS-NfD
- CMMC
- ITAR
Target profiles, not customers. No site has joined the programme yet.
Eligibility
A good fit, and an honest not-yet.
One short call settles it either way.
- Your network rules forbid or tightly restrict outbound connections
- You can name the first workload and the people who would use it
- You have GPUs on site, or budget for one to three nodes
- Someone in security or OT will review the evidence pack with us
- Your site is in the EU or a NATO country
- You need production next month: the first release is built during the pilot
- You want a managed cloud service, or a vendor holding the keys
- Your workload needs a closed frontier model; Kernwall runs open-weight models only
- You run US classified work at cloud scale: a hyperscaler's air-gapped region fits better today
The first call
Thirty minutes, no slides.
We come to listen, not to demo. Here is every question we ask, so you can bring the right person and the answers you have.
- Tell us about the last time someone asked to use an AI model on production data. What happened?
- Where does that data live, and what stops it from leaving today?
- Who would have to sign off on a box like this, and what would they ask for first?
- How do you patch an isolated machine today? How long does it take, and who carries the USB stick?
- If a model or driver update broke something, how would you know, and how would you roll back?
- What would you need to see in 90 days to keep going?
- Where would a 90-day pilot land against your budget, and against a consultant?
- Who else at your site should hear this?
If you run a fab or build its tools, we ask one more: is SEMI E187 or E188 in your purchase terms, who checks it, and is an on-box anti-malware agent mandatory? The SEMI E187 mapping
How the pilot runs
Three steps to an appliance inside your walls.
The Proving Ground is a paid pilot with a fixed scope. If you continue, Kernwall credits it to year one.
- 01
- 02
Scoping
Hardware, models and the evidence your assessor will ask for, written down.
- 03
90-day on-site pilot
The appliance runs inside your walls, with no connection out.
- Length
- 90 days on site
- Scope
- One site, 1–3 nodes, two use cases
- Network
- Runs with no outbound connection; updates cross the gap as signed bundles
- Discounted pricing for the first cohort
- A seat in roadmap decisions
- A named engineer for your site
- A quarterly on-site visit
- A named site contact and one feedback call a fortnight
- Your assessor's questions, as early as you have them
- A reference only with your written consent, anonymised by default
Deployment
Loading dock to evidence pack in six weeks.
A design target for your first site. Every step happens inside your building, and nothing needs the internet.
The appliance arrives sealed
Rack it, power it on, leave the network cable out. Before anything else, the box proves it booted the image that left the factory.
Site initialised
One command creates your site signing key, seals the data volume to the measured boot, links your directory and arms the egress audit.
First model served offline
You carry a signed bundle across on USB or a data diode. Kernwall OS verifies it, scans it again and re-signs it with your site key, then serves it on an OpenAI-compatible endpoint.
Answers grounded in your documents
Index the SOPs and specs already on your file shares. Access rules carry over, so your people only get answers from documents they could already open.
Evidence pack for your assessor
Kernwall OS exports the evidence it has written since day 0. You still hold the accreditation; the pack is designed to shorten your path to it.
Book a demo
See it run on your hardware.
Four fields and a note. We set up the demo around your workload.
Kernwall OS is pre-release, and every certification is planned on a dated roadmap. In your pilot, Kernwall builds and proves the first release on your hardware, against your assessor's questions.