Reference architecture
Why the wire stays cut.
A thirty-second look for a firm that will only run its own models, on its own machines.
30-second teaser
The model is elsewhere.
Caption. Beat 1 of 5. An analyst pastes the firm's own records into a cloud chat, or sends them through a model API. The prompt leaves the building.
Reference architecture. TrueNorth does not run this, and it is not a certification.
Text version
- An analyst pastes the firm's own records into a cloud chat, or sends them through a model API. The prompt leaves the building.
- This firm will not connect a cloud language model, a vendor chat, or a model API.
- Custom models run only on machines the firm owns. There is no network path to a model provider. The corpus is that firm's data.
- New data arrives on a thumb drive, or as a manual copy onto the drive. Nothing is fetched over the network.
- The brief under the film says whether this design fits, how a team would install it on the firm's machines, implement it on the firm's data, and configure updates that arrive by hand. A name and firm asks for the install. Sending it does not schedule the work.
This page is a reference architecture for air-gapped, on-prem models, and the standard we build toward. TrueNorth does not run this system. There are no air-gapped machines in the product, and TrueNorth is not certified for IL5, IL6, HIPAA, or FINRA. It is a different design from zero-egress analytics, which is a logical boundary and not a claim that a network is physically air-gapped.
Zero-egress analytics is a different reference. That design lets pixels leave a logical boundary. This one does not connect a model at all.