For this theme, the central product question is: what physical operation does the system perform more reliably, safely, or cheaply than the existing process. A strong team will be able to answer it in one sentence and then prove the answer with a working result. The most appropriate type of final artifact: a testbed or digital twin, component diagram, firmware and service, measurement log, video of real behavior, and a safe-fail plan. This is an editorial recommendation derived from the theme; the official mandatory format must be taken only from the event website.

Participation of a team from Kazakhstan

In the card, eligibility is marked as Yes — KZ. The recorded basis is: XII season; KZ and Central Asia.. These two lines must be read together. The phrasing "Kazakhstan is not excluded" is weaker than a direct invitation to participants from all over the world, and the word "international" itself does not always mean the absence of restrictions on citizenship, residency, place of study, age, or sanctions compliance. If the value contains "conditional", if the proof is indirect, or if the legal rules have not yet been published, it is worth getting a written response from the organizer before spending time.

The recommended inquiry to the organizer should state the country of residence and citizenship, the proposed team composition, age or student status, the method of receiving the prize, and the chosen format of participation. It is best to save the response along with a snapshot of the rules version. Separately check whether the platform applies its own restrictions, whether a Kazakhstani bank can receive the payout, whether a tax form is required, and whether participation on behalf of a company is allowed. These are not additional rules of this hackathon, but a standard risk check for an international application.

Who is it suitable for and how to assemble a team

Target audience: Robotics/AI teams. Fixed criteria: Exact age TBA. Team composition info: not published in verified materials. Before registration, each participant must independently confirm compliance with age, student status, residency, and other personal conditions. If individual participation is not explicitly permitted, it should not be assumed to be allowed. If the maximum team size is unknown, do not register extra people before receiving a response from the organizer.

For a task in the field of 'hardware, IoT, and engineering systems', a rational distribution of roles looks like this: embedded/hardware engineer, backend or edge developer, test engineer, and product/demo lead. One person can combine several functions, but there must be clear owners of the product, technical result, quality assurance, and final submission. It is useful to agree in writing beforehand on the contribution, the right to represent the project, repository access, use of the result after the event, and the distribution of the potential prize. Such an internal agreement is a recommendation and does not replace the platform's terms.

The working language is specified as EN. Even if the team communicates in Russian or Kazakh, prepare a unified glossary of terms in advance and designate a person who can confidently answer the jury's questions in the required language. For an English submission, it is better to use short sentences, captions on diagrams, and subtitles for the demonstration. The goal is accuracy, not a complex style.

Format, calendar, and logistics

Fixed format — In-person, location — Almaty Arena. Start: 30.06.2026; end: 01.07.2026; deadline: deadline not confirmed. Transport information: Not required. Online component availability: no; signs of mandatory in-person presence: yes. These signs are obtained only from the text fields and do not override event-specific rules.

For the online format, it is important for a team from Kazakhstan to convert the deadline to their time zone, check the schedule of mandatory sessions, the upload speed of large videos, and the availability of all APIs. Create a technical buffer of at least a few hours and do not leave registration until the submission deadline. For an in-person or hybrid format, first calculate the full budget: visa, flight, accommodation, insurance, public transport, meals, and refundable deposits. The phrase 'travel support' does not mean automatic coverage of all expenses. The fixed value for this event: Not required.

Fee, prizes, and real value

Participation fee is recorded as not published in verified materials. Prize information: not published in verified materials. Before making a decision, separate cash payouts, grants, cloud platform credits, subscriptions, equipment, mentorship, and marketing statements about total value. Clarify the number of winning teams, currency, deadlines, taxes, restrictions on receipt, and the requirement to attend the ceremony. If TBA, page discrepancies, or a re-verification requirement appear in the field, the amount cannot be used as guaranteed income.

Even without a cash prize, an event can be useful if it provides a strong case study, a public demonstration, feedback, or access to a community. However, paid services, travel, and several weeks of work have an opportunity cost. It is best to make a decision about participation based on three questions: can the mandatory requirements be met; can a convincing result be assembled on time; will the created artifact be useful after the winners are announced?

Recommended project strategy

For this track, the following sequence is useful:

This strategy is not an official evaluation criterion. Its goal is to help turn the broad topic of Humanoid Unitree, navigation, locomotion, manipulation. XII season; KZ and Central Asia. into an honest, verifiable, and complete prototype.

Known risks and gaps

Recorded risk: Age/team cap are not visible in the available rules text.. Next recommended step: Monitor April–June 2027.

The current card does not sufficiently confirm: the exact time and time zone of the deadline; the limit and rules for team formation; the cost of participation and mandatory payments; the structure, currency, and procedure for paying prizes. These points should be considered open questions, rather than permission to act on the most convenient assumption.

Practical go/no-go criterion: it is worth applying if the team documentarily meets eligibility, has access to the required stack, has time to complete the verified scenario, and accepts financial and logistical risks. Participation should be paused if Kazakhstan's eligibility, submission rights, mandatory in-person presence, the cost of critical services, or the procedure for paying a significant prize are unclear.

Sources and level of reliability