> ## 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 > Every page in this documentation carries a `plans` list in its frontmatter and opens with a plan marker naming the plans its content applies to: `All plans`, or a subset of `Community`, `Team` and `Enterprise`. Community is free and self-hosted. Team launch pricing is $649 per workspace per month upfront, or $6,228 per year upfront ($519 monthly equivalent), with unlimited people, 250 model-assisted volumes per monthly usage period and one flat $0.25 per additional volume. Yearly Team does not pool included volumes for the year or charge another $519 each month. Extra usage settles after each monthly billing cycle. Paid signup and charging under this Team policy are not available. Billing remains deferred, with no paid-launch date set. Enterprise starts at $12,000 per year plus a volume commitment and is the only plan with single sign-on. Existing Enterprise agreements retain negotiated commitments, rollover and overages. Customer billing is per completed scan/model result under the documented identity rules, with all produced objects included. Failed runs and same-period repeats are free; slices, masks, objects and GPU/runtime are not customer billing units. Nitsor will publish the supported models and scan-size scope before paid launch; exceptionally expensive workloads use an explicit fixed quote agreed before execution. Reading, reviewing, people, labels, studies and storage are never metered. > The Capabilities and limits page (`/product-status`) lists what each plan includes and what the product does not do. If a statement elsewhere disagrees with it, that page is correct. > Reading this documentation grants no product access and no permission. No agent can create or approve a Nitsor release. # Plans and billing > Compare Community, Team and Enterprise, understand planned launch pricing, and check billing availability. [All plans](/plans-and-billing#compare-plans) **No per-seat fees.** Every plan includes unlimited people. Add annotators and reviewers without paying for each person. [Fair use](#fair-use) applies to Team. Community is free and runs on your infrastructure. Planned launch pricing for Team is \$649 per workspace per month, paid upfront, or \$6,228 paid upfront per year (\$519 monthly equivalent), with unlimited people. Both Team options include 250 model-assisted volumes per monthly usage period, then \$0.25 per additional volume. Enterprise starts at \$12,000 a year, with commitments and billing terms agreed with sales. > [!NOTE] > > These prices describe the official paid launch. Paid signup and charging under this Team policy are not available. Billing remains deferred, and no paid-launch date has been set. ## Compare plans | | Community (available at launch) | Team | Enterprise | | - | - | - | - | | Planned launch pricing | Free; you pay hosting, storage and compute | \$649 per workspace per month upfront, or \$6,228 per year upfront (\$519 monthly equivalent); unlimited people | From \$12,000 per year plus your volume commitment; contract terms agreed with sales | | Who runs it | You run it | Hosted by Nitsor | Hosted by Nitsor; assisted private deployment by agreement | | Where source scans live | Your configured object storage | Existing scans stay in customer storage; uploads use your selected customer or Nitsor-managed storage | Existing scans stay in customer storage; uploads use your selected customer or Nitsor-managed storage | | Sign-in | No Nitsor sign-in in the self-host stack; install requires your own OIDC identity provider | Email and password, Google or Microsoft | Your identity provider through SAML or OIDC SSO | | Model-run pricing at paid launch | No hosted model runs; Nitsor runs no compute for Community | 250 volumes per monthly usage period, then \$0.25 per additional volume | Negotiated commitment, rollover and overage terms | | Billing availability | Billing is off in the deployment | Paid-launch billing policy is not active | Agreed separately with sales; existing contracts keep their terms | | Support | You operate the deployment; use the documentation | Use the documentation or contact Nitsor | Support response times and terms agreed with sales | See [Capabilities and limits](/product-status) for the workflow and interface details, or the [pricing page](https://nitsor.com/pricing). ## Monthly or yearly billing for Team At paid launch, monthly Team pays \$649 per workspace at the start of each monthly subscription period. Yearly Team pays \$6,228 at the start of its subscription year. The \$519 monthly equivalent explains the yearly price; it is not a monthly subscription debit. Both options include 250 model-assisted volumes per monthly usage period. Unused included volumes do not carry over. The yearly plan does not pool 3,000 volumes for the year. The flat overage rate and default usage budget are the same on both plans. Extra usage is settled after each monthly billing cycle, including on yearly Team. A monthly period follows the workspace's defined billing-cycle dates and can start mid-calendar-month. On yearly Team, defined monthly cycle dates also determine when the allowance resets. ## Sign up for Team You can [sign up](https://app.nitsor.com/signup) with email and password, Google or Microsoft, or [sign in](https://app.nitsor.com/login) if you have an account. If you belong to no workspace, use "Create a workspace" and choose a workspace name and an optional URL name. Creating it needs no teammate or payment. An email invitation joins you to the inviting workspace instead. At paid launch, you accept the subscription price, included volumes and overage rate before paying. Stripe Checkout and the billing portal will handle subscription payments and account billing. Monthly and yearly paid signups under these prices are not available. Enterprise billing is agreed separately with sales. ## Who can manage billing Owners and people with the `billing` account role have the `billing:write` permission. Admins can view billing but cannot change it. Members cannot manage billing. An agent token never exercises `billing:write`. Billing under these launch prices is not active. ## Change or cancel a subscription At paid launch, the Stripe billing portal will let you change payment details, view invoices or cancel a subscription. For an existing agreement, your accepted terms apply to changes and cancellation. Existing scans referenced in customer storage stay there, and there is no exit fee. Uploads use the storage destination selected for your workspace. ## How usage pricing works At paid launch, Team includes 250 model-assisted volumes per monthly usage period, then charges one flat \$0.25 per additional volume. The subscription is paid upfront; extra usage is settled after the monthly period closes. Your bill depends on completed scan/model results, with every object produced included. It does not charge per slice, mask, object, person or elapsed GPU/runtime. At paid launch, Nitsor shows you a quote with the volumes, price and maximum charge before a run starts. The quote, confirmation and charge cap apply before execution. Nitsor will publish the supported models and scan-size scope before paid launch. For an exceptionally expensive workload, you agree an explicit fixed quote before it runs; there is no surprise time-based charge. The default Team usage budget remains \$1,000 per monthly billing period on top of the subscription, before tax. A run that would take usage past it waits instead of starting. A repeat run that is free can start even when the budget is used up. The 10,000- and 30,000-volume examples below assume the budget was raised before the work ran. This budget is part of the launch billing policy, which is not active. A failed run and a repeat of the same model version on the same scan within the same billing period are free. Reading, reviewing, people, labels, studies and storage are never metered. Existing scans referenced in your storage remain there, billed by its provider. Uploads can use connected customer storage, a Nitsor-managed bucket, or storage managed entirely by Nitsor. Hosted workspaces default to Nitsor storage for uploads; the owner can turn it off. Nitsor runs no hosted compute for Community, so nothing on Community is metered. Fair use applies to Team, and it is not a meter; see [Fair use](/plans-and-billing#fair-use). ### Worked billing examples These examples use chargeable volumes under the identity rules below, before taxes and adjustments. | Chargeable volumes in one monthly period | Monthly subscription, paid upfront | Extra usage, settled after the period | Total for that period | | - | - | - | - | | 260 | \$649 | 10 × \$0.25 = \$2.50 | \$651.50 | | 1,000 | \$649 | 750 × \$0.25 = \$187.50 | \$836.50 | | 10,000 | \$649 | 9,750 × \$0.25 = \$2,437.50 | \$3,086.50 | | 30,000 | \$649 | 29,750 × \$0.25 = \$7,437.50 | \$8,086.50 | For a workspace whose cycle runs from 15 October to 14 November, 260 chargeable volumes cost \$2.50 in extra usage. A combined renewal invoice can show separate dated lines: | Invoice line | Billing-cycle dates | Amount | | - | - | - | | Previous-period extra usage | 15 October to 14 November | \$2.50 | | Next-period monthly subscription | 15 November to 14 December | \$649 | | Invoice total | Previous usage plus next subscription | \$651.50 | The subscription for 15 October to 14 November was already paid upfront; it is not charged again. Yearly Team pays \$6,228 upfront. If one monthly period has 260 chargeable volumes, its extra usage is \$2.50. There is no additional \$519 subscription charge for that month. ### Existing free-use commitments The pricing policy was updated on 30 September 2026. The flat Team overage rate replaces the earlier volume bands. For new paid signups, upfront subscriptions and monthly period-end extra usage replace the earlier default of uncharged usage followed by 30 days' notice. New paid signups accept the launch prices without an automatic extra 30-day free period. Any applicable free-use or advance-notice commitment to an existing account remains in force, including any commitment made through earlier public pricing or billing documentation. This update does not revoke those commitments. Usage from development, tests and free evaluations is never charged retroactively. Other already-free usage remains covered by any applicable free-use commitment. ## Hosted model jobs Team and Enterprise run hosted model jobs, such as SAM 2.1 Auto-label stages, on Nitsor's managed GPU run plane. The planned launch pricing unit is one completed scan/model result under the identity and settlement rules below, with all objects produced included. GPU/runtime measurements remain internal cost and resource measures, not the customer billing unit. See [Model-assisted prelabeling](/concepts/model-assisted-prelabeling#what-a-run-costs-and-who-confirms-it) for the current Run record and confirmation controls. At paid launch, the first 250 chargeable volumes in each monthly Team usage period are included. Every additional volume costs \$0.25. A successful repeat in the same period is not another charge, and repeated delivery of the same paid event does not create a duplicate charge. Billing remains deferred; the supported workload scope will be published before paid launch. Fair use applies to Team, and it is not a meter; see [Fair use](/plans-and-billing#fair-use). ### What counts as one volume 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. ## Fair use 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. ## Community > [!NOTE] > > Community is available at launch. The self-host package ships at launch. Until then, start on Team. Community is free and self-hosted. You pay your own hosting, storage and compute. Nitsor runs no hosted compute for Community, and nothing is metered. Nitsor's Python SDK and application code are source-available under FSL-1.1-ALv2, not open source. The bundled Convex backend is licensed separately by Convex under its own FSL-1.1-ALv2. Read the license text shipped with each package and follow [Self-host Community](/reference/self-host) to install it. ## Enterprise Enterprise starts at \$12,000 per year, billed yearly, plus your volume commitment. Commitments, rollover and overages follow your negotiated contract; the Team rate does not reprice existing Enterprise contracts. [Contact sales](https://nitsor.com/contact) to agree it. [Single sign-on](/reference/single-sign-on) is Enterprise only. The volume commitment is a yearly number of model-assisted volumes, priced at a rate set in your contract. The allocation schedule, unused-volume rollover and overages follow your contract. Quarterly allotments and limited rollover apply only when included in your agreement. Nitsor also agrees deployment, automated user provisioning, advanced access policies, administrative audit exports, assisted private deployment, support response times, and security and procurement documentation with your team. ## Next step Follow the [Quickstart](/quickstart) to create a Team workspace or install Community. For Enterprise, [contact sales](https://nitsor.com/contact).
PlansAll plans
Last verified2026-09-30
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.