Build whatever fits the problem: an app, an assistant, an agent, a tool, a pipeline. It doesn't have to be an agent. The problem is yours to choose across everyday life, government services, business, education, transport, culture or industry.
Your project has to be built with Hugging Face. That can mean our open-source libraries, our platform, or both. For example:
See the resources section for links to all of these.
Fine-tune only if your project needs it. Plenty of strong projects will just use inference. If you do fine-tune, smaller models are cheaper and faster to work with, but Jobs gives you access to powerful GPUs if you want to go bigger.
48 hours, from Thursday 5:00 PM (Doha time). The moments that matter for builders:
| When | What |
|---|---|
| Thu, 5:00 PM | Kickoff and challenge reveal. Building starts. |
| Fri | Full build day, workshops and a fireside chat. Note: venue pauses 11–1 for Friday prayer. |
| Sat, 2:00 PM | Submission deadline, hard |
| Sat, afternoon | Pitches, judging and awards. |
username/my-model). Confirm your email, because without it you can't use credits or claim the coupon.pip install -U huggingface_hub$100 per team, one shared pool. Nominate one team captain who holds it.
hf auth login --token $TOKENEveryone now draws from the captain's pool, and your work lives under the captain's account. On shared wifi, everyone must be logged in or you'll share one rate-limit pool.hf jobs hardware · Jobs guidehf jobs uv run --flavor a10g-large --timeout 3h train.pypush_to_hub=True or checkpoints), because the job's disk is wiped when it ends.hf jobs ps and hf jobs cancel <id>. Check before you leave at night.Pick whatever fits your project. A few starting points:
There's no team org. Your Space (and your model, if you fine-tuned one) sit under your team captain's account, the one holding the credits that your tokens are tied to. Name them with your Team ID so they're easy to spot:
captain-username/team-NN-<short-name>-appcaptain-username/team-NN-<short-name>Use lowercase and hyphens, add the tag qai-hf-hackathon-2026, and if you have a model, link it from the Space. Then paste the links in the sheet.
Optional: write a short blog post about what you built and drop the link in the "Blog URL" column of the sheet. A nice way to share your work, and we love to see it.
Open the submission sheet →| Criterion | What we look for |
|---|---|
| Impact & relevance | A real, worthwhile Qatar or Middle East problem, solved well |
| Use of Hugging Face | Your project is genuinely built with Hugging Face |
| Technical execution | It actually works end to end |
| Efficiency | Smart, resourceful use of your compute budget |
| Demo & pitch | How clearly and compellingly you show it off |
No. Build whatever fits the problem: an app, an assistant, an agent, a tool or a pipeline. The one requirement is that it's built with Hugging Face.
No, fine-tuning is optional. Many strong projects will just use inference. Fine-tune only if your project needs it.
It must be grounded in Qatar or the wider Middle East. Projects that aren't clearly contextualized to the region will be disqualified.
You can use frontier models around the edges, but your project needs to be genuinely built with Hugging Face, and that's what we score.
Yes, if you're deliberate. Check pricing before big runs, and lean on inference or efficient fine-tuning. No top-ups, so plan it.
No. Working creatively within the budget is part of the challenge.
Hugging Face engineers are on-site as mentors across all 48 hours, so grab them. The event channel (shared with your acceptance email and at kickoff) is your home base for setup, credits, Jobs and submission questions, with office hours each day.
Venue: Nestwork & Scale 7, Abdulla Bin Thani St, Doha. Questions: info@trustqai.com
Scan the QR, or tap the button on your phone, to join the Hackathon01 group — announcements, Q&A and updates during the event.
Join on WhatsApp →Quick links: full agenda · submission sheet