Built for the mission side of the firewall.

Yes. WE Org runs NURA and keeps it updated, with your data kept separate from other customers at the database. Your agency reviews hosted NURA under its own process, and we provide the documentation for that review. If your mission needs everything inside your boundary, or a disconnected deployment, install NURA in your environment instead.

A Kubernetes environment (or the compute to host one), a PostgreSQL-compatible database tier, and object storage for immutable anchoring, all within your enclave. NURA ships as signed container images with a software bill of materials and a deployment guide. Your evidence, credentials, and CUI never leave infrastructure you control.

Yes. The platform has no license server, no activation callback, and no phone-home dependency, it is fully functional with zero external connectivity. Updates transfer as signed bundles through your approved media or one-way transfer process, verified offline against public keys pinned at installation. One optional AI-narrative feature is feature-flagged off in disconnected deployments while it completes its move to fully in-boundary operation.

With our software out of the trust path. We provide a standalone verification tool, auditable Python, no platform dependency, that takes any evidence record, retrieves its canonicalized content, recomputes the hash locally, and walks the chain to the anchored root. An SCA methodology guide documents the procedure, a sampling approach, and the canonicalization specification, so the verification can even be re-implemented independently. In demonstrations, we ask your team to pick the record.

Connectors use dedicated, least-privilege, read-only service accounts scoped per connector type, with credentials in a secrets vault, never in code or on disk. Agents are outbound-only: they initiate mTLS to the platform and expose no inbound ports, no shell, and no arbitrary execution path, they run only query types defined in a signed task registry. There are no write scopes anywhere in the collection path, and every agent action is itself logged to the evidence chain.

Four extraction paths, chosen per system: database-level read adapters (read-only SQL), file-drop ingestion (scheduled exports, logs, CSV), host-based agent collection, and, for controls no system can evidence automatically, a structured attestation workflow where a named respondent answers a defined question set and the response is sealed into the same chain with the same integrity guarantees. The target system never needs to know OSCAL exists; OSCAL is generated platform-side.

Yes, and by design rather than exception. Categorization and baseline outputs are fully overridable, scope-outs, overlays, compensating and inherited controls, organization-defined parameters, with rationale required at the point of decision. Overrides change scope and interpretation; they never touch evidence. Each override is itself sealed to the chain (who, what, when, why), so mission-specific tailoring increases your audit record instead of weakening it.

The architecture is hybrid, agentless API connectors where targets expose queryable interfaces, lightweight outbound-only agents where host-level presence is needed, on a horizontally scalable Kubernetes platform with a partitioned evidence store. Our honest scale statement: NURA is validated at pilot scale today, and a formal sizing guide with load-test results (resource envelopes per 100 and per 1,000 systems) is a committed deliverable of our pre-deployment engineering program. We won’t assert production scale we haven’t tested, and we’d encourage you to hold every vendor to that.

You do, unambiguously, in the agency-deployed model it is your database in your enclave. Everything exports: evidence as canonicalized JSON with hashes and chain metadata, OSCAL artifacts in standard machine-readable form, assessment and POA&M history in open formats. And because integrity is public math, exported evidence remains independently verifiable after you leave the platform. Your audit history’s trustworthiness does not depend on NURA continuing to exist, which we consider the only honest answer to the lock-in question.