---
title: "The Company: PolicyCortex, Inc."
description: "PolicyCortex, Inc., Dallas-Fort Worth. Built where evidence falls apart and the answer matters: federal R&D, defense, financial services, aviation."
url: https://policycortex.com/company
sealed: 2026-08-31
amended: 2026-09-06
register: company
records: 4
digest: sha3:323107bfba04a485b8bc73c7399be371b23bd4b8cb3a118981bf141ee7c844ba
---

# Built by people who had to answer these questions.

Company

PolicyCortex, Inc., Dallas-Fort Worth, Texas. One U.S. nonprovisional utility patent application pending. Active DoD and DoE clearances. This page is the company's own evidence record: origin, entity facts, and the gaps we declare about ourselves.

**In one paragraph.** PolicyCortex, Inc. is a Dallas-Fort Worth, Texas company founded and run by Leonard Esere, who holds active DoD Secret and DoE Q clearances. One U.S. nonprovisional utility patent application pending. SAM registration is active under CAGE 19CQ3. No sales organization sits between you and the engineers who build the system; every engagement is delivered by the people who wrote the code.

[Request Access](https://app.policycortex.com/auth?mode=request-access) · [Read the delivery record](https://policycortex.com/track-record)

## Why we built this

Before this company existed, we sat in rooms where the answer mattered: federal R&D, defense engineering, financial services, aviation. In those rooms we watched evidence fall apart. Systems that could produce ten thousand log lines could not answer what was true as of a given date. Machines that had changed production could show what they did, but not what they had been allowed to do. And nobody could verify any of it without trusting the operator.

Logs and evidence are different words. A log is whatever a system happened to write down. Evidence is a record built to be checked by someone who does not trust you: content-hashed, chained in sequence, timestamped, with its gaps declared instead of hidden. The distance between those two words is where audits stall and authorizations die. PolicyCortex exists because nobody should have to rebuild that record from memory, in the room, while the assessor waits.

## Who we are

The company, stated as fields. Everything below is checkable against SAM.gov, USPTO filings, or a direct call.

- **entity.name**: PolicyCortex, Inc. The product and the company share the name.
- **entity.location**: Dallas-Fort Worth, Texas.
- **leadership**: Leonard Esere, founder and chief executive.
- **clearances**: DoD Secret and DoE Q, both active.
- **experience**: DOE national laboratory (active consultant), MITRE, USAA, Frontier Airlines.
- **ip.patents**: Patent pending for evidence-grounded, provider-aware cloud governance remediation and continuous authorization.
- **gov.registration**: SAM registration active. CAGE 19CQ3.
- **contact.direct**: [gov@policycortex.com](mailto:gov@policycortex.com)

## The operating principle

The product has one rule for missing data: when a collector is down or a scope is unobserved, the record carries an explicit gap entry with the interval and the reason. It never shows silently fewer rows. We hold the company to the same rule. Every page on this site that states what the product does also states, in plain sentences, what it does not do. The limits are part of the record, not fine print.

The stated limits for the system itself are on the architecture page. [Read the architecture and its stated limits.](https://policycortex.com/architecture)

**Declared gap.** There is no sales organization and no customer success layer between you and the engineers who build the system. Every engagement is delivered by the people who hold the clearances and wrote the code. If your procurement process requires those intermediary layers, that is a gap we declare here rather than one you discover later.

## Related records

- **record.founder**: [Leonard Esere: background, clearances, and prior work.](https://policycortex.com/about-leo)
- **record.delivery**: [Delivery history: where this has run and what it produced.](https://policycortex.com/track-record)
- **record.procurement**: [Procurement: SAM registration, CAGE code, and how to buy.](https://policycortex.com/procurement)

Inspect the system with the engineers who build it. [Request Access](https://app.policycortex.com/auth?mode=request-access)

## Register colophon

| Seq | Label | SHA3-256 | Prev |
|---|---|---|---|
| REC 0000 | ORIGIN | bb75caf4db23 | ec97bf34ae8e |
| REC 0001 | ENTITY RECORD | 83a3e901fbd9 | bb75caf4db23 |
| REC 0002 | OPERATING PRINCIPLE | 49016fcd4ca4 | 83a3e901fbd9 |
| REC 0003 | CROSS-REFERENCES | 323107bfba04 | 49016fcd4ca4 |

Head sha3:323107bfba04a485b8bc73c7399be371b23bd4b8cb3a118981bf141ee7c844ba. Each digest is SHA3-256 over the previous digest, the register key, the record label, and the record copy; a second party can recompute it from this document.