A young product, and a published list of its limits.

One: sovereignty is a constraint, not a preference. For a growing number of organisations, the sentence “the architecture model cannot leave our infrastructure” is not a negotiating position. It is the decision. A product that treats that as an edge case will always be a poor fit for them.

Two: a tool that overclaims compliance is worse than no tool. A dashboard that reads compliant and cannot say how it knows will be believed right up to the moment somebody asks. The architect is the one holding it at that moment. So Noveam renders a gap as a gap, and the highest thing it will ever say about its own coverage is modeled.

Noveam is written in Rust. The workspace carries 752 test functions and 60 browser test cases across 21 specification files and four browser profiles, including mobile. The commit gate is build, test and lint with warnings treated as errors — a change that produces a single compiler warning does not land.

Noveam is a young product and this page says so, because you would find out anyway.

What that buys you: the appliance runs with the network unplugged, your entire dataset is a database file you can copy, and the model exports as CSV, JSON, XLSX and OSCAL. There is no proprietary cloud state to be stranded in, and no migration to escape from.

The counter-offer is a pilot on your own hardware, on your own data, with a defined exit. If it does not hold up, you have lost a pilot, not a platform.