Tutorials Day runs on the Monday before the conference proper — four small benches, twenty to thirty seats each, in the same building. We are looking for maintainers, integrators, hardware folk, protocol authors and anyone who can take a tight group through a hands-on Monday. Half-day or full-day. One form. Ten minutes.
If you have a session you've taught before and want to teach again, a tool whose internals deserve a guided tour, a piece of hardware you can put in the room — send it. The committee reads every proposal. Travel grants are available for accepted tutors who can't otherwise come.
A tutorial proposal lands strongest when the proposer is one of these four. If you are more than one — that is itself a recommendation.
You ship a cryptographic library, a protocol, a CA toolchain, a hardware token, an FFI binding. You know its internals because you wrote them. A tutorial from you is a walking tour of the codebase by the person who put the rooms in.
You ship the library inside a product that runs at scale — an OS, a browser, a payments stack, a regulated medical device, a satellite. Your tutorial is the field report: what we learned the hard way, in production.
You bring kit. HSMs, smartcards, secure elements, dev boards, oscilloscopes. The session is hands-on because there is something to hold. We provide the room and the power; you provide the silicon.
You read the standards, you sit on the committees, you write the conformance suite. A tutorial from you is the room where engineers learn what the standard actually requires — and where the inspectors learn what implementers actually do.
Whatever the topic, a tutorial earns its place by being something the room does, not something the room watches. Three room types map to three shapes of work.
Screen, AV, microphone, sound, projection, a recording rig if you want one. Climate, water, fast Wi-Fi. The same building as the main conference.
Sessions cap at twenty seats; thirty for the code-along horseshoe. Attendees self-select for your topic and are pre-briefed on prerequisites.
A volunteer from the OpenSSL team is present to handle hand-outs, A/V issues, splitting groups, and the parts of the day that aren't you teaching.
Tutors are paid an honorarium proportional to format. Travel grants are available for accepted proposers who otherwise can't make Prague.
A small Křižík plate — a brass-and-enamel pin you wear for the rest of the conference. The hallway then comes to you.
An open bar at the hotel on the Monday evening — light refreshments, the maintainers, and the people who taught the day.
Submit any time. Earlier proposals get earlier feedback. The form takes about ten minutes if you've taught the session before, ~twenty if you're shaping it for the first time.
23:59 CEST. After this, the committee meets weekly to finalise the four benches. Strong proposals received late may still land — please send a note if you need an extension.
Each proposer hears back — accepted, waitlisted, or declined with notes. Accepted tutors get a brief and a producer contact within the week.
The final tutorial line-up publishes on the tutorials page — with seat counts, durations, and pricing — so attendees can buy tickets with the full programme in hand. Tutors are billed for their honorarium & travel after publication.
Four rooms in Prague. Some full day, some split into morning and afternoon halves. You arrive, the room is ready, the producer hands you a microphone. The conference proper starts the next morning.
Four rooms in Prague. Half-day or full-day. More benches still open.
The form is open until 15 June 2026.