FastAPI Conf Is Oct 28. Your OpenAPI File Is the Talk

FastAPI Conf ‘26 is on the official site as October 28, 2026, Amsterdam, an official event by FastAPI, at Transformatorhuis · De Wester in Westerpark. One day. The homepage already lists Sebastián Ramírez, Samuel Colvin, and Marcelo Trylesinski in the same speaker grid. That is the framework, the validation library, and the Starlette/Uvicorn maintainer. If you ship a FastAPI app, those names are the stack, not a keynote theme.

The after-party page, which search indexed this week, puts attendees at Blast Galaxy from 7 p.m., a 15–20 minute walk from the hall, badge required, food not included. Tickets are the CTA on the homepage. The schedule page still has to be the thing you actually read before you book a flight.

What the site will commit to

Date: October 28, 2026. City: Amsterdam, NL. Venue: Transformatorhuis, De Wester. The location block also prints 52.386807° N, 4.869844° E. “Get your ticket” and “View the schedule” are the two buttons.

Speakers named on the homepage in the extract:

• Sebastián Ramírez, creator of FastAPI
• François Voron, lead engineer at Polar
• Samuel Colvin, founder of Pydantic
• Ben Falk, principal cloud engineer
• Marcelo Trylesinski, Starlette and Uvicorn maintainer
• Jason Liu, developer experience engineer
• Paige Bailey, developer relations lead
• Pieter Cailliau

The schedule fragment that extracted includes Colvin’s “Constrained Optimism,” an open panel with the FastAPI team, closing, then the after-party. That is not a full timetable. Do not invent talk lengths.

The site describes a code of conduct that attendees, speakers, sponsors, and volunteers have to follow. Sponsor copy still lists gold and silver as open. Diamond is a heading. None of that is a talk.

After party: Blast Galaxy, arcade, all conference attendees welcome, 7 p.m., 15–20 minutes on foot, bring the badge, buy your own food and drinks. If you skip it you still got the day. If you go, the badge is the ticket they named.

Why this is a web-dev note and not a travel blog

FastAPI talks are usually “we rewrote the service.” This lineup is the people who own the dependencies your requirements.txt already pins. Colvin on the same day as Ramírez is a Pydantic version conversation with a microphone. Trylesinski in the same grid is your ASGI server and the Starlette BaseHTTPMiddleware stack you copied in 2023.

We already had to treat Starlette’s BadHost CVE as a FastAPI inheritance problem. A maintainer on stage does not patch your pin. It does mean the Q&A is a place to ask which version they want you on before you freeze a Docker image for winter.

Cloudflare’s Python Workers going GA without bringing Uvicorn is the other edge of the same week-to-week beat: FastAPI as a local server versus FastAPI as a shape that other runtimes keep trying to host. Amsterdam will not resolve that. It will put the FastAPI team in a room where someone can ask it without a GitHub reaction emoji.

Django shops are not the audience on the after-party page (backend, API architects, Python, ML/AI, “builders”). If you are in the middle of Django 6.1.2’s CVE set, this conference is still not your patch window. It is a FastAPI-source day. Go if that is your stack. Do not go to “keep up with Python web” in the abstract.

What to freeze in git before you buy a ticket

Export the OpenAPI file your production app actually serves. Not the one in /docs on your laptop. The one behind the gateway. If Colvin talks about constrained types, you want a JSON file you can grep, not a memory of a route.

Pin FastAPI, Starlette, Uvicorn, and Pydantic with hashes, then note the versions in the PR you would be embarrassed to show a maintainer. If you are four minors behind, the conference is not going to shorten that diff.

Write down one production incident from the last year that was a validation miss, a startup import, or a middleware order bug. Those are the questions that belong in a hallway. “What is FastAPI’s vision” is not.

If you cannot name the Starlette version, you are not ready to ask Trylesinski anything useful. pip show is cheaper than KLM.

Workers who cannot go should still do the OpenAPI export. The recordings, if they appear, will land after your November freeze. The pin can happen Monday.

Tickets, travel, and the 423 joke

The after-party page’s sample app raises HTTP 423 on /schedule with detail “Compiling talks…” That is site chrome. Believe the schedule button on the homepage more than a joke snippet, and re-check it the week you fly.

Transformatorhuis is a hall in Westerpark. The site’s own copy says talks, lunch, and coffee in that building. Blast Galaxy is a separate walk after 7 p.m. Do not assume the arcade is next door.

Food at the after-party is not in the ticket. Budget dinner. Badge at the door is in the ticket. Screenshot the attendee email.

Sponsorship is still “accepting applications” in the extract. That is for vendors. It does not change whether you should attend.

If your company needs a reason: it is the first official FastAPI conference, on the project’s own site, with the author and the Pydantic founder listed. That is a sharper reason than most Python days. It is still one day. Do not build a 2027 roadmap out of a panel.

What not to announce on October 29

Do not blog that FastAPI “won” web Python because a conference existed. Django did not vanish on October 28.

Do not treat a hallway quote as a deprecation schedule. Wait for a release note.

Do not skip the Starlette CVE you have not pinned because you are packing. The conference does not close CISA tickets.

Do not skip the OpenAPI export because you expect a recording. The useful artifact is your schema, not their slides.

A Monday checklist if you are staying home

1. Dump /openapi.json from production to git.
2. Record FastAPI / Starlette / Uvicorn / Pydantic versions.
3. Open the issue list you have been ignoring that mentions validation or middleware.
4. Read the Conf schedule the week of the 28th and pick one talk title to watch later.
5. Leave the after-party to the people in Amsterdam.

Bring a printed list of pinned versions in your pocket if you are the person who will actually ask a question. Phones die. Maintainers remember the person who had a version number.

If your app is FastAPI on Uvicorn behind nginx, say that in the question. If it is FastAPI’s shape on a worker runtime, say that instead. Mixing them is how you get an answer for a process you do not run.

Constrained types are Colvin’s home turf. If your models are all str and int with a prayer in the route, the talk title “Constrained Optimism” is not aimed at you until you read the OpenAPI file and see how much of it is unconstrained. You do not need the talk to add a constr or a Field. You need the talk if you already did that and still got a surprise at the boundary.

Ramírez on a one-day official event is not a product launch by default. Do not pre-write “FastAPI 1.0” posts. Wait for a version tag.

People flying in should treat lunch-in-the-hall as the networking block the site already described. The after-party is arcade lighting and a cash bar. Useful, optional, not the Q&A.

Remote teammates can still watch the speaker list and map each name to a library they pin. Ramírez → FastAPI. Colvin → Pydantic. Trylesinski → Starlette and Uvicorn. Voron, Falk, Liu, Bailey, Cailliau → read their profile pages on the site before you quote them. The extract gave job titles, not talk abstracts.

October 28 is a Wednesday. If you need manager approval, send the official URL, the speaker grid, and the one-day constraint. Do not send a Medium recap from August. The after-party page update this week is the live site.

Westerpark is not Schiphol. Budget the tram or the walk from wherever you actually sleep. The coordinates on the site are for the hall, not the arcade.

If you only have budget for one Python event this fall, compare this to a general conference by looking at whether your open issues mention FastAPI, Pydantic, or Uvicorn. If they mention Django’s GIS CVE from last week, stay home and patch. If they mention request validation and lifespan startup, Amsterdam is the more honest spend.

Code of conduct is on the site. Read it. That is not filler. Official events that skip it are the ones you should skip.

Sponsor logos will be on the hall screen. They are not a talk. Redis posted about heading to Amsterdam; that is a vendor travel note, not a schedule. Gold and silver applications being open means the money is still being raised. It does not mean the speakers are tentative. Ramírez and Colvin are already on the grid.

If your team cannot fly, assign one person to watch the schedule on the 28th and drop timestamps in the engineering channel. That is cheaper than three tickets and still more useful than a summary tweet.

Lunch is listed as part of the day at the Transformatorhuis. Use it. The Blast Galaxy walk is after 7. Do not skip lunch to “network later” at an arcade that sells its own food.

Pin versions on Monday even if the ticket is declined. The conference is a calendar object. The lockfile is the artifact you still have in November, when the hall is empty and Starlette has shipped another patch. Dump OpenAPI the same day so the November you has a file to diff, not a memory of Amsterdam. Hash-pin FastAPI, Starlette, Uvicorn, and Pydantic in that same PR even if nobody is flying. Write the four version numbers in the PR body so the diff is searchable later. Do not keep polishing that same PR all week.

If you are going, the same five steps still apply, plus a badge and a 7 p.m. walk if you want the arcade. The Transformatorhuis day is the product. Blast Galaxy is optional. Your lockfile is not.