Federal capability.
11/11 AI builds Execution Governance: per-request authorization and cryptographic proof for autonomous systems. Before an autonomous action executes, our control plane evaluates identity and policy and decides whether it is permitted. Permitted actions execute and are recorded with a signed evidence root and append-only audit lineage. Non-permitted actions fail closed.
Entity information
Registered and active.
- ✓ Legal name: 11 AI & Blockchain Development LLC
- ✓ Doing business as: 11/11 AI
- ✓ UEI: GHEZH441JN51
- ✓ CAGE: 1A1G9
- ✓ DUNS: 144921555
- ✓ SAM.gov: Active registration
- ✓ Business size: Small business
- ✓ Registered office: 30 N Gould St Ste R, Sheridan, WY 82801
Codes
NAICS and PSC.
- ✓ 541511 Custom Computer Programming Services
- ✓ 541512 Computer Systems Design Services
- ✓ 541519 Other Computer Related Services
- ✓ 541715 Research and Development in the Physical, Engineering, and Life Sciences
- ✓ 513210 Software Publishers
- ✓ D302 IT and Telecom, Systems Development
- ✓ D310 IT and Telecom, Cybersecurity
- ✓ D399 IT and Telecom, Other
Standards and policy alignment
The control, and the requirement it meets.
| Control we provide | Standard or policy requiring it |
|---|---|
| Per-request authorization before execution | NIST SP 800-207; DoD Zero Trust target architecture |
| Runtime governance of autonomous agents | NIST AI RMF, Measure and Manage |
| Signed evidence root and chained audit lineage | OMB M-25-21 transparency and risk determinations |
| Fail-closed default for high-impact action | OMB M-25-21 minimum practices for high-impact AI |
| Accountability over autonomous action | 10 U.S.C. 130h |
| Post-quantum signatures in production | CNSA 2.0; FIPS 204 (ML-DSA-87); FIPS 205 (SLH-DSA-SHA2-128f) |
Cryptographic posture
Cryptographic primitives
Named cryptography, in full.
- ✓ Ed25519 (EdDSA) FIPS 186-5
- ✓ ML-DSA-87 FIPS 204, post-quantum, in production
- ✓ SLH-DSA-SHA2-128f FIPS 205, post-quantum, in production
DECISION LAYER
- ✓ SHA-256 FIPS 180-4
- ✓ SHA-512 FIPS 180-4
EVIDENCE STATE, CONTROL PLANE
- ✓ SHA-512 FIPS 180-4
AUDIT AND LINEAGE CHAIN
- ✓ SHA3-512 FIPS 202
- ✓ BLAKE2b-512 RFC 7693
BLAKE2b-512 is not a FIPS-approved algorithm. It is used only in the audit and lineage chain, alongside SHA3-512, which carries the tamper-evidence claim there. The decision record and the control plane evidence state are hashed with SHA-256 and SHA-512 under FIPS 180-4. An approved-algorithm-only mode is available for federal deployment.
Our signature algorithms and primary hash algorithms are FIPS-approved. BLAKE2b-512 is not, and we state that plainly rather than leave it implied. Module-level FIPS 140-3 validation is on our roadmap and not in hand today.
- ✓ NIST SP 800-207 Zero Trust Architecture: per-request authorization applied to non-person entities
- ✓ NIST AI RMF: Measure and Manage functions
- ✓ OMB M-25-21: minimum risk management practices for high-impact AI
- ✓ CNSA 2.0: post-quantum signature algorithms deployed today
Independent verification
Verifiable without our involvement.
Our technical claims are verifiable without our involvement. The control plane is live with a public proof endpoint and an open-source reference verifier.
Published doctrine
Eight principles, each with a permanent DOI.
Sovereign and regulated compute
For the operators who run the data centers.
AI is moving from answering to acting. Systems running in modern data centers increasingly move funds, change records, and take real-world actions on their own. Compute and models advance fast. The control over what that AI is allowed to do, and the proof of what it did, has been missing.
11/11 AI is not a compute or data-center provider. It is the authorization and proof layer that sits on top of compute and models. The operator owns the facility and the economics. 11/11 governs what runs inside it.
Compute
Capacity. Owned and operated by the facility.
Models
Intelligence. Chosen by the tenant.
Governance
Authorize, enforce, prove. Model-neutral and vendor-neutral, so it works across any tenant's stack.
An offering a prospective tenant can test rather than take on trust: pre-execution authorization, and a public proof surface they can check themselves before signing.
Sold on governance rather than on racks and power. It is a different conversation from price per megawatt.
Addresses buyers who increasingly ask for provable controls over autonomous actions rather than assurances about them. Tenant-scoped isolation: every artifact binds to a tenant at issuance.
Signed, timestamped records of what was authorized and what actually ran. That is the artifact auditors, regulators and insurers ask for when they ask how a control was enforced.
11/11 AI does not own, operate, or resell compute, and takes no data-center economics. The public proof ledger reports its own coverage and this page does not claim more than it reports. A portion of the corpus predates the field that makes an evidence root recomputable, and those roots cannot be recomputed by anyone, including us. /v1/public/proof-ledger gives the live counts. Post-quantum signature status is reported by the signer. Independently verified in the reference path: Ed25519.
Current stage
Stated plainly.
Founder-led and pre-revenue at TRL 6. Federal accreditation is on our roadmap rather than in hand. We state this plainly so an evaluator knows exactly what is proven and what is next.
Capability statement
One click, no gate.
Contact
Bradley B
Founder and Architect