Plan your first project

All plans Start with one CT or MRI workflow and one Dataset Version your team can use. The workflow in this guide runs on Team and Enterprise, from a workspace and agent token through annotation and review to a Dataset Version. A Community deployment cannot run it today. It has no supported way to issue an agent token: tokens are created in the hosted app on Team and Enterprise, and its stack does not include the Nitsor dashboard. Its run plane is off and it runs no data-plane Workers, so it cannot build or read a Dataset Version. Compare the plans to choose who will run Nitsor and how your team signs in.

Describe one workflow

Describe the recurring task and the release or quality decision it feeds. Identify where people need to reconstruct an annotation, a review or the version used for training. Write down the following before setting up the project. You can describe each item without disclosing scan data, credentials or storage locations.

Item	What to write down
Modality and recurring task	The imaging type and the job your team repeats, in one sentence.
Formats and approximate scale	Representative file formats and a rough sense of volume, without exact figures if sensitive.
Current tools and handoffs	The systems the work passes through and where it changes hands.
Roles and external contributors	Who takes part, including vendors or contractors outside your organization.
Review and escalation	How many reviews are required and who decides a contested item.
Release or downstream decision	The decision this workflow feeds, and what a wrong one costs.
First project result	The result your first project needs to produce.

Keep the first project small

On Team and Enterprise, register one series from your bucket, bind a two-stage pipeline, have one annotator and one reviewer work it, create one Dataset Version and read it through the HTTP API. The Python reader is not on PyPI. Dataset Version downloads from a self-serve customer connection need a signer that Nitsor sets up with you. A mask workflow also needs write access. Community cannot complete these steps today. Use documentation and demo data to define the workflow. Use your own data and people to check that the workflow meets your team’s requirements.

What documentation and demo data can establish	What needs your real data and people
How the version graph, rungs and stages describe your workflow	Whether Nitsor handles your volumes and formats
How product terms map to the terms your team uses	Whether reviewers can label your structures with the editor
How review verdicts and rework operate	Whether your team can complete its review process within the product’s limits
How the data boundary divides storage and security responsibilities	Whether your bucket and identity provider connections work
Which records a Dataset Version contains	Whether those records let your team reconstruct its release decision
Which plan covers your hosting and identity needs	Cost, reliability, performance and suitability for your use

What you set up

Piece	What to configure
Workspace	Create a Team workspace at app.nitsor.com or arrange Enterprise with sales. The Community self-host stack does not include the Nitsor dashboard today.
Members and roles	Invite people and assign `owner`, `admin`, `member` or `billing` account roles. Set project rungs for the work each person does.
Storage connection	Choose connected customer storage, a Nitsor-managed bucket, or storage managed entirely by Nitsor. Hosted uploads default to Nitsor storage; the owner can turn it off. Existing scans stay where they live. An owner or admin connects customer storage and submits keys through the dashboard or personal authority; Nitsor encrypts them. New customer connections are read-only.
Agent token	On Team and Enterprise, an owner or admin creates a service account in Team settings › Service accounts with the permissions it needs, and a token for it. The token expires 90 days after creation unless another time is chosen, at most 365 days, and the service account sees no project until a project admin gives it access on the project’s Access page, at `operate` at most. A Community deployment has no supported way to issue one. See Service accounts and tokens.
Client	The Python SDK (`nitsor`) is not on PyPI. Use the HTTP API.
Hosted model jobs	Auto-label stages run on Nitsor’s managed GPU run plane, confirmed per Run. See Plans and billing for plan coverage and billing.

Talk to us

Request a walkthrough with a description of your workflow. For Enterprise deployment, SSO, billing or support terms, contact sales. Do not send credentials, patient or customer scan data, storage locations, or confidential strategy or contract material through the contact form. A description of the workflow is enough.

Next step

Follow the Quickstart, then Register a source for your first project.

Plans	All plans
Last verified	2026-09-30

Get started

Concepts

Guides

Reference

Describe one workflow

Keep the first project small

What you set up

Talk to us

Next step

​Describe one workflow

​Keep the first project small

​What you set up

​Talk to us

​Next step

Describe one workflow

Keep the first project small

What you set up

Talk to us

Next step