HackNU/26
HackNU/26
Editorial card, not a replacement for official terms. The text below is compiled from structured catalog information and explains how to evaluate the possibility of participating from Kazakhstan. Confirmed facts are clearly separated from analytics and practical recommendations. If the official website or legal rules differ from this card, the most recent version of the organizer's documents always takes priority.
Brief profile
Topic: AI/ML, Software Engineering, Growth. Students of Central Asia; annual series.
Format and location: In-person; Nazarbayev University, Astana
Period: 04.04.2026 — 05.04.2026
Registration or submission deadline: deadline not confirmed
Current status: Completed
Admission for Kazakhstan: Yes — KZ
Target audience: Students
Age and other criteria: Student
Team: 2–4
Primary language: EN
Fee: not published in verified materials
Prizes: 2.8 million ₸
What is this opportunity
HackNU/26 is an event in the field of "artificial intelligence, agents, and data". The recorded thematic formulation is: AI/ML, Software Engineering, Growth. Students of Central Asia; annual series.. The practical value of participation should be assessed not only by the prize size but also by the quality of the task, access to experts, the suitability of the result for a portfolio, the cost of preparation, and the probability of completing a strong submission in the available time. The status in the catalog is Completed, and the editorial priority is A — January 2027. This helps determine the order of work but is not a rating of the organizer and does not guarantee selection or victory.
For this topic, the central product question is: what user solution is improved by the model and why a standard deterministic process is not enough. 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 working vertical scenario, a set of test cases, an evaluation log, an explanation of data and the model, as well as safe error handling. This is an editorial recommendation derived from the topic; the official mandatory format should only be taken from the event website.
Participation of a team from Kazakhstan
In the card, admission is marked as Yes — KZ. The basis that was successfully recorded: Students of Central Asia; annual series.. 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 meaning contains "conditionally", if the evidence is indirect, or if legal rules have not yet been published, it is worth getting a written response from the organizer before spending time.
The recommended request 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 better to save the response together with a snapshot of the rules version. Separately, check whether the platform applies its own restrictions, whether a Kazakhstani bank can receive payment, whether a tax form is required, and whether it is allowed to participate on behalf of a company. These are not additional rules for this hackathon, but a standard risk check for an international application.
Who is it for and how to assemble a team
Target audience: Students. Fixed criteria: Student. Team composition information: 2–4. Before registration, each participant must independently confirm compliance with age, student status, residency, and other personal conditions. Unless permission for solo participation is explicitly stated, it should not be considered permitted. If the maximum team size is unknown, do not register extra people until you receive an answer from the organizer.
For a task in the field of "artificial intelligence, agents, and data," a rational distribution of roles looks like this: ML/agent engineer, product/backend developer, UX/domain researcher, and eval/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 in advance on the contribution, the right to present the project, access to the repository, use of the result after the event, and 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 a person capable of confidently answering the jury's questions in the required language. For an English-language submission, it is better to use short sentences, labels on diagrams, and subtitles for the demonstration. The goal is accuracy, not a complex style.
Format, calendar, and logistics
Fixed format — In-person, location — Nazarbayev University, Astana. Start: 04.04.2026; end: 05.04.2026; deadline: deadline not confirmed. Transport information: Not required. Availability of an online component by card: no; signs of mandatory in-person presence: yes. These signs are derived only from the field text and do not override event-specific rules.
For an online format, it is important for a team from Kazakhstan to convert the deadline to their time zone, check the time 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 moment of submission. For an in-person or hybrid format, first calculate the full budget: visa, flights, accommodation, insurance, local transport, food, and refundable deposits. The wording "travel support" does not mean automatic coverage of all expenses. The value fixed for this event: Not required.
Fee, prizes, and real value
Participation cost is recorded as not published in verified materials. Prize information: 2.8 million ₸. Before making a decision, separate cash payments, grants, cloud platform credits, subscriptions, equipment, mentorship, and marketing wording about total value. Clarify the number of awarded teams, currency, deadlines, taxes, receipt restrictions, and the need to be present at the ceremony. If TBA is encountered in a field, page discrepancies, or a re-verification requirement, the amount cannot be used as guaranteed income.
Even without a cash prize, an event can be useful if it provides a strong case, public demonstration, feedback, or access to a community. But paid services, travel, and several weeks of work have an alternative cost. It is better 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 direction, the following sequence is useful:
- Research. First, define the task and the basic non-AI process, collect a small representative eval-set, then choose a minimal model and tools. Do not start with a list of technologies: first formulate the user, the problem, the basic process, and the observable success criterion.
- Project scope. Choose one end-to-end scenario that can be run from start to finish. Write down the features deliberately left out of the hackathon version.
- Proof. Key metrics: quality on a fixed set, share of successfully completed tasks, latency, request cost, resilience to bad input, and human evaluation of utility. Fix the baseline value before improvement and the test conditions so the result does not look random.
- Reliability. Check for empty, erroneous, and edge inputs, unavailability of an external service, and understandable recovery. Do not send secrets and personal data to external models, verify facts, disclose AI usage, and separate demonstration results from overall performance.
- Demonstration. Show a normal example, a complex or erroneous input, a trace of key steps, the measured result, and a safe handover to a human in case of uncertainty. Keep a backup local recording in case of a network error, if the rules allow.
- Submission. Link every claimed advantage to a screen, measurement, source, or feedback. Clearly separate what works now from plans after the hackathon.
This strategy is not an official evaluation criterion. Its purpose is to help turn the broad topic of AI/ML, Software Engineering, Growth. Central Asian students; annual series. into an honest, verifiable, and completed prototype.
Known risks and gaps
Fixed risk: 24 hours in-person; acceptance and exact rules of the future cycle TBA.. Next recommended step: Monitor January–March 2027.
The current card does not sufficiently confirm: the exact time and time zone of the deadline; participation cost and mandatory payments. These points should be considered open questions, not permission to act on the most convenient assumption.
Practical go/no-go criterion: it is worth applying if the team documentarily meets the eligibility, has access to the mandatory stack, has time to complete the verifiable scenario, and accepts financial and logistical risks. Participation should be paused if the admission of Kazakhstan, submission rights, mandatory in-person presence, cost of critical services, or the order of payment of a significant prize are unclear.
Sources and confidence level
- Official event page.
- Rules or additional source.
- Fixed proof of admission: Central Asian students; annual series..
- The date and version of the documents may change; open both links again before acting.
Summary: HackNU/26 looks like an opportunity on the topic of "artificial intelligence, agents, and data" with the status Completed and a Kazakhstan participation rating of Yes — KZ. The recommended action is to Monitor January–March 2027. The decision should be made after closing the listed gaps, not just based on the attractiveness of the topic or the prize title.