Russian Businesses Surge Chinese LLM Usage More Than 11-Fold in First Half of 2026
Russian small and medium-sized businesses along with large corporations have sharply increased their adoption of Chinese large language models. According to data from MWS Cloud, organizations consumed more than 400 billion tokens during the first half of 2026. This volume is 11.3 times higher than the 39.1 billion tokens recorded for the entire previous year.
The Qwen family remained the undisputed leader. Its share rose from 20 billion tokens and 51.1% in 2025 to 261.1 billion tokens and 59.1% in the first six months of 2026. GLM held second place with 91.2 billion tokens, representing 20.7% of total consumption.
DeepSeek, which ranked third in 2025, was overtaken by the Kimi family. Models from Kimi processed 81.4 billion tokens and captured 18.4% of usage. The rapid pace of the Chinese LLM race means that last year’s frontrunner can quickly fall outside the top three.
The statistics are drawn from MWS GPT Model Hub and MWS GPT platforms, whose primary clients are large enterprises. Businesses deploy these models for chatbots, personalized advertising, mass email campaigns, product descriptions, and analysis of customer reviews and inquiries. In practice, companies assign LLMs tasks that must run continuously, at high speed, and without typical human limitations.
MWS Cloud estimates that the entire Russian LLM market will expand by 35% in 2026, reaching 19.6 billion rubles. The cloud segment, which includes SaaS and API access to models, is expected to approach 1.5 billion rubles. In response to rising demand, MWS Cloud expanded its Model Hub catalog nearly twofold to 17 models. New additions include GLM 5.2, Kimi K2.6, Qwen3.6, Gemma 4, GPT OSS, as well as speech recognition and synthesis tools and rerankers for search systems and RAG pipelines. All services are available through a single OpenAI-compatible API.
The volume of tokens processed indicates that Russian enterprises have moved beyond experimentation and are now embedding Chinese LLMs into core operational processes, with demand continuing to outpace catalog updates.
Related articles
Yandex Black October: How Architectural Flaws and Capacity Mismanagement Turned Data Center Losses Into a 11-Day Fintech Coma
In October 2026 three Yandex data centers in Central Russia were physically destroyed within days, triggering the collapse of Yandex Cloud and multiple core services. Between the first and third site failures engineers had 74 hours to restore quorum and rebalance workloads yet failed to do so because Control Plane components remained tied to the lost zone and spare capacity had been eliminated to cut costs. Core banking and BNPL systems entered Read-Only mode after losing quorum, forcing a complete stop-the-world reconciliation that lasted until 22 October. Backups stored inside the same regional S3 buckets proved unusable, resulting in a seven-day RPO and primary-key collisions after restoration. The incident exposed that Metro-Cluster designs had been incorrectly treated as full Disaster Recovery and that aggressive AP microservice patterns created logical split-brain conditions outside the database layer.
Astra Group Releases Low-Code Astra AI Platform for Building Corporate AI Agents in Closed Environments
Astra Group has launched the Astra AI Platform, a low-code constructor designed for creating corporate AI applications that operate entirely within closed circuits without reliance on foreign clouds. The platform targets small and medium businesses as well as large corporations, enabling rapid deployment of AI secretaries, technical support assistants, and other agents in days rather than months. It forms part of the broader Astra AI ecosystem and includes two main constructors: one for machine learning model training and deployment, and another for LLM-based language assistants, document search, and process automation. Users can assemble scenarios from visual blocks, debug them in real time, or extend functionality with custom Python code when needed. The solution supports RAG-based knowledge bases, integration with external tools such as CRM and ERP systems, and the coordination of multiple agents for distributed task handling. One demonstrated use case involves processing ten pages of engineering drawings and specifications in five minutes to prepare data for downstream systems. The product is already listed in the Russian domestic software registry and available to customers.
Multi-Tenancy Isolation in VictoriaMetrics, VictoriaLogs and Grafana: Building Client Separation in a Shared Stack
Voltir runs a single shared monitoring stack consisting of VictoriaMetrics, VictoriaLogs, Grafana and vmalert for all customers instead of deploying separate instances per tenant. Isolation relies on numeric account IDs enforced at every layer: nginx validates tokens against the platform API before proxying writes, Grafana data sources hard-code tenant accounts, and vmalert rules receive automatic account filters. The team discovered that a single malformed rule or template could break alerting for every tenant because vmalert loads the entire rules directory at once. They also found that Grafana automatically created personal organizations granting Org Admin rights, accumulating hundreds of orphaned organizations and users that consumed disk space and resources. A dedicated cleanup module plus hourly reconciliation now removes rules, organizations, series and users when a tenant is deleted, while isolation tests verify both data and API objects across tenants.
The Real Costs of Using Claude and GPT for Russian Businesses Exposed
Accessing generative AI models like Claude and GPT has become straightforward for Russian companies, yet calculating their true expenses remains complex. Hidden factors such as intermediary commissions, currency conversion rates, taxes, and the often-overlooked costs of model reasoning tokens can double or triple initial estimates. Founder Vitaly Nagay of the Heli service analyzed these financial and organizational risks for Russian firms relying on foreign AI providers. In one example, a support department processing 20,000 monthly queries sees costs rise from $240 to $480 when reasoning tokens are included. Nagay recommends evaluating providers by dividing actual ruble charges by the model's official dollar pricing to reveal hidden markups. Additional concerns involve data control, document compliance, and access history when employees use personal subscriptions. Companies are advised to verify billing details, data storage policies, and issue dedicated API keys with spending limits before procurement.