- Self-serve signup with no wait for a sales call
- A 14-day trial for up to 50 employees, no card required
- Updates and backups are entirely the vendor's job
- Billed per paid employee, with no minimum contract for dedicated infrastructure
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.
Where your data physically lives
The application and database live in a separate deployment on shared regional infrastructure in Kazakhstan: 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 Kazakhstan under Law No. 94-V.
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.
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.
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).
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.
FAQ
How does Standard Cloud differ from Dedicated Cloud?
In Standard Cloud the network and compute pool are shared across the class; Dedicated Cloud gets its own cloud project (VPC) and reserved resources. In both cases the database and deployment are the customer's own.
Can we move from Standard Cloud to Dedicated Cloud?
Yes, the move is arranged under a separate agreement. Data migrates into the new dedicated contour; the details are worked out with sales.
Who's responsible for updates on Standard Cloud?
The vendor. Updates ship on the platform's common schedule, with no customer involvement and no way to defer a specific release for a single customer.