01
Functional scope
Package capabilities, relevant roles, permissions and usage boundaries are confirmed.
CONTRACTING MODEL
Pay for the packages and scope you actually need.
There is no public price list or universal bundle. The commercial model is formed around the Core foundation, selected packages, user count, contract term and required configuration.
Exact price, currency, billing method, validity period and support are confirmed in an individual proposal and contract. Existing contracts and active capabilities remain preserved.
CONTRACT LOGIC
The contract follows real operational scope — without generic public pricing.
01Core
02Packages
03Users
04Scope
05Activation
CONTRACTED SCOPE
From foundation to an active operating system.
- 01Opearia Core as the shared foundation
- 02Selection of operational and industry packages
- 03User seats, roles and responsibilities
- 04Data scope by team, site, partner or company
- 05Contract term, support and activation plan
TERMS BY PACKAGE
Every package has its own commercial configuration.
02
Commercial terms
Price, currency, billing method, seats and validity period are defined by contract.
03
Lifecycle
A package may be planned, available, existing or withdrawn while valid contractual rights remain preserved.
ACCESS CONTROL
A package is not the same as a user permission.
- 01The package determines which capabilities are available to the company
- 02The role determines which actions a user may perform
- 03Scope determines which data the user may access
- 04Server controls verify package, membership, permission and scope
- 05Sites and business partners can be assigned to an individual user
NO PUBLIC PRICE LIST
The proposal follows the real process, not an invented average company.
Companies differ in user count, sites, assets, data volume, required packages, support and rollout dynamics. We therefore confirm pricing only when the scope is sufficiently clear.