Introduction - Nitsor documentation

Available now Nitsor is version control for 3D AI inspection data, and the system of evidence for AI-assisted inspection. It is pre-release. These pages describe the product precisely and say, on every page, how much of it you can use today. The product site is at nitsor.com.

What Nitsor is

Industrial computed tomography (CT) and non-destructive testing are the initial commercial focus. Magnetic resonance imaging (MRI) helps test whether the same ideas work in a different field. The intended product keeps a clear record of how a dataset changes and how a release is approved. It is designed to complement the storage and annotation tools a team already uses. The full workflow describes planned behavior and is not available as a public service today.

What is available now

This public marketing site and customer documentation.
A contact path for product questions and design-partner conversations.
A clear description of the planned product that teams can evaluate without assuming it is already available.

Read Product status before relying on any statement about workflows, integrations, deployment, software packages, command-line tools, or application programming interfaces (APIs).

How these pages are arranged

Every page carries an availability label at the top. The label answers one question: can you use the behavior this page describes? Read Product status for the definition of each label.

Section	What it answers	Start with
Quickstart	What can I do in the next hour, given that this is pre-release?	The first-action table for your role.
Product status	Which capability is built, which is reachable, and which is still an open decision?	The capability status matrix.
Concepts	What do the words mean, and how does the intended model fit together?	Version model.
Guides	How is one job meant to run from beginning to end?	The guide closest to the work you already do.
Reference	What exactly exists, with its exact boundary?	Integrations and public interfaces, then the interface you care about.

Choose your path

Each path orders the same documentation for a different job. Pick the one closest to your role; every path links back to shared concepts when it needs them.

Annotators and reviewers

Learn the vocabulary and the intended review workflow. You do not need storage or API knowledge to judge whether the task model makes sense. Destination: Vocabulary and review basics.

Operations and program teams

Follow what changed, which reviews happened, what counts as an approved release, and which evidence each step should leave behind. Destination: Change and release tracking.

ML, data, and software teams

Evaluate the interfaces that exist and the evidence to demand before depending on one. No public SDK, command-line package, or self-hosted product is available now. Destination: Interfaces and acceptance tests.

Researchers and leaders

Separate the problem Nitsor addresses from the product behavior that still needs design-partner testing before you rely on it. Destination: Capability register and open decisions.

If a term is unfamiliar, open the Glossary.

Common mistake

Do not read a concrete workflow example as proof that you can run it today. Examples marked planned — not available yet explain intended behavior and do not contain runnable product instructions.

Next step

Read the Quickstart for a first action, then Product status before you rely on any capability claim.

Outcome	Choose a truthful next step without assuming a planned capability is already available.
Availability	Available now
Audience	Technical program managers, Annotators and reviewers, Technical teams, Researchers and leaders
Prerequisites	No Nitsor account is required
Last verified	2026-08-23

​What Nitsor is

​What is available now

​How these pages are arranged

​Choose your path