Does PolicyCortex make us compliant?

No. It produces the records compliance decisions rest on. The authorizing official, the C3PAO, or the accountable official makes the determination; PolicyCortex hands them evidence they can recompute instead of a narrative they have to believe.

Where does the data live?

In the customer's own tenant. There is no telemetry pipeline to PolicyCortex servers and no egress of evidence.

How is evidence verified?

By recomputation. Every record is SHA3-256 hashed over its content plus the digest of the record before it. Export the stream, recompute, compare: intact, or the exact sequence number where integrity fails. No PolicyCortex account or API is needed.

What happens when a collector is down?

The chain carries a declared gap: the stream, the interval, the reason, and when it was declared. Evidence never silently has fewer rows.

The platform, in plain language.

What is PolicyCortex?

PolicyCortex is a compliance and assurance platform for regulated cloud and AI systems. It connects requirements, control implementation, remediation, and verifiable evidence in your tenant, helping your organization prepare for self-assessment, independent assessment, and authorization review, and maintain readiness as systems change.

Request Access How it works

Access is reviewed. Scope and onboarding are agreed with your team.

Who it is for

Security, compliance, and infrastructure teams responsible for regulated systems. You may be establishing your first program, closing gaps in an existing implementation, preparing a review package, or keeping an authorized system ready for its next assessment. PolicyCortex connects that work to the evidence behind it.

WHO-01
Defense contractors pursuing CMMC and managing CUI
WHO-02
National laboratories under DOE and NNSA
WHO-03
Federal agencies
WHO-04
Defense Industrial Base organizations
WHO-05
Regulated commercial environments running autonomous systems

FOR-01
ATO and continuous authorization
FOR-02
CMMC Level 2, the 110 requirements of NIST SP 800-171
FOR-03
FedRAMP 20x
FOR-04
NIST SP 800-53 Rev 5 and NIST SP 800-171
FOR-05
OMB M-25-21 AI use-case inventories and minimum risk management practices

Licensed software with access arranged through our team; fixed-scope delivery engagements are optional. The pricing page describes the license; the engagement page describes the optional delivery work.

What it produces: three proofs

Everything PolicyCortex exports is a projection of three records, kept on one hash chain inside your tenant. Each is stated here in one paragraph; each has a page of its own.

PROOF 01 / STATE

Proof of state

Proof of state is a point-in-time record of cloud configuration, taken from the cloud provider APIs, content hashed with SHA3-256, chained to the previous record, retained for seven years, and regenerable to any timestamp a second party picks. It answers what was true in the environment on a date somebody else names, not what is true now.

Read the record PROOF 02 / CHANGE

Proof of change

Proof of change records who or what altered the environment, under what authority, with before and after state hashes, the hashed delta, the policy gates that ruled, and a rollback identifier, committed to an append-only chain that administrators cannot edit without detection. Changes made around the gates surface at the next capture as drift with no authority attached.

Read the record PROOF 03 / AGENCY

Proof of agency

Proof of agency holds three artifacts for every autonomous action: the envelope that permitted it before it ran, the chained record of what it did, and the counterfactual showing what would have blocked it had it been one notch different. Envelope versions are records, so the authority in force at 02:14 comes from the chain, not the current settings page.

Read the record

The PolicyCortex evidence package export: assessor-ready ZIP with complete evidence inventory, validation results, POA&M items, SSP, SAR, OSCAL and eMASS formats, and AES-256 protection — The assessor-ready package all three proofs ship in: inventory, validations, POA&M, SSP, SAR. One ZIP, hash chained, AES-256 protected. Illustrative demo data; the interface is real.

What it is not

PolicyCortex states its limits as plainly as its claims. Four things it is not.

Stated limit

NOT-01
Your team owns the program. PolicyCortex connects controls, remediation, and evidence. Your organization implements its policies, assigns responsibilities, and makes its risk decisions. Optional delivery engagements provide support for that work.
NOT-02
Not a certifier. PolicyCortex is not a C3PAO and does not certify anything. The assessor remains the authority on what passes, and the authorizing official remains the authority on what operates.
NOT-03
Preparation is not a determination. Readiness tracking and a generated package support review. Meeting the applicable requirements and receiving any required assessment or authorization remain separate responsibilities.
NOT-04
Not a scanner and not a chatbot. It is an evidence system. The AI inside it can only propose; a policy gate rules before it reasons, a formal proof checks after it drafts, and a rollback identifier exists before anything is touched. Every handler that can change your estate ships a matched captureState and restoreState pair, and the runtime refuses to execute an action whose rollback path is undefined.

How it compares with Vanta, Drata, Wiz, Prisma Cloud, RegScale and GCC High is answered by the same eight questions on the comparisons.

How to get access and verify it

Request access so we can review your environment and agree on scope and onboarding. After access is approved, a read-only connection in SHADOW mode can produce state records and declared gaps inside your tenant. Nothing executes. Verify the chain yourself: export the stream, recompute SHA3-256 over each record plus the digest of the record before it, and compare.

access: Read only. We do not need write access to show you something.
onboarding: Access is reviewed. Scope and onboarding are agreed with your team.
trust.mode: SHADOW. The reasoning layer proposes and publishes confidence; zero actions are executed.
location: Your tenant, including AWS GovCloud, Azure Government, and GCC High. On-premises delivery for air-gapped environments is available.
egress: None. There is no telemetry pipeline to PolicyCortex servers and no egress of evidence.
you.get: State records, declared gaps, and a chain you can recompute without a PolicyCortex account or API in the loop.

Request Access Book a founder call

The vocabulary, defined once

Seven terms this site uses. The same definitions are published for machines in llms-full.txt.

Proof of state: A point-in-time record of what a cloud environment was, captured from the provider APIs, content hashed, chained to the record before it, regenerable to any date inside retention.
Proof of change: Who or what altered the environment, under what authority, with before and after state hashes and a rollback identifier, on a chain that cannot be edited without detection.
Proof of agency: What a machine was permitted to do before it acted, what it actually did, and what would have stopped it one notch different.
Declared gap: An explicit chained entry, with interval and reason, written whenever a collector is down or a scope is unobserved. Absence is recorded, never inferred from fewer rows.
Autonomy envelope: A machine-enforced object read before every autonomous action: allowed and blocked action types, maximum affected resources, minimum published confidence, cost ceiling, excluded environments, change windows, emergency stop. Every evaluation of it is a chained record.
Trust modes: SHADOW (watch only, nothing executes), GATED (default; a named human approves each action and becomes part of its record), AUTONOMOUS (narrow, well-tested action classes, every gate still run on every act).
Register: A page or evidence stream whose visible copy is the input to its own SHA3-256 hash chain, so a second party can recompute it.

Five questions, answered plainly

Q-01
What is PolicyCortex?
PolicyCortex is a compliance and assurance platform for regulated cloud and AI systems. It connects requirements, control implementation, remediation, and verifiable evidence in your tenant, helping your organization prepare for self-assessment, independent assessment, and authorization review, and maintain readiness as systems change.
Q-02
Does PolicyCortex make us compliant?
No. It produces the records compliance decisions rest on. The authorizing official, the C3PAO, or the accountable official makes the determination; PolicyCortex hands them evidence they can recompute instead of a narrative they have to believe.
Q-03
Where does the data live?
In the customer's own tenant. There is no telemetry pipeline to PolicyCortex servers and no egress of evidence.
Q-04
How is evidence verified?
By recomputation. Every record is SHA3-256 hashed over its content plus the digest of the record before it. Export the stream, recompute, compare: intact, or the exact sequence number where integrity fails. No PolicyCortex account or API is needed.
Q-05
What happens when a collector is down?
The chain carries a declared gap: the stream, the interval, the reason, and when it was declared. Evidence never silently has fewer rows.

Request access to review your scope and verify the record.

Request Access