Choose how you run Nitsor.

Community has no Nitsor subscription fee. You run it on your own infrastructure and pay any hosting and storage costs. Its source-available licence sets the permitted uses. The self-host package ships at launch. Until then, start on Team.

A hosted workspace with collaboration, annotation, review and dataset history, plus the Team features above, billed per workspace. It includes 250 model-assisted volumes in each monthly billing period. Nitsor manages application updates and backups of the hosted workspace data. At paid launch, you choose a plan and pay the subscription upfront.

At paid launch, yearly Team is $6,228 paid upfront for the year ($519 per month equivalent). Both Team plans include 250 model-assisted volumes per monthly billing period, then $0.25 per extra volume. Usage settles monthly; it is not a pooled yearly allowance or another monthly subscription charge.

No per-seat fees. Add annotators and reviewers without paying for each person.

When you need single sign-on, more access controls, deployment help, integration work, contractual support or a yearly volume commitment. Enterprise starts at $12,000 per year, billed yearly, plus the volume commitment at a rate set in your contract. Existing negotiated commitments, rollover and overages keep their contract terms; the Team rate does not reprice Enterprise contracts. The standard yearly volumes arrive in quarterly allotments from the contract start, and an allotment's unused volumes carry into the next quarter only, then lapse. Contact sales, and we agree the supported configuration, responsibilities and billing before the service begins.

Yes. Each monthly billing period includes 250 model-assisted volumes. One model-assisted volume is one completed scan/model result under the existing scan identity rules, with every object the model finds included. Included volumes reset at the start of each monthly billing period on both Team plans; unused volumes do not carry over. The yearly plan does not pool the allowance for the year. After the first 250, each extra volume costs $0.25.

No. A run that fails is free. Before a run starts, you see how many volumes it will use, what they will cost and the most it can be charged.

Within one billing period, the first successful run of a model version on a scan counts one volume. Later runs of the same model version on the same scan in that period are free. A new billing period, a new model version or a different scan counts again. A failed run never counts. Two runs are on the same scan when Nitsor's scan identity matches, and that depends on the format:

• DICOM series: the same slices, each identified by a checksum of the whole file, in the same slice order. File names, folders and the storage connection do not matter, so a moved DICOM file is still the same scan.
• VGStudio volumes (.vgi with .vol): the same .vgi descriptor (its path, its size and its entire content) and the same .vol voxel file (its path, its size and its first 4 KB). The storage connection does not matter. Moving or renaming either file makes a new scan, and so does any change to the .vgi. A .vol changed after its first 4 KB without a change in size counts as the same scan.

Hosted model runs accept DICOM series. Other formats are refused before the run starts. A workload outside the supported models and scan sizes, including an exceptionally expensive run, needs a separate fixed quote agreed before it runs, with no surprise runtime charge.

Each extra volume costs $0.25, settled after the monthly billing cycle. Each Team workspace has a default usage budget of $1,000 per monthly billing period on top of the subscription, before tax. A run that would take usage past the budget waits instead of starting. A repeat run, which is free, can start even when the budget is used up.

No. Only hosted model runs are metered. Slices, masks, objects and GPU/runtime seconds are not billing units. A self-hosted deployment still needs enough infrastructure for its workload.

Existing scans referenced in customer storage remain there, and its provider bills you. Hosted uploads default to Nitsor-managed storage under fair use; the owner can switch that destination off. You can also upload to a write-enabled customer bucket or let Nitsor manage all storage. Browser reads use short-lived signed links; model jobs use temporary copies.

Team is unlimited for people, labels and reviews under fair use. Fair use also covers Nitsor-managed storage, including uploaded scans, label records, history and dataset versions, and the volume of API traffic, including from agents and scripts. Existing scans referenced in customer storage remain in that storage.

Fair use is not a meter, and Nitsor does not bill for it. If a workspace uses far more than a typical team, we talk to its owner and agree a plan that fits. We give notice before we change this policy.

Scans referenced in customer storage stay there. Your labels and their history stay readable through the documented interfaces and plain exports, with no exit fee. Hosted retention and access after cancellation follow the published terms.