Industries · Defence and Aerospace
The design can’t leave the country. Your AI shouldn’t either.
Northwood deploys and operates Oak for teams that build vehicles, sensors and systems for defence and space: chat, search and agents over your designs, test data and code, in your cloud region, on your servers or fully air-gapped.
Why it matters
Your security officer is right.
Defence and aerospace teams work from material they can’t share: controlled technical data, test results, source code and customer program files. Export rules and contract terms decide who may see it and where it may sit, so it can’t go to a public AI tool.
Northwood deploys Oak inside the environment you approve, with each program walled off, outbound traffic denied unless you name an exception, and every question logged to a named user.
Use cases
Where defence and aerospace teams put Oak to work.
Engineering knowledgeAsk across specs, design reviews and test reports. Each answer cites the document and its revision.
Test campaign reviewSummarize a test campaign from its reports and logs, with every finding traced to its source.
Code and firmwareGive engineers answers from your own repositories. The code stays in your environment.
Proposal draftingDraft proposal sections and compliance matrices from your own past work, reviewed by a named person before they go out.
Controls
What stays true in every deployment.
Data stays in the region you approve.
Air-gapped installs for isolated networks.
Each program is walled off from the next.
Deployment
Your cloud, your servers, or no connection at all.
Your cloudOak runs in your own cloud account, next to the data it reads.
Your serversRun Oak on hardware you own, in your data centre or your office.
Fully air-gappedNo outside connection. Models, search and logs all run locally.