Participation of a team from Kazakhstan

In the card, eligibility is marked as Yes — direct. The recorded basis is: Students worldwide 14+ and recent graduates.. 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" by 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 for and how to build a team

Declared audience: Students/recent graduates. Recorded criteria: 14+; minors parental approval. Team composition info: Up to 4. Before registering, each participant must independently confirm compliance with age, student status, residency, and other personal conditions. If permission for solo participation is not explicitly stated, it should not be assumed to be allowed. If the maximum team size is unknown, do not register extra people until you receive a response from the organizer.

For a task in the field of 'applied technologies and open innovations', a rational distribution of roles looks like this: product lead, developer, designer or subject matter researcher, and the person responsible for testing and submission. 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, 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 who can confidently answer the jury's questions in the required language. For an English-language 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

The fixed format is In-person, location — Barcelona, Spain. Start: 24.04.2026; end: 26.04.2026; deadline: deadline not confirmed. Transport information: Limited reimbursement €120–200; Schengen and remainder self-funded. Presence of an online component on the card: no; signs of mandatory in-person attendance: yes. These signs are obtained only from the text of the 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 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, flight, accommodation, insurance, public transport, meals, and refundable deposits. The phrase 'travel support' does not mean automatic coverage of all costs. The value fixed for this event is: Limited reimbursement €120–200; Schengen and remainder self-funded.

Fee, prizes, and real value

The cost of participation is recorded as Free. Prize information: Sponsor tracks; food/workspace. Before making a decision, separate cash payments, grants, cloud platform credits, subscriptions, equipment, mentorship, and marketing statements about aggregate value. Clarify the number of winning teams, currency, deadlines, taxes, restrictions on receipt, and the need to attend the ceremony. If TBA, page discrepancy, or a re-verification requirement is found in the field, the amount cannot be used as guaranteed income.

Even without a cash prize, the 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. The decision to participate is best made 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

The following sequence is useful for this track:

This strategy is not an official evaluation criterion. Its purpose is to help turn a broad topic like Open tech + sponsor challenges. Students worldwide 14+ and recent graduates. into an honest, verifiable, and complete prototype.

Known risks and gaps

Recorded risk: Reimbursement is limited and paid only after attendance/submission.. Recommended next step: Monitor application and travel reimbursement rules.

The current card lacks confirmation of: exact deadline time and time zone. These points should be treated as open questions, not as permission to act on the most convenient assumption.

Practical go/no-go criterion: you should apply if the team documents eligibility, has access to the required stack, can complete a verifiable scenario, and accepts financial and logistical risks. Participation should be paused if the eligibility of Kazakhstan, submission rights, mandatory in-person presence, cost of critical services, or the payout process for a significant prize is unclear.

Sources and confidence level