Commercial packaging

The commercial model: units of delivery, the licensing model and prices, the key and the modes without one, partnership levels.

You buy the right to embed the engine and managed compatibility, not the source code. That means a supported runtime with commitments on compatibility and updates, not a fork you would then have to maintain yourself.

Deal component	What it is	Why it matters
The right to embed	The right to embed and distribute SumOffice under your brand.	The legal basis for delivering it under your own name.
Access to the developer kit	Built packages, types, the public interface, examples, and documentation. For documents, the public contract works today; for spreadsheets, the set is still being separated from the internal contract, and its current contents are a matter of the agreement, not a default.	Integration goes through a stable contract, not internal details.
Capability profile	A named set of features, platforms, formats, embedding methods, and limits.	This, not general phrases, is what defines the commercial promise.
Integration package	Joint development of an adapter for your application, storage handling, and an acceptance scenario.	Reduces the risk of a failed pilot.
Automation modules	An interface for agents, VBA compatibility, Power Query, and data connections — each with its own profile.	The base editor delivery isn’t mixed with what needs separate verification.
Version support and commitments	The support period, security fixes, the update cadence, the compatibility period.	Enterprise rollout depends on how predictable these timelines are.
Security package	The delivery’s component inventory, vulnerability response times, the disclosure process, file signatures, release notes. What’s already signed in the current release and what isn’t yet is listed in Risks.	Covers the requirements of the security and procurement teams.
Quality program	A set of documents for regression testing, sample files, speed and memory thresholds, an escalation process.	Reduces the risk of disputes after rollout.

Product tiers

Tier	What’s included	Who it’s for
Evaluation kit	The runtime, a sample application, a few sample documents, the quick start, and a list of known limitations.	For a CTO or architect running a first check.
Limited pilot	One platform, one real working scenario, a narrowed capability profile.	Check whether the product fits and whether compatibility is good enough.
Embedding kit	The public interface, types, a shell under your brand, adapters, and documentation. For documents, this is a contract and surface that work today; for spreadsheets, the public set is still taking shape, and its contents are fixed by the agreement — what’s in it today.	A working integration into your product.
Enterprise profile	The security package, version support and commitments, an update channel, acceptance before production use.	For enterprise customers and anyone deploying the product inside their own perimeter.
Extended automation	Agents, the supported subset of VBA, Power Query and data connections, policy enforcement points. “Agents” means different things here: for documents, an agent uses the same commands as a person (there are 41), there is no separate interface for it, and it only proposes; for spreadsheets, the “inspect, propose, apply” flow relies on the release’s operations, while the agent’s permissions, the audit contents, and the approval process are fixed by the pilot.	Complex data migrations, document-management, accounting, and resource-planning systems, analytical processes.

Licensing model

The engine is licensed to the application that embeds it: not per seat, not per document, not per operation.

Stage	Terms
Evaluation	Free: the full engine, real files. Working in the editor is not time-limited; automated processing without a key switches to quiet mode after 60 days — key and operating modes.
Pilot	Two weeks on your corpus with written acceptance criteria; the report stays with you either way — Pilot and acceptance.
Production use	An annual license for one embedding application. Updates and engineering support with a named response time are included in the price; deployment inside your perimeter, under your brand; users aren’t counted.
Editors as a server	Server images of SumDoc and SumSheet inside your system: evaluation is free, production use is the same annual license for the embedding application.
A Layers node with the editors inside	90 days at full speed, then a key: 150 € per month for up to 50 people, 400 € for up to 200. Without a key, the node keeps working and keeps its data; only the automated paths slow down — export, conversion, transcription.

What the license covers: distributing the engine inside your application — in your perimeter or in your cloud, all engine updates during the term, engineering support with a named response time. The price depends on one thing: which application embeds the engine and how it is delivered. A written proposal — within one business day.

Changes for your process

You don’t pay for the right to open a file. You pay for adapting the tool to your process — with a deadline and a named owner. Our defects aren’t an order: a file that opens incorrectly, a lost edit, a crash — these are fixed for free, and the service level only sets the speed.

Class	Price	Deadline	Examples
A — behavior settings	150 €	1 business day	The default export format, page settings and fonts, the template set, features turned on and off, your logo and name on the editor surface, the interface language.
B — connection to your system	300 €	2–3 business days	Two endpoints of your system (“who am I”, “file by ID”), pass-through single sign-on, a save notification (webhook), a file naming rule, reverse proxy setup, a reversible rollback.
C — engine behavior	600 €	up to 5 business days	Porting one macro or one Power Query source of a typical form, support for one DOCX or XLSX construct from your corpus, an export variant, automation of one operation.
By estimate	from 600 €	agreed in advance	Everything beyond class C: a set of macros, integration with a document management system without WOPI, a new data source, on-site work, a corpus audit before migration.

On-call — 150 € per month per organization: a response within a business day, a file fix in the engine within five days, builds with fixes as they are ready. For one person — 9 $ per month. The price and deadline are named before work starts; if the deadline is missed, you don’t pay. A change arrives as a build or a setting, verified on our test bench with your file, with a note on what changed and how to roll it back; your originals and your system are not touched.

Key and operating modes

A person working in the editor — the editor window, the mobile app, the web sandbox — is never limited by a key. A key is needed only for automated processing: the command line, the developer kit, the API, and server-side export.

Mode	When	Limits
Full	Working in the editor — always; automated processing with a valid key that covers the product.	No limits.
Evaluation	Automated processing without a key, the first 60 days after the first launch on this machine.	No more than two operations in parallel, up to 1,000 documents per day, the “SumOffice evaluation” mark in the PDF footer.
Quiet	Automated processing without a key after 60 days.	One document at a time, a 3-second delay per operation, 100 documents per day, the same mark in the PDF.

There is no refusal in quiet mode: parallel requests wait their turn, and an exhausted daily quota waits for the next day. A key covers the products named in it and remains valid for another 30 days after it expires.

For developers

Environment variables for automated processing:

Variable	What it does
`SUMOFFICE_LICENSE`	The key as a string; `SUMOFFICE_LICENSE_FILE` — the path to the key file.
`SUMOFFICE_SESSION_KIND=interactive`	Declares an interactive session — for the desktop shell that starts the processor on behalf of a person.
`SUMOFFICE_LICENSE_QUOTA_WAIT=fail`	Instead of waiting for the quota, return exit code 75 — for a service with its own queue.

Concurrency in quiet mode is held by locks: the second request waits rather than being refused.

What’s next

How verification works before the contract — Pilot and acceptance.
What’s in the delivery — What the delivery includes.
To request a written proposal or a pilot — contact us.