Office SDK runs on your infrastructure, so pricing follows the deployment rather than per-file usage. Tell us the editor count, environments, and workflow scope, and you receive a quote that matches the deployment you are actually evaluating.
A sample Office surface for products that keep a document beside the work around it.
Use these pages to decide which workflow, format, and ownership boundary should be validated first.
The license covers the self-hosted Office SDK deployment in your environments. Opening, editing, and converting files inside that deployment is not metered, so usage growth does not change the invoice.
Concurrent editors, the environments you run (evaluation, staging, production), and the workflow scope you need first. A focused first scope keeps the entry price honest.
The quote includes integration support during evaluation, upgrade access, and help validating the exact formats and workflows you plan to run in production.
The recommended path is a single-server proof of concept on one workflow. Pricing for production is easier to accept after the evaluation has evidence behind it.
Office SDK pricing is a self-hosted deployment license sized by editors, environments, and workflow scope, without per-file or per-document charges.
One self-hosted license covers the Office SDK runtime in the environments you agree with the team.
Preview, editing, and conversion inside the deployment are not metered per file or per document.
Concurrent editors, environment count, and first workflow scope determine the quote.
| Factor | Moves the quote | Why |
|---|---|---|
| Concurrent editors | Yes | Sizing follows the people editing at the same time, not the document count |
| Environments | Partly | Evaluation, staging, and production are scoped explicitly |
| Files opened or converted | No | Document volume is not metered inside the deployment |
| First workflow scope | Partly | A focused first scope keeps the evaluation and the quote small |
