CogniGraph / Enterprise

Evidence in.
Signed facts out.

CogniGraph Enterprise adds governed knowledge construction to the database: facts built from text that keep their evidence, construction rules a reviewer can read, and a signed chain from policy to release. For teams that will be asked how a relationship entered the graph, and who let it.

01 / From text to a stored fact

Keep the evidence attached.

Retrieving a stored relationship is only part of the problem. In an investigation or research workflow, a reviewer may also need the passage supporting it, the construction policy and the authority behind a release.

  • Evidence-bound construction. Facts created through the governed construction workflow retain source-chunk references and UTF-8 evidence spans.
  • Semantic Neurons. Reviewable construction rules and deterministic gates help control which proposed relationships may be grounded. Evaluation measures recall and restraint.
  • Signed governance. Separate policy, approval and promotion roles provide an attributable path through evaluation, artifacts and deployed generations.
  • Multi-tenancy. Enterprise supports more than one tenant per server, with tenant-scoped operational boundaries.

The pipeline is built to refuse: a proposed relationship that fails its gate is recorded as refused, not quietly dropped, and never becomes a fact by assertion alone.

02 / A useful evaluation

Bring a question you can check.

A useful trial starts with representative documents, a defined set of permitted relationships, independent reference labels and named reviewers. Agree on how to measure both useful findings and relationships the system should refuse.

Scope it to what ships: a single-writer deployment today, with replication and failover on the roadmap, and research-grade evidence rather than clinical qualification.

03 / Choose the right scope

The database. The governance.

Current edition boundaries; the license texts govern
CapabilityCommunityEnterprise
Native storage, CGQL, search, Lua, auth and toolsIncludedIncluded
Governed construction and signed governanceNot includedIncluded
More than one tenant per serverNot includedIncluded
Production termsFree under FSL for permitted usesWritten commercial agreement required
Read replicas and standbyRoadmapRoadmap

Community uses FSL-1.1-Apache-2.0. You can build commercial applications on it under the license terms; offering CogniGraph itself as a competing database product or managed service is restricted. Each Community version gains an Apache 2.0 grant two years after its release.

Enterprise is available now for evaluation, development, testing and demonstration. Production use runs on a signed commercial agreement; the published license text is the draft that agreement is based on.

04 / Start a conversation

Show us the hard question.

Tell us which documents you work with, which relationships matter and what your reviewers need to establish. Include the deployment constraints and the evidence you would need from an evaluation.

Talk to the people building it.

Contact Gedank Rayze about Enterprise evaluation, integration or commercial terms.

Go to Contact