> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nitsor.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Nitsor is a pre-release product. Every page in this documentation carries an availability status in its frontmatter (`availability`) and, as the first element of its body, a link labelled `Available now`, `Limited design-partner access`, or `Planned - not available yet`. That label is binding: it says whether a reader can use the behaviour the page describes.
> A page written in the present tense is not a claim that the behaviour ships. Where the availability label says `Planned - not available yet`, the page describes a target contract and there is no runnable product, screen, command, or public interface behind it.
> Every readiness claim this documentation makes lives on the Product status page. If any statement elsewhere disagrees with the capability status matrix on that page, the matrix is correct.
> Reading this documentation grants no product access and no permission. No agent can create or approve a Nitsor release.

# Introduction

> Version control for 3D AI inspection data. Understand what Nitsor is, what a visitor can use today, and where each part of this documentation answers a different question.

<a className="nit-availability" data-availability="available-now" href="/product-status#status-definitions" aria-label="Available now. Read the status definitions."><span aria-hidden="true" className="nit-availability__dot" />Available now</a>

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](https://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](/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](/product-status) for the definition of each label.

| Section                           | What it answers                                                                     | Start with                                                             |
| --------------------------------- | ----------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
| [Quickstart](/quickstart)         | What can I do in the next hour, given that this is pre-release?                     | The first-action table for your role.                                  |
| [Product status](/product-status) | Which capability is built, which is reachable, and which is still an open decision? | The capability status matrix.                                          |
| [Concepts](/concepts)             | What do the words mean, and how does the intended model fit together?               | Version model.                                                         |
| [Guides](/guides)                 | How is one job meant to run from beginning to end?                                  | The guide closest to the work you already do.                          |
| [Reference](/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.

<Columns cols={2}>
  <Card title="Annotators and reviewers" href="/guides/annotate-and-review">
    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.
  </Card>

  <Card title="Operations and program teams" href="/guides/dataset-release">
    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.
  </Card>

  <Card title="ML, data, and software teams" href="/guides/plan-an-integration">
    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.
  </Card>

  <Card title="Researchers and leaders" href="/product-status">
    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.
  </Card>
</Columns>

If a term is unfamiliar, open the [Glossary](/reference/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](/quickstart) for a first action, then [Product status](/product-status) before you rely on any capability claim.

<table className="nit-page-details" aria-label="Page details">
  <tbody>
    <tr><th scope="row">Outcome</th><td>Choose a truthful next step without assuming a planned capability is already available.</td></tr>
    <tr><th scope="row">Availability</th><td>Available now</td></tr>
    <tr><th scope="row">Audience</th><td>Technical program managers, Annotators and reviewers, Technical teams, Researchers and leaders</td></tr>
    <tr><th scope="row">Prerequisites</th><td>No Nitsor account is required</td></tr>
    <tr><th scope="row">Last verified</th><td>2026-08-23</td></tr>
  </tbody>
</table>