Item 1 · Kazakhstan market positioning & compilation baseline date
🇰🇿 Kazakhstan Hub · Scenarios & Local Delivery
Connecting Kazakhstan scenario demand with China's embodied AI solutions: start from public data, verify step by step, deliver locally.
6362
Kazakhstan public enterprise records
3
Industry categories
370
Cities & regions covered
Statistics come from the Kazakhstan public enterprise pool currently loaded in the platform's overseas public-data domain (C0 candidate pool, compiled from public data), contain only publicly compiled information, and change automatically as data updates. Turkmenistan and Tajikistan records are in the public pool but their country hubs are not open yet.
Public-data compilation baseline date for the market positioning and statistics caliber on this page: 2026-09-06 (public-source and desensitization checks completed; enterprise identity not verified). The statistics above are the currently published figures of a dynamic public-data pool (compiled from public data) and are republished as the public data package updates; evidence status across this page follows the labeled verification dates and authorization statuses.
Item 2 · Post-expo scenario progress funnel
From Public Data to Verified Cases (C0→L3)
Every lead starts from the public-data pool (C0): manually curated into a candidate scenario (L1), confirmed with the parties involved on demand and conditions (L2), and finally becomes a mutually confirmed verified case (L3). No presumed demand, no level skipping.
01C0 Public-data candidate
Public enterprise pool
Publicly compiled Kazakhstan enterprise records (C0), for search and candidacy only, without means of reach
02L1 Candidate scenario
Scenario leads
Manually curated into candidate scenarios (L1) with industry, region and task labels
03L2 Contact-confirmed
Contact & confirm
Contact the parties involved and confirm the authenticity of demand and initial conditions (L2)
04L3 Verified
Verified
Demand, budget and delivery conditions all confirmed (L3), entering delivery services
Stage caliber: C0 → L1 → L2 → L3 form the demand-verification main chain (C0 public-data candidates, L1 candidate scenarios, L2 contact-confirmed, L3 verified). P0-P2 are verification-execution stages (P0 scope drafted, P1 verification started, P2 acceptance completed), D1 is formal delivery, and R1 is a replicable case. The public layer only discloses stage statuses that are authorized and redaction-reviewed; conversion counts between stages are not published, and no operating-progress targets appear on this page.
Item 3 · Authorized L2/L3 scenario summaries
Verified Scenario Cases (L3)
Only L3 cases authorized in writing by the enterprise are shown (redacted summary cards).
Verified cases in preparation
Verified Kazakhstan cases will be published after enterprise authorization; the first batch is being connected.
Public summaries only show content that is authorized and has passed redaction review; there is currently no authorized Kazakhstan L2/L3 scenario summary in the public layer. Nothing is pre-listed here — a summary appears only after written authorization and redaction review are completed.
Item 4 · Key industries & first-batch blueprints
Key Industries & Reference Blueprints (Data-driven Projection)
The Kazakhstan public pool currently covers three industry tags — industrial robotics, embodied AI and low-altitude; the blueprint area below is auto-projected from the single global blueprint library by applicable markets, all carrying the "reference blueprint" attribute — derived from industry knowledge and public evidence, not tied to any verified demand side; they are not written as projects before L2 demand is confirmed.
The global blueprint library's applicable markets do not include Kazakhstan yet, so this area shows an honest empty state by the data gate; cards appear automatically once applicable markets extend to KZ, with no hard-coding at the page layer. Turkmenistan and Tajikistan records are in the public pool but their country hubs are not open yet.
Item 5 · Local partner capability network
Local Delivery Partner Network
A "local delivery partner" refers to a local service provider in Kazakhstan (integrator / distributor / maintenance provider) offering installation, operations, spare parts and training support. The platform and partners collaborate per project: the platform handles demand curation, solution matching and verification; partners handle local delivery and after-sales.
- Delivery collaboration: solutions that pass verification are installed, commissioned and maintained by local partners
- Channel and lead referrals: partners refer local demand; the platform provides solution matching and verification
Item 6 · Expo enterprise showcase
Expo Enterprise Showcase (Data-driven Projection)
Relationship types are limited to six labels: public data, expo contact, negotiation in progress, authorized display, verified partner, verified demand; no other relationship wording is used without a written basis. Before written public-display authorization is obtained, only text-only capability cards are published — no company logos, images or material excerpts. The past-expo page (/expo/) remains a historical archive; the "expo contact" label records that contact occurred at an expo and does not imply any relationship between the platform and the expo organizer or the enterprise. Capability profiles' Kazakhstan projection codes are not configured yet, so this area shows an honest empty state by the data gate.
Item 7 · PoC, short-term lease & on-site research entry
Verification First: Paid PoC Service Forms (Historical Examples)
For confirmed scenarios (L2 and above), the platform offers paid PoC (proof-of-concept) services: scope and acceptance criteria are signed first, then execution starts. The following are generic descriptions of historical projects, for service introduction only, not a sales entry.
- Park inspection PoC: wheeled/quadruped inspection solutions are verified on the customer's site for several weeks, delivering a comparison report and landing recommendations.
- Line loading/unloading PoC: robotic-arm loading tasks verify cycle time, success rate and exception recovery, clarifying retrofit boundaries and payback calibers.
The above are service-form descriptions; specific PoC scope, acceptance criteria and commercial terms are signed separately after mutual confirmation; this page is for display only.
Besides paid PoC, the verification-first service includes two more entry forms: short-term lease — equipment and solutions enter verification scenarios via short-term leasing, with lease terms agreed after scope confirmation; on-site research — remote or on-site research for L2-or-above scenarios, producing site information and risk lists. Scope and arrangements for both entries are agreed separately after mutual confirmation, and no commitment is made on this page. Common entry: /services/poc/
Item 8 · Data, wording & authorization notes
Data, Wording & Authorization Notes
- Data caliber: the Kazakhstan public enterprise pool follows the compiled-from-public-data caliber (cleaning + public-source and redaction checks + export whitelist + "compiled from public data" source labeling), with sources compiled as of 2026-09-06; every public card shows its source type, verification status and source-as-of date; statistics come from the dynamic public-data pool. Valuation, ranking, pricing, production, delivery and financing information must carry a source and date, and is marked "to be verified" until evidence is obtained.
- Wording discipline: relationship wording between enterprises is limited to the six relationship labels (public data, expo contact, negotiation in progress, authorized display, verified partner, verified demand); no wording implying cooperation, purchasing or successful delivery is used without a written basis.
- Authorization rule: public display requires written authorization and is labeled per the granted scope; upon revocation, related public content is removed from the next release package.
- Privacy boundary: this page shows no natural-person means of reach, budgets, detailed addresses, unpublished project plans or talk records.
Kazakhstan Local Compliance & Delivery Notes
Generic wording for project planning reference; specific compliance requirements follow current local regulations and professional advice, and no specific legal provisions are cited on this page.
- Local agency: most enterprise-grade deliveries require a locally registered entity or authorized agent for contracting, customs and after-sales
- Compliance access: equipment import, installation and use may involve general requirements such as certification, licensing and personnel qualifications, to be verified item by item in advance
- Language & culture: Contracts, training and documentation are recommended in Kazakh and Russian; on-site communication respects local processes.
- Logistics & installation: Inland logistics lead times and site conditions (winter conditions, power/space/network) should be part of the delivery plan.
Delivery principle: build local service capability first, then execute overseas delivery actions.
