Open Enterprise Beta

Start here. Run your own when you're ready.

chandrahub.net is the open beta for the Chandra governed deployment network. Organizations getting started with Chandra connect here. Organizations running Chandra at scale run their own chandrahub instance — the topology is decentralized by design.


What chandrahub is.

Chandra is an open protocol for append-only, hash-chained, attributed audit records. Every act — every human decision, every agent action — produces a record at the moment it occurs. Immutable. Attributed. Hash-sealed to its predecessor.

A chandrahub instance is the governed deployment network for a forest of Chandra deployments. This instance is the open beta — the entry point for organizations evaluating or beginning their Chandra deployment. When you are ready to run sovereign infrastructure, you run your own chandrahub.

The record is not a receipt. It is produced simultaneously with the act it records.

Find what you need.

For regulators
Examiner Reference
Verify GABA certs, read CUs, trace audit opinions to work papers. No prior Chandra knowledge required.
For auditors
Auditing with Chandra
SSAE 18 engagement types, governed work papers, opinion issuance, chain of custody.
For organizations
Being Audited
What your audit trail contains, how to produce evidence for examiners, retention policies by standard.

The examiner reference lives here permanently.

Regardless of where a Chandra deployment runs — on this instance or on a sovereign chandrahub operated by the organization itself — chandrahub.net is the stable public reference. It is the URL that goes on GABA certs. It is where examiners start. It does not move.

The examiner reference is written for regulators and auditors who have never encountered Chandra. Plain language. Explicit verification steps. A full glossary mapping Chandra terms to standard audit vocabulary. A direct line to General Reasoning for anything the document doesn't cover.

Any Chandra deployment. Any examiner. One reference.

One column addition. Full audit coverage.

Integrating an existing application with Chandra requires one column addition per auditable database table. No schema redesign. No audit middleware. No separate compliance system. Every write your application makes appends a context unit to the corresponding Chandra chain. The chain is the compliance record.

The open beta is the starting point. Enterprise inquiries and deployment support: inquiries@genreason.com

Examiner reference Integration guide

General Reasoning, Inc. · Birmingham, Alabama · 2026
Enterprise inquiries: inquiries@genreason.com
Page integrity: Pending chandrapassport deployment — CU verification active post-launch.