- The application and database run inside the customer's own perimeter
- An annual license for the contracted edition and headcount, with a runbook and release materials
- Standard 5/8 support covers defects in the application
- The Managed On-prem Operations add-on moves operations to the vendor
Isolation and infrastructure
The application deployment and database sit not in the vendor's infrastructure but in the customer's own: the server, cluster, network and storage are chosen and administered by the customer, or by its contracted operator. This is the only delivery class where the vendor has no access to the runtime environment outside work agreed in the SOW.
Where your data physically lives
The application and database sit in infrastructure the customer provides and controls, typically in Uzbekistan, where Law No. ZRU-547 applies. Data never leaves that perimeter: the vendor has no access to the customer's servers outside work agreed in the SOW.
Who updates it, and in what windows
The vendor does not roll out updates itself: it prepares release materials and a runbook, and the customer (or its contracted operations partner) applies them on its own schedule. There is no shared release window for the class, because the vendor does not operate the runtime. The Managed On-prem Operations add-on moves this work to the vendor under a separate agreement.
What's included in support
Standard 5/8 support: requests are handled during business hours. The SLA covers defects in the application itself; servers, OS, cluster, network, power and backup storage remain the customer's zone. End-to-end uptime for the whole instance is realistic only with the separately purchased Managed On-prem Operations add-on and a jointly validated architecture.
Responsibility zones
The vendor is responsible for the application's correctness, the license and the release materials. The customer (or its contracted operations partner) is responsible for everything the application runs on: servers, OS, Kubernetes or Docker, network, TLS and PKI, database hosting, backup storage, a DR site and GPU if using self-hosted AI, unless Managed On-prem Operations is purchased separately.
Who it's for
A fit for organizations for whom deployment outside their own perimeter is closed off entirely, even a dedicated cloud: banks, government and quasi-government bodies, companies with a strict internal security policy. The standard offering is an annual license; a perpetual license exists only as a separately approved exception.
FAQ
What infrastructure does the customer need to provide?
Servers, an operating system, Kubernetes or Docker, network, TLS and PKI, database hosting, backup storage, a DR site and GPU if using self-hosted AI, plus system administration, unless the Managed On-prem Operations add-on is purchased.
Does a perpetual license exist?
The standard On-prem SKU is an annual license. A perpetual license is available only as a rare, separately approved exception, not as a default option.
Who applies updates if the vendor doesn't operate the runtime?
The vendor prepares releases and a runbook, and the customer or its contracted operations partner applies them on its own schedule. The separate Managed On-prem Operations add-on hands this work to the vendor.