VibeKode Berlin 2026: Dates, Tracks, Tickets & AI Native Week
November 16-20, 2026
VibeKode Berlin 2026, billed as The Vibe Coding Conference, runs November 16-20, 2026 at the Maritim proArte Hotel on Friedrichstrasse. Bootcamps land November 16-17, the main conference and expo November 18-19, and...
VibeKode Berlin 2026, billed as The Vibe Coding Conference, runs November 16-20, 2026 at the Maritim proArte Hotel on Friedrichstrasse. Bootcamps land November 16-17, the main conference and expo November 18-19, and Power Workshops November 17 and 20. Four tracks: AI Coding, Agentic Development, AI-Driven Software Delivery, and AI-Native Teams. Early-bird All Access is 1,799 EUR through September 10 (checked 2026-08-24, vibekode.it/berlin/tickets-berlin). No 2026 programme is published yet.
I run StackVerdict’s AI events hub, and VibeKode is the event on it I have gone back and forth on most. A conference named after a phrase that started as a half-joke is easy to be sniffy about. The subject underneath the name is the one genuinely new engineering discipline of this cycle, and almost nobody is programming two full days on it. AI conferences cover models. DevOps conferences cover delivery. The craft change in between, what happens to review, architecture and mentoring when most of the code is generated, is largely unserved.
The one fact that decides the whole booking
VibeKode Berlin’s price list is identical, line for line, to MLcon Berlin’s and the API Conference Berlin’s. Same five tiers, same numbers, same September 10 deadline, same 299 EUR week upgrade. That is not a coincidence and it is not laziness. Four conferences from one publisher run in the same building, on the same days, with one shared price sheet.
Which means your base-ticket choice costs you nothing. The only real question is which room you want to sit in by default. Pick VibeKode if you build with AI assistance day to day. Pick MLcon Berlin 2026 if you build the models. Pick the API Conference Berlin 2026 if you build the interfaces the agents run on top of. The 299 EUR upgrade adds the other three regardless.
VibeKode Berlin runs a five-day, not-five-equivalent-day schedule
The core is Wednesday and Thursday. A conference-only attendee needs Tuesday night to Thursday evening. Bootcamp buyers start Monday. A Friday workshop buyer stays to the end of the week.
| Day | Date | What runs |
|---|---|---|
| Monday | Nov 16 | Bootcamp day 1 |
| Tuesday | Nov 17 | Bootcamp day 2 and Power Workshops |
| Wednesday | Nov 18 | Conference day 1 and expo |
| Thursday | Nov 19 | Conference day 2 and expo |
| Friday | Nov 20 | Power Workshops |
Maritim proArte sits on Friedrichstrasse in Mitte, about as central as Berlin gets. Friedrichstrasse station is a few minutes on foot with S-Bahn, U-Bahn and regional services. Mid-November is off-peak for Berlin tourism, so hotel rates are modest by European conference standards. This is a materially cheaper week to attend than a December event in the same city.
The two tracks worth flying for are the ones nobody else programs
The published list walks outward from the keyboard.
- AI Coding
- Agentic Development
- AI-Driven Software Delivery
- AI-Native Teams
Tracks one and two are the obvious content and the most likely to attract tool demos. Tracks three and four are why the trip earns its ticket.
AI-Driven Software Delivery is the concrete engineering problem underneath most agentic ambitions: what your agent can reach, how it authenticates, what it is allowed to change, and the blast radius when it is wrong. The Munich edition framed this track around connecting AI and MCP, and the model context protocol is where these arguments currently get settled in practice. If you are going, our MCP servers report is the useful preparation. It ranks that layer on real adoption and maintenance signals, with a security pillar fed by the GitHub Advisory Database, and it will tell you within minutes of a session whether the speaker has operated this or only demoed it.
AI-Native Teams is the track most conferences skip because it does not demo. Who reviews generated code and how long that takes. How you hold architectural coherence when output volume triples. What code ownership means when nobody typed the code. What happens to mentoring when the junior task has been automated. Those are the questions engineering managers actually ask me, and they are chronically under-programmed. Well cast, this is the most valuable two half-days of the week.
Worth noting what is absent: no track on evaluation, testing or verification of generated code. That is arguably the discipline’s biggest open problem, and its absence from a four-track list is a fair criticism of the programme’s shape.
VibeKode Berlin 2026 ticket prices, with the numbers that actually matter
All prices in EUR, already including the 10% team discount for bookings of three or more tickets, plus VAT.
| Ticket | Early bird | Regular | Saving |
|---|---|---|---|
| All Access (5 days + bootcamps) | 1,799 | 2,299 | 500 |
| 4-Day Pass | 1,349 | 1,799 | 450 |
| 3-Day Pass | 1,169 | 1,454 | 285 |
| 2-Day Pass | 899 | 1,199 | 300 |
| Workshop Day | 559 | 732 | 173 |
| AI Native Week upgrade | 299 | 299 | n/a |
Prices checked 2026-08-24 on vibekode.it/berlin/tickets-berlin.
The 3-Day Pass is the practical floor. At 1,169 EUR it covers both conference days plus one bootcamp or workshop day, which is the minimum configuration where a hotel-format event does something a recorded talk cannot. The 2-Day Pass at 899 EUR buys the conference days and an expo, and at a young event the expo is not a reason to fly anywhere. The 270 EUR step up is the best marginal spend on the standard list.
The 4-Day Pass carries the deepest advertised cut and the weakest case. It saves 450 EUR against 285 EUR on the 3-Day Pass. If a fourth day is genuinely useful to you, the early-bird window is the cheapest it will ever be, at 180 EUR of real difference over the 3-Day Pass. If it is not, the discount is not a reason to buy it.
September 10 is a cliff, not a slope. No later discount tier is published. After that date you pay the regular column.
The 299 EUR AI Native Week upgrade is the strongest add-on I have priced this year
Run the comparison. One extra workshop day on VibeKode’s own price list costs 559 EUR. Three additional conferences cost 299 EUR. That is nearly half the price for many times the content. Anyone booking a VibeKode ticket without at least pricing the upgrade is leaving money on the table.
For a vibe coding audience the bundle is unusually well matched. VibeKode covers the practice of building with AI. The API Conference’s APIs for AI & Agentic Systems track covers the interfaces that practice runs on top of. MLcon’s agent, RAG and MLOps tracks cover the models and operations underneath. Those are three layers of the same stack, sold as three conferences in one building.
The honest caveat: access is not attendance. You still have two conference days and one body, and four parallel programmes buys optionality, not volume. Where it clearly pays: you sit between disciplines (a developer being pulled into agent work, or a platform engineer who has inherited the AI tooling decision), you send two or three people who can split across conferences, or you want the recording library across four programmes instead of one.
Where it does not pay: one person with one narrow objective and a habit of conference-hopping will fragment the week and see the first ten minutes of a lot of talks. Under those conditions, staying in VibeKode and going deep is the better outcome, and skipping the upgrade is a legitimate choice.
Berlin beats Munich and Utrecht on every checkable number
VibeKode runs in several cities. The editions are not equivalent.
Munich 2027 is undated. The official Munich page reads “2027 | Munich and online” with a newsletter signup to be told when tickets go on sale. No dates, no venue, no prices, no tracks. The programme and pricing blocks lower down that page are still the leftover June 2026 edition, so a quick read leaves you budgeting against dates that have already passed. There is nothing to book (checked 2026-08-24, vibekode.it/munich).
Munich was also the more expensive edition. The June 2026 Munich all-inclusive ticket discounted to 2,069 EUR against the same 2,299 EUR regular price. Berlin discounts the equivalent tier to 1,799 EUR, 270 EUR cheaper, and throws in three co-located conferences for 299 EUR that Munich did not have.
Utrecht on October 5-7, 2026 is a three-day standalone. Dated and bookable, and earlier if your training budget expires in Q3. Not inside AI Native Week, so no four-conference upgrade attached.
Berlin if you want the most content per euro. Utrecht if you need it before October. Munich only if you live there and can wait for an announcement.
The whole risk of this event, and where I would spend the money anyway
Go if a meaningful share of your team’s code is now machine-generated and you have not yet worked out what that does to review, architecture and onboarding. AI-Driven Software Delivery and AI-Native Teams address questions almost nobody else is programming, and at 1,169 EUR plus 299 EUR you are buying four conferences in central Berlin for less than the standalone price of most single AI conferences.
The risk is real. No programme, no session titles, no names, across all four AI Native Week conferences. For an established discipline that would be a minor annoyance. For a field this young it is the whole variable, because vibe coding sessions in 2026 split cleanly into two kinds: people reporting what actually happened when they changed how their team works (including the parts that went badly), and people showing you a tool. The first is worth the airfare. The second is a YouTube video you could watch for nothing.
There are roughly three weeks between now and the September 10 deadline. Check the programme page again before you commit. If it is still empty and you need certainty, accept you will pay the regular column. That is the real trade.
My go-or-skip. Buy the 3-Day Pass plus the 299 EUR upgrade before September 10 if you are going. That lands around 1,468 EUR and is the strongest configuration on the sheet. Make VibeKode your base ticket if your work is hands-on building with AI assistance. Make MLcon or the API Conference your base if it is models or interfaces, since the price is identical either way. Go online if travel is the constraint. Skip it if you need a confirmed speaker lineup before you pay, or if what you actually want is model and infrastructure content rather than craft and team content.
For the practical grounding either way, the AI tools I recommend to developers is where I keep what has survived my own testing. That is a decent baseline to judge a vibe coding session against.