Uzbekistan's IT landscape has been undergoing a fundamental transformation in recent years. For CTOs, system architects, and large business owners, the question of cloud migration has moved beyond theoretical discourse into the realm of hard-nosed pragmatism. The concept of 'going all-in on cloud' often hits the wall of harsh reality: businesses have accumulated a massive fleet of hardware that physically occupies racks in server rooms and data centers, functions reliably, and has not yet recouped its capital investment (CAPEX).
In this context, hybrid cloud serves not as a temporary compromise, but as a long-term, technically sound strategy. It allows you to 'stitch together' existing on-premise servers with the elastic capacity of local provider UzCloud, creating a unified, seamless infrastructure.
The Technology Dead End and the Myth of 'Pure' Cloud
For a system architect in Uzbekistan, moving to the cloud always means balancing innovation against legacy systems. First, there is accumulated heritage: for decades, businesses invested in their own server rooms. Second, regulatory requirements: the legislation of the Republic of Uzbekistan mandates storing personal data within the country. Third, network connectivity issues: latency to European data centers is 90–100 ms, which is fatal for transactional databases and ERP systems.
Market Specifics: UzCloud as a Local Hub
UzCloud does not merely provide virtual machines — it acts as a connecting link integrated into the national traffic exchange network TAS-IX. Hybrid cloud in Uzbekistan is not two separate data stores connected via the public internet. It is a single network circuit where the provider's cloud resources are accessible over local channels with latency comparable to that within a corporate LAN.
Latency Comparison from Tashkent
| Destination (from Tashkent) | Connection type | Average latency (ms) | Suitability for DB/ERP |
|---|---|---|---|
| UzCloud (TAS-IX) | L2/L3 VPN / Direct Connect | 1 – 5 | Ideal |
| AWS Frankfurt (eu-central-1) | Public Internet | 94 – 99 | Limited |
| AWS Tokyo (ap-northeast-1) | Public Internet | 168 – 171 | Unsuitable |
| Azure UAE (Dubai) | Public Internet | 55 – 70 | Acceptable for non-critical systems |
| Google Cloud (St. Petersburg) | Cross-border link | 178 – 180 | Unsuitable |
Legal Foundation: ZRU-547 and Data Localization
Article 27-1 of the Law of the Republic of Uzbekistan 'On Personal Data' requires owners or operators to ensure the collection, systematization, and storage of personal data of Uzbekistan's citizens in databases physically located on technical facilities within the country. Hybrid cloud enables this scheme: expanding infrastructure through UzCloud while meeting regulatory requirements.
Technical Implementation: Layer 3 VPN
On the client side, a border router establishes a secure IPsec tunnel to the UzCloud cloud gateway. The process includes: creating a VPC with a dedicated IP address range, configuring the VPN Gateway, registering the Customer Gateway, and setting up routing via BGP. This allows cloud servers to access on-premise resources via internal IP addresses as if they were in an adjacent rack.
Layer 2 Extension and Direct Connect
In specific cases where a VM needs to be migrated from an on-premise data center to the cloud without changing its IP address, L2 segment stretching via VXLAN is used. UzCloud offers the Enterprise Switch — a virtual switch that terminates VXLAN tunnels from the client's on-premise equipment.
Direct Connect — establishing a physical fiber-optic channel from the client's site to the provider's PoP — ensures exceptional security (traffic never traverses public networks), guaranteed speeds up to 100 Gbps, and minimal jitter for real-time systems.
Economics: A Smooth Transition from CAPEX to OPEX
The hybrid model enables a gradual transition to cloud consumption. Instead of purchasing five servers for an annual report or seasonal sale — rent from UzCloud for one week. No need to buy a second set of equipment for backup. Traffic within TAS-IX for business is often significantly cheaper or included in provider service packages.
Use Cases
Banks and Fintech: the master database resides in the company's own data center. Web servers and API gateways are deployed in UzCloud. When load increases, the cloud automatically adds new virtual machines.
Retail and E-commerce: the core accounting system (ERP) operates in the hybrid cloud. The power of TAS-IX ensures instant synchronization of product inventory between a warehouse in Tashkent and a store in Nukus.
Disaster Recovery: UzCloud is used as a hot backup site. If an on-premise server fails, the IT team can spin up its copy in the cloud with just a few clicks. Recovery time objective (RTO) drops from days to minutes.
Conclusion
Hybrid cloud is a strategy for business survival and growth in Uzbekistan's current reality. It is a way to gain the flexibility and power of world-class technologies while staying within the national legal framework and maintaining control over your assets. By leveraging UzCloud's local capacity, TAS-IX integration, and secure communication channels, you build a foundation that can withstand any load. Hybrid is not a compromise. It is the rational choice of those who know how to manage costs and value reliability.