Wednesday, 13 January 2027 · 08:00 – 15:00 UTC
Apply to attend
250 seats, free, reviewed by hand. We prioritise people who build, secure or govern software supply chains day to day, and we balance the room across disciplines, regions and company sizes.
Why we cap it
At 250 people the chat is still readable and your question still gets answered. At five thousand it is a broadcast with a comment section.
Why we review it
So the room is people who work on this, not people prospecting into it. We are not screening for seniority or logos — a solo maintainer counts as much as a bank CISO.
Why nothing is published
Recordings stay with attendees. That is the trade that lets a speaker name the vendor, show the broken config, and describe the incident as it actually happened.
What a seat gets you
Everything, for nothing
A room of ~250 practitioners
Every seat reviewed. No bots, no badge scanners, no drive-by attendees — which is what makes the chat worth reading.
All 13 sessions live
One track, so the whole room shares the same conference and nobody picks between two talks they wanted.
Recordings, for you only
Shared with confirmed attendees within 72 hours. Not published, not on YouTube, not handed to sponsors.
Direct access to speakers
Moderated Q&A in every session, and speakers stay in the channel afterwards. A small room means your question actually gets answered.
Opt-in sponsor contact only
You choose which sponsors may contact you, per sponsor. We never share the attendee list.
Certificate of attendance
On request afterwards, listing the sessions you joined. Accepted by most CPE schemes.
Application
Request a seat
Sign in with Google or LinkedIn so there is a real identity on the application, then it is about three minutes. We reply within three working days, either way. Applications close 11 January 2027, or earlier if we fill up.
Sign-in is not configured yet
This deployment is missing its Supabase environment variables, so the application form is unavailable. In the meantime, email hello@chainday.live and we will sort you out by hand.
Set NEXT_PUBLIC_SUPABASE_URL and NEXT_PUBLIC_SUPABASE_ANON_KEY, then rebuild.