Ground your AI in knowledge your experts approved

Curate the content your AI assistants and applications depend on, with review, approval and versioning, and keep ownership of your data.

To an AI agent approved data set · master

Can we use the Hamlet summary in our EU catalog?

No. Example Press licenses the summary for non-commercial use only, which excludes a catalog. The EU is a cleared territory, so the license is the only blocker.

Hamletstore:book
License
Editorial, non-commercial
Territories
US, EU
Changeset
44:95f85022
Release
Spring 2026
Example answer grounded in an approved node, with its license and changeset. Illustrative data.

What enterprise AI needs from content

AI answers are only as good as the content behind them, and companies want that content, and what they build on it, to stay theirs.

Accuracy
An assistant that answers from stale or unreviewed documents can be worse than none.
Privacy of data
Business content often can’t leave infrastructure you control for a public service.
Ownership
The data sets, models and endpoints you build on your content should stay yours.
Traceability
When an answer is wrong, you need to find the source behind it and correct it.

How Gitana keeps your AI grounded

Gitana keeps the content behind your AI governed: versioned, approved and delivered incrementally to the systems that use it.

  • Approved data sets

    Reviewed content releases as a data set, with a staging step to test before it goes live. AI assistants called sidekicks draft and tag content, then hand their work back for approval.

  • Private deployment

    Keep source content on your own network by running Gitana and your models together.

  • Your data sets, your endpoints

    Data sets deploy incrementally to the vector databases and LLM endpoints you choose, with the embedding model and vector size you choose.

  • Answers that cite their sources

    Agents point back to the content, license and changeset behind each answer, so a wrong answer can be traced and corrected.

HamletHistory
master spring-catalog Spring 2026

masterspring-catalogRelease: Spring 2026

  1. 44:95f85022Merge spring-catalog into master · 1 conflict resolved in rights.territories
  2. 43:7c21d0a4Edit /summary on spring-catalog · editor
  3. 42:e9a03f61Add EU to rights.territories on spring-catalog
  4. 41:3b5d8e17Add CA to rights.territories on master
The cited changeset, 44:95f85022, is the merge at the top of this history. Example history of one node. Every change is a changeset, and releases promote approved branches on a schedule.

See how Gitana fits your content

In a demo, a solutions engineer walks you through Gitana around your use case. The same call covers architecture, security, deployment and procurement questions.