Delivery classes
Talantiq ships in three classes: the difference is isolation, infrastructure, and who is responsible for updates and backups. Pick a class for the detail, or compare all three in the table below.
Comparing delivery classes
One product, three deployment models. Delivery class is a required attribute of the SKU, the Order Form, the license and the SLA: it gets agreed explicitly before the order, not implied by the word "cloud".
| Attribute | Standard Cloud | Dedicated Cloud | On-prem |
|---|---|---|---|
| Isolation and infrastructure | A separate application deployment and a separate database per customer, physically your own, not a shared schema with row-level separation. The network, compute pool and operational contour (monitoring, backups, support) are shared across every Standard Cloud customer, which is what makes onboarding fast and affordable. | A separate application deployment inside a dedicated cloud project (VPC), with resources reserved for the customer instead of drawn from a shared regional cluster. The database, secrets, task queues, vector store (RAG) and file storage each run in their own contour, separate from other customers. In Standard Cloud only the database is separate; here the whole contour is. | 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 live in a separate deployment on shared regional infrastructure in Uzbekistan: the network and compute pool are shared among Standard Cloud customers, but the database and secrets are the customer's alone. Personal data is stored in Uzbekistan under Law No. ZRU-547. | The application and database run in a dedicated cloud project (VPC) in Uzbekistan: resources are reserved for the customer and the network is private. Personal data is stored in Uzbekistan under Law No. ZRU-547, but the contour is not shared with any other customer. | 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 | Updates and backups are the vendor's responsibility, with no action needed from the customer. The update window is shared across every customer in this class, and no version is pinned for an individual customer: releases follow the platform's common schedule. | The release window is agreed with the customer instead of set by the platform. This contour also supports a controlled version pin, an option Standard Cloud does not offer. Backups remain the vendor's responsibility. | 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 support: requests are handled during business hours, priority and response time follow the platform's general SLA. Extended support (24/7, a dedicated manager) is available as a separate option for more demanding contours, but is not included by default in this class. | The same support tiers as Standard Cloud apply, framed around the dedicated contour: response and restore times are measured against the customer's own instance rather than the shared platform. Premium support and higher availability (HA/DR) become available once the contour passes readiness review. The Enterprise edition is sold only on Dedicated Cloud or On-prem; it is not available on Standard Cloud. | 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 infrastructure, releases, backups and platform availability. The customer is responsible for the data it uploads, employee access rights and the content of its configuration (branding, theme, roles). | The vendor still runs infrastructure, releases, backups and platform availability, now inside the customer's own reserved cloud project. The customer remains responsible for the data it uploads, employee access rights and the content of its configuration. This stays a vendor-operated cloud model, not customer-hosted infrastructure as in On-prem. | 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 companies with 50 to 1,000 employees running standard HR processes that do not need a dedicated network contour or an individually scheduled update window. The fastest path from signup to a working instance. | A fit for companies from 200 employees, and for regulated organizations of any size: banks, microfinance institutions, government and quasi-government bodies, or any company that needs a private network. The choice once Standard Cloud's shared infrastructure is not enough. | 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. |