Loading...
Topic: Defence, Sport & Healthcare, Smart City, AI. 18+; no national restrictions in the rules.
Format and location: In-person; Krakow, Poland
Period: 03.10.2026 — 04.10.2026
Registration or submission deadline: 04.10.2026
Current status: Open
Kazakhstan eligibility: Yes — according to the rules
Target audience: Developers, designers, testers, domain experts
Age and other criteria: 18+
Team size: 1–6
Primary language: EN/PL
Fee: A fee may apply if indicated in the form
Awards: Tracks and prize amounts TBA
HackYeah 2026 is an event focused on health, accessibility, and well-being. The stated thematic formulation is: Defence, Sport & Healthcare, Smart City, AI. 18+; no national restrictions in the rules.. The practical value of participating should be assessed not only by the prize amount 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 likelihood of completing a strong submission within the available time. The status in the catalog is Open, and the editorial priority is B — early registration. 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 verifiable user or specialist need does the product solve, and where is the boundary between support and medical approval. A strong team will be able to answer this in one sentence and then prove the answer with a working result. The most appropriate type of final artifact is: a user journey prototype, an explainable model or support service, a scenario for a specialist, and documented limitations. This is an editorial recommendation derived from the topic; the official mandatory format should only be taken from the event website.
In the card, eligibility is marked as Yes — according to the rules. The basis that was verified: 18+; no national restrictions in the rules.. 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 the 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 intended 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 along with a snapshot of the version of the rules. Separately, check if the platform applies its own restrictions, whether a Kazakhstani bank can receive the payment, whether a tax form is required, and whether it is permitted to participate on behalf of a company. These are not additional rules for this hackathon, but a standard risk check for an international application.
Stated audience: Developers, designers, testers, domain experts. Verified criteria: 18+. Information about team composition: 1–6. Before registration, 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 considered permitted. 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 "health, accessibility and well-being", the rational distribution of roles is as follows: developer, UX/accessibility designer, subject researcher, and a person responsible for ethics, data, and fact-checking. 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 contributions, the right to represent the project, repository access, use of the result after the event, and the distribution of a potential prize. Such an internal agreement is a recommendation and does not replace the platform's terms.
The working language is specified as EN/PL. Even if the team communicates in Russian or Kazakh, prepare a unified glossary of terms in advance and designate a person capable of confidently answering jury 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 complex style.
The confirmed format is In-person, location — Krakow, Poland. Start: 03.10.2026; end: 04.10.2026; deadline: 04.10.2026. Transport information: Travel, hotel, and Schengen are at the participant's expense. Availability of an online component per 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 costs. The value recorded for this event: Travel, hotel, and Schengen are at the participant's expense.
The participation cost is recorded as Fee may apply if shown in the form. Prize information: Tracks and prize amounts TBA. 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 appears in a field, or if there is a discrepancy between pages or a requirement for re-verification, the amount cannot be used as guaranteed income.
Even without a cash prize, an event can be useful if it provides a strong case, a public demonstration, feedback, or access to a community. But paid services, travel, and several weeks of work have an opportunity cost. It is better to make the decision to participate 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.
For this direction, the following sequence is useful:
This strategy is not an official evaluation criterion. Its purpose is to help turn a broad topic like Defence, Sport & Healthcare, Smart City, AI. 18+; no national restrictions in the rules. into an honest, verifiable, and completed prototype.
Recorded risk: First-come; price and prizes depend on the form/tracks.. Next recommended step: Register before spots fill up.
The basic card fields are filled, but before registering, you still need to check the exact hours, the current version of the rules, and any changes made after the data collection date.
Practical go/no-go criterion: you should apply if the team documentarily meets the eligibility, has access to the mandatory stack, has time to complete a verifiable scenario, and accepts the financial and logistical risks. You should pause participation if the admission of Kazakhstan, application rights, mandatory in-person presence, cost of critical services, or the procedure for paying out a significant prize is unclear.