Opsphere
← All articles

DevOpsDays for SREs: Find Events, Speak, Turn Talks Into Ops Changes

DevOpsDays for SREs: Find Events, Speak, Turn Talks Into Ops Changes

Session cards leading toward an operations platform

DevOpsDays is the volunteer-run global conference series: check the official events listing for dates and your city page to register or view the program. Each city event follows a consistent format built around curated talks, Ignite talks, and Open Space sessions, though schedules and speaker lineups vary by location and year.

TL;DR:

  • Confirm dates, venues, and ticket availability on the current city page before booking travel, because local teams update schedules independently and TBD listings remain unsettled.
  • City speaking pages list calls for proposals, which usually open months ahead; reviewers favor one concrete lesson over a broad survey.
  • Open Space sessions are run by attendees and scheduled on site; bring specific operational questions, and move rooms when you stop learning or contributing.
  • Streaming and hybrid access vary by city, may cover only stage talks, and can require separate tickets; check registration pages for access and recording details.
Opsphere
Turn DevOps Insights Into Operational Clarity
Opsphere unifies context across cloud, observability and engineering tools, helping teams investigate incidents and make faster operational decisions.

Table of Contents

Upcoming DevOpsDays events: dates and locations to watch

City teams control their own calendars, so dates shift from year to year and some cities list sessions as TBD while logistics firm up. The official events directory stays the single source of truth for confirmed dates, venues, and ticket links, and because local volunteers run each event, attendee experience, sponsorship mix, and topic focus can differ meaningfully from one city to the next even though the global format stays consistent.

A sample of the geographic spread you’ll find on the calendar in a given year:

  • Boston: a long-running US edition with a published multi-day program page covering talks and Open Space.
  • Los Angeles: a West Coast edition with local organizers and sponsors.
  • Regional European cities: Switzerland and other national chapters run events with locally adapted agendas.
  • Egypt and other emerging chapters: newer editions expanding the series into regions with developing cloud and platform engineering communities.

Large-city editions tend to sell out registration faster and draw bigger sponsor pavilions, so checking a city page early matters if you want a seat or a speaking slot. Entries marked “TBD” usually mean the organizing team has committed to a year but hasn’t locked a venue or date, and it’s worth revisiting those pages every few weeks as the event approaches. Because every page is maintained independently, never assume a schedule you saw months ago is still accurate: always pull the date and registration link straight from the current city page before booking travel.

How to attend, speak, or volunteer at a DevOpsDays event

Getting involved takes a few concrete steps, whether you want a ticket, a speaking slot, or a role on the organizing team.

  1. Find your city page through the official events listing and confirm the current date, venue, and ticket link.
  2. Check the speaking page for that city’s Call for Proposals, which typically opens several months before the event and closes weeks ahead of the schedule being finalized.
  3. Submit either a 30-minute talk proposal or a 5-minute Ignite pitch, keeping the abstract focused on one concrete lesson or technique rather than a broad survey.
  4. Register through the ticketing link on the city page, watching for early bird windows and typically limited capacity.
  5. Reach out to the local organizing team listed on the city page if you want to volunteer or help plan a future edition.

Pro Tip: Write your Ignite proposal around a single failure or fix you can walk through in five minutes. Reviewers favor concrete, specific stories over broad overviews.

Organizer contact details live on every city page, and most teams welcome new volunteers year-round, not just in the months before the event.

What to expect on a typical DevOpsDays agenda

A standard day mixes three formats. Morning blocks usually carry curated 30-minute talks from invited or selected speakers. Ignite talks run exactly five minutes with 20 slides that auto-advance every 15 seconds, a structure that forces speakers to cut filler and land one clear point. Afternoons shift to Open Space, where attendees pitch and run their own discussion sessions.

  • Curated talks: scheduled in advance, typically 30 minutes with time for questions.
  • Ignite talks: a strict 5-minute, 20-slide format with automatic slide advancement.
  • Open Space: attendee-pitched sessions scheduled on a board the same day.

The Ignite format’s 20-slide, 15-second auto-advance structure trains speakers to deliver a focused message instead of a rambling one.

Open Space runs on attendee pitches posted to a session board each morning, and sessions follow what organizers call the law of mobility: if a session isn’t teaching you anything or you have nothing left to contribute, you’re expected to walk to a different room. Bring two or three real operational questions you want answered, and jot down outcomes as you go so you have something concrete to act on once you’re back at work.

What to expect on a typical DevOpsDays agenda — overview diagram

How to find a local or nearby DevOpsDays event

Start with the official events calendar and filter by region. Each confirmed city page lists the venue, dates, registration link, and organizer contact in one place, which makes it the fastest way to confirm whether an event near you is still accepting registrations.

  • Check the main events listing first, since it reflects the current status of every chapter worldwide.
  • If no event is scheduled near you, look for recorded talks from past editions or community livestreams shared by local chapters.
  • Search for allied meetups or platform engineering groups in your area as a lower-commitment way to stay connected between conferences.
  • Contact the global organizing team through the organizing guide if you want to discuss starting a new chapter in your city.

Starting a new chapter takes real commitment, but the organizing documentation walks new teams through the requirements step by step.

How DevOpsDays events are organized and governed

DevOpsDays runs on a decentralized model: no single company owns or operates the series. Organizing guidance requires each city’s team to include at least three people from three different organizations, a rule designed to keep events community-run and prevent any one company from using the conference as a lead-generation channel.

Sponsorship follows the same neutrality principle. Local sponsors fund venue, food, and swag costs, but the organizing rules keep the agenda vendor-neutral so sessions stay focused on practitioner experience rather than product pitches. Each city page links to a code of conduct, privacy policy, and sustainability guidance, and attendees are expected to read those before showing up.

Turning conference sessions into operational improvements

The real value of a DevOpsDays event shows up after you leave the venue. Treat every curated talk and Ignite pitch as a candidate for your runbook library: if a speaker walks through a specific alert-tuning technique or incident postmortem structure, write it down and test it against your own production environment within the following week, while the details are still fresh.

Steps from conference insight to tested operational change

Open Space sessions work well as a prioritized backlog of experiments. Each pitch on the board is really a hypothesis someone in the room wants to test, so treat the outcomes as a list of things worth trying, not just notes to file away.

This is also a natural point to evaluate tooling gaps surfaced during sessions. We built Opsphere’s platform engineering use case around exactly this kind of follow-up: connecting incident response and observability tools so teams can act on what they learned instead of rebuilding dashboards from scratch, an approach reflected in how we expanded integrations with PagerDuty and Prometheus.

Practical on-site expectations: what to bring and how the day flows

A typical DevOpsDays day runs from morning registration through an afternoon Open Space close-out, usually eight hours or so including breaks. Bring a laptop for note-taking and Open Space sign-ups, a notebook or app for capturing pitch ideas, and a business card or social handle ready to share since most conversations happen between sessions rather than during them.

Expect registration and coffee to open roughly 30 minutes before the first talk, with curated sessions running through late morning and a lunch break that organizers often use for sponsor booths and informal networking. Open Space pitches typically happen right after lunch, with the board filling up fast, so arrive on time if you want to pitch your own topic. Closing remarks and a wrap-up session usually close out the day, sometimes followed by an informal social gathering.

Comfortable shoes matter more than people expect, since most venues spread talks and Open Space rooms across a full floor or building. Check your city’s program page for exact timing, since start times and break lengths vary by location and venue capacity.

Virtual and hybrid attendance options

Not every DevOpsDays event streams, and the ones that do typically make that clear on the registration page well ahead of the date. When a hybrid option exists, it usually covers curated talks and Ignite sessions, since those are the formats built around a stage and a projector. Open Space sessions are harder to stream meaningfully because they depend on in-room discussion and spontaneous topic pitching, so virtual attendees often get a lighter version of that part of the day, if any at all.

If you can’t travel to a specific city, check that city’s page for a streaming link or recording policy before assuming the event is in-person only. Many organizing teams post recordings of curated talks after the event even when they don’t offer a live stream, which gives remote practitioners a way to catch up on content without needing same-day access.

Hybrid access, where it exists, is usually priced and ticketed separately from in-person attendance, so check the registration flow carefully rather than assuming a single ticket type covers both formats.

Networking and community engagement at DevOpsDays

The format is built for conversation, not just content consumption. Open Space sessions put attendees in small rooms discussing a specific problem, which tends to produce more useful connections than a large keynote audience ever could. The community-first, vendor-neutral design reduces trade-show noise and keeps conversations focused on shared operational problems rather than product demos.

Hallway time between sessions, shared meals, and informal evening meetups organized by local chapters all extend the networking well past the scheduled agenda. Many attendees find that the relationships built during Open Space, where you’ve already worked through a real problem together, carry over into ongoing peer relationships long after the event ends.

If you want to stay connected year-round, look for local meetup groups tied to your nearest DevOpsDays chapter, since many organizing teams run smaller gatherings between annual events. Following a city’s organizing team on social channels is usually the fastest way to hear about those in-between meetups.

Sponsorship benefits and how to become a sponsor

Local sponsorship funds venue costs, meals, and the volunteer-run logistics that keep ticket prices accessible, and most city organizing teams publish a sponsorship prospectus or contact link directly on their event page. Sponsorship tiers typically include booth space, logo placement, and sometimes a short speaking slot, though the vendor-neutral structure means sponsorship doesn’t guarantee editorial influence over the curated agenda.

Because organizing guidance keeps each event’s governance spread across multiple organizations, sponsorship at DevOpsDays functions differently than at a vendor-run conference: you’re funding a community event rather than buying speaking slots or lead lists. For infrastructure and tooling vendors, that makes DevOpsDays a useful venue for visibility among working practitioners, provided you engage through the format’s norms rather than trying to turn sessions into product pitches.

To sponsor a specific event, reach out to that city’s organizing team through the contact information on its event page, since sponsorship decisions and pricing are handled locally rather than through a central office.

Apply what you learn with Opsphere

Conference sessions are most useful when they turn into something you actually ship, and that’s the gap we built our platform to close. Instead of walking away from a great Open Space discussion with a page of notes that never gets revisited, we help you connect the operational tools you already use, AWS, Kubernetes, observability platforms, CI/CD, so the fixes and ideas from a session become a working change instead of a forgotten notebook entry.

Our Developer plan starts at €19 per month, with Team and Enterprise tiers built for larger engineering organizations, and a free Community tier for practitioners who want to try the operational layer before committing budget. If a session leaves you thinking about alert correlation, incident investigation, or infrastructure-as-code visibility, our Terraform-native teams use case and our platform overview show how we bring that operational context into one interface without replacing the tools you already rely on.

Check our pricing and see which tier fits the backlog of experiments you’re bringing home from your next DevOpsDays.

FAQ

Where can I find devopsdays dates and locations?

The official devopsdays events listing lists every confirmed city edition along with dates and registration links. Each city page carries the most current schedule, since local organizing teams update their own pages directly.

How do I submit a talk or Ignite proposal?

Check the speaking page for your target city, since Calls for Proposals typically open several months before the event and close well ahead of the final schedule. Ignite talks follow a strict five-minute, 20-slide format with automatic slide advancement, so proposals should focus on one clear, concrete point.

What happens during Open Space sessions?

Open Space sessions are pitched and scheduled by attendees on-site using a session board, rather than planned in advance by organizers. The format follows the law of mobility, meaning attendees are encouraged to leave a session and join another if they aren’t learning or contributing.

Can I watch devopsdays talks online if I can’t attend in person?

Some city editions offer live streaming or hybrid tickets, though Open Space sessions are rarely streamed since they depend on in-room discussion. Check your target city’s registration page directly, since streaming availability and recording policies vary by event and aren’t centrally standardized.

How do I start a new devopsdays chapter in my city?

Review the organizing guide, which requires a founding team of at least three people from three different organizations to maintain community neutrality. From there, you can contact the global organizing team listed in that guide to begin the process.

OOpsphere
Discuss Your Operational Challenges
Reach out to discuss how Opsphere brings operational context together across cloud, observability, CI/CD, security and engineering tools.

This article is provided for general informational purposes only and does not constitute professional, legal, security, or compliance advice. Please evaluate recommendations against your organization’s specific environment and requirements.