Community

TokioConf 2026 slated April 20-22 in Portland, focused on async networking

TokioConf will bring roughly 300 developers to the Hyatt Regency Portland April 20–22 for a three-day, single-track deep dive on async networking with Tokio.

Nina Kowalski3 min read
Published
Listen to this article0:00 min
Share this article:
TokioConf 2026 slated April 20-22 in Portland, focused on async networking
AI-generated illustration

Corrode Dev’s event listing calls TokioConf "The first-ever dedicated conference for developers building high-performance network applications with Tokio and async Rust. A single-track event bringing together ~300 developers from across the Rust ecosystem." The conference is scheduled for April 20–22, 2026 at the Hyatt Regency Portland, 375 NE Holladay St, Portland, OR 97232, and organizers describe a three-day format with one optional workshop day followed by two single-track days of sessions.

Project lead Carl Lerche published a Tokio blog update on March 3, 2026 to mark progress and push logistical clarity. He wrote, "We're about seven weeks out from TokioConf and most of the big planning decisions are behind us. The program is set, including a workshop (somehow, I convinced Alice and Sean to do the workshop with me), the venue, A/V, and social events are figured out." Lerche also singled out conference operations, thanking "Tiffanie who is doing most of the conference organizing."

The update answers a common audience question directly: "Is this just for Tokio core contributors?" Lerche's reply is explicit: "No. The program was selected for people who use Tokio, not just people who work on it. We specifically asked the program committee to prioritize talks where you walk away with something practical to use in your daily work. Adoption stories, production debugging techniques, performance patterns, architectural decisions. If you have a tokio dependency in your Cargo.toml and you're shipping something with it, this conference is for you." The post credits the program committee by name: Armin Ronacher, Jon Gjengset, Conrad Ludgate, Marc Bowes, Sean McArthur, and Alice Ryhl.

Organizers are framing TokioConf as a technical deep dive rather than a broad Rust showcase. TokioRs phrased the difference this way: "Unlike these conferences which cover the Rust ecosystem as a whole, the entire focus of TokioConf is to go deep on one specific area, network programming. This gives us the ability to get in the weeds to talk about how to instrument your Tokio runtime to find that one task blocking the executor. How to reason about async Rust cancellation semantics. What your peers are doing to deploy new services with minimal downtime. These topics are often too detailed for a general conference."

Practical ticket details appear in Corrode Dev and JetBrains coverage: tickets and the program were announced in January, the call for proposals is closed, and listed pricing is Early Bird $650 and General Admission $750. JetBrains publishes a promo line for readers: "Use the code jetbrains10 for 10% off the general admission ticket (excluding any add-ons)."

JetBrains framed the timing as the Tokio ecosystem’s moment: 2026 marks ten years since Tokio was first announced and JetBrains argued that "Tokio and Rust have become one of the default ways companies build infrastructure-level networking software these days." JetBrains also hosted a livestream that featured Carl Lerche and Vitaly Bragilevsky, and the recording is available on JetBrains TV. The company concluded, "Tokio solved async infrastructure and now the ecosystem is evolving toward productivity and full-stack capability."

The March 3 update says it included practical details about logistics, content focus, and accessibility measures; the excerpts available to this report do not enumerate specific accessibility accommodations. With program set, workshops lined up with Carl Lerche, Alice Ryhl, and Sean McArthur, and Tiffanie coordinating operations, TokioConf will convene a focused cohort of production Tokio users in Portland later this month to tackle runtime instrumentation, cancellation semantics, and low-downtime deployment.

Know something we missed? Have a correction or additional information?

Submit a Tip
Your Topic
Today's stories
Updated daily by AI

Name any topic. Get daily articles.

You pick the subject, AI does the rest.

Start Now - Free

Ready in 2 minutes

Discussion

More Rust Programming News