# TTF Hackathon 2026: context for coding agents

Tourism Technology Festival hackathon, Saturday 7 and Sunday 8 November 2026, Messezentrum Salzburg, Hall 10, Floor 1, part of “Alles für den Gast”. Address: Am Messezentrum 1, 5020 Salzburg, Austria.

This feed belongs to the optional buildbar_ setup. Human version: https://buildbar.at/ttf-2026 (German: https://buildbar.at/ttf-2026/de). Official festival information: https://www.tourism-technology.com/en

## Key times (Salzburg, CET)

### Saturday, 7 November

- 10:00 Doors open and registration
- 11:00 Kick-off
- 12:00 Challenge reveal and team building
- 13:00 Hackathon starts

### Sunday, 8 November

- 12:00 Publish your app by now (buildbar_ setup)
- 13:00 Submission
- 14:00 Final pitches

Full agenda: https://www.tourism-technology.com/en

## Challenges

The challenges are revealed on Saturday, 7 November 2026, at 12:00 CET (2026-11-07T12:00:00+01:00). Until then this feed contains no challenge text. Fetch it again after the reveal.

## The buildbar_ setup

- Repo: one per team in the GitHub organisation buildbar-ttf, made from a template with rules and skills. Start with team.md.
- Team facts: call the hub tool `team_info` (slot, team name, slug, app URL, members, n8n URL and project). The team name is not stored in the repo.
- MCP server `buildbar`: https://hub.ttf.buildbar.at/g/<token>/mcp, configured in .mcp.json (Claude Code), .codex/config.toml (Codex) and opencode.json (OpenCode). It offers the n8n-mcp tools plus `team_info`, `publish_app` and `publish_status`. The URL works like a key: never post it and never put it into an app.
- n8n: your team's n8n URL and project come from `team_info` (normally https://n8n.oi.destination.one, one.intelligence by destination.one). Credentials live only in n8n. Keep your workflows as JSON files in the repo.
- AI models: the one.intelligence models in n8n. Your own API keys are allowed, as n8n credentials only.
- Frontend: the Next.js starter in frontend-starter/. The app calls the webhooks of your n8n workflows (allow CORS in the Webhook node). No keys in the app.
- Claude Code in the browser needs the network access “Full” to reach the hub.

## Publishing

1. Commit, then `git push origin HEAD:main`.
2. Call `publish_app`. The app is built from main and served at https://<slug>.ttf.buildbar.at
3. Call `publish_status`. It waits up to 45 seconds inside the hub; if the build is still running, call it again, at most every 30 seconds.

Publish by Sunday 12:00. Shortly before the submission at 13:00, builds queue up.

## Data

- TTF Data Space by nexyo: data for the challenges. Onboarding at https://portal.ttf.nexyo.io/, separate from the buildbar_ setup, registration per challenge. Store your access as a credential in your team's n8n project.
- Open data:
  - OpenStreetMap (https://www.openstreetmap.org/): Places, paths and points of interest. Licence ODbL, credit “© OpenStreetMap contributors”.
  - Open-Meteo (https://open-meteo.com/): Weather forecasts and past weather, no key needed for non-commercial use. Licence CC BY 4.0.
  - data.gv.at (https://www.data.gv.at/): Open government data from Austria.
  - data.ooe.gv.at (https://data.ooe.gv.at/): Open data from Upper Austria.
  - destination.one Open Data (https://open.destination.one/): Open tourism data such as POIs, events and tours. The licence is given per item.
- Basic kit: one.intelligence n8n and models, DataForSEO and Apify through the shared n8n credentials “TTF DataForSEO” and “TTF Apify”, n8n Data Tables.

## Fair play

- No keys in apps: API keys, tokens and passwords stay in n8n credentials. Your app only calls your webhooks.
- Respect data licences: Use data the way its licence allows and name your sources. Partner data from the Data Space comes with its own terms.
- Publish by Sunday 12:00: One hour before the submission at 13:00. Shortly before the deadline, builds queue up.
- Your own setup is welcome: The buildbar_ setup is an offer, not a requirement. Your own tools, accounts and hosting are just as welcome.

## Help on site

Questions about the setup, the hub or publishing: Friedemann Schütz (buildbar_) in Hall 10.