Start with the boundary.
Nomiarch is an open source trust and authorization platform in development. The goal is to keep infrastructure and AI within the conditions an organization has approved.
The portable core and desktop wizard are implemented. Start with the installation guide for packaged preview availability, requirements and upgrade steps. The architecture pages also describe future capabilities; this is not a production release.
Choose a starting point
Architecture
How local AI, independent policy, bounded execution, and evidence fit together.
02 / THE FIRST DEPLOYMENTGet started
Download the kit, install a local VM, verify it and upgrade through the same wizard.
What the platform is for
Platform and cloud engineers need a way to connect a security finding to a controlled change, then give reviewers evidence that the deployed state was checked. AI introduces another question: who decides what an agent is allowed to do?
The proposed platform observes an environment, reasons about deviations, authorizes permitted actions, coordinates repairs, independently checks the result, and records evidence. Policy enforcement sits outside the model.
Start narrow. Preserve the larger design.
A future remediation scenario focuses on one Azure Storage account in a test environment in Canada Central. The target setting is allowBlobPublicAccess=false. The intended flow lets local AI propose the repair and separate authorization, execution, and verification services complete the loop. The current preview checks submitted sample configuration; it does not write changes to Azure.
The broader vision includes conventional workloads, additional clouds and on-premises infrastructure, AI tool admission, sovereignty profiles, and disconnected deployments. These remain future directions.
The principles behind the design
- Intelligence and authority are separate. Model output alone cannot grant permission to act.
- Approval describes an exact change. A modified proposal must be evaluated and approved again.
- Deployed state is checked independently. An executor reporting success is insufficient.
- Evidence stays useful locally. The intended runtime should not depend on an external SaaS evidence service.
- Deployment conditions are explicit. A private VM, Canadian hosting, and a physical air gap provide different guarantees.
How to follow development
The roadmap separates the current design from the planned prototype and reproducible release. The Get started page includes commands, expected results and explicit validation limits.
Design documentation · Updated 15 September 2026 · Nomiarch · Architecture in development.