Evidence note: This article draws on Docker’s official announcement. It establishes what Docker advertised, not independent confirmation that sessions took place or that demonstrated technologies achieved particular results. The relevance filter below is editorial analysis, not a product test.
Docker Announces Pavilion Sessions and Speakers
Docker’s September 22, 2026 announcement listed partner and customer speakers for its Pavilion at WeAreDevelopers World Congress North America, scheduled for September 23–25 in San Jose. The announced program covered practical AI, security and development. Those dates have now passed; the post is an announced agenda rather than a report of completed sessions. Docker’s announcement
For individual developers and small teams building AI tools, the agenda offers relevant subjects to investigate. Its usefulness depends on whether a session addresses a specific engineering decision, rather than simply sharing the team’s interest in AI.
Practical AI, Security and Development: The Announced Topics
Three examples illustrate the program’s scope:
- AI: Docker listed Spectro Cloud’s Colton Shaw presenting repeatable agent workloads and edge deployments.
- Security: Docker listed Datadog’s Amrita Lakhanpal presenting an agent incident workflow spanning detection, investigation and response.
- Development: Docker listed J.P. Morgan Payments’ Alan Torrance presenting a Docker Compose example for working with payment APIs.
These were advertised presentations in Docker’s session listing.
A useful relevance filter separates those subjects by the decision a team needs to make:
| Subject | Team question | Evidence worth seeking |
|---|---|---|
| AI | Can the deployment approach fit the team’s target environment? | Required infrastructure, model dependencies and behavior when connectivity fails |
| Security | Can the team investigate and contain an unwanted agent action? | Recorded activity, enforcement points and a demonstrated failure case |
| Development | Can the example help reproduce an integration locally? | Runnable instructions, prerequisites and a clear distinction between mock and live services |
These are evaluation criteria, not claims that the presentations supplied those answers. A topic match earns further attention; it does not establish suitability for deployment.
Docker Invites Attendees to Meet the Teams Building and Using the Technologies
Docker also invited attendees to meet partners, customers and speakers, compare approaches and ask questions about the featured technologies. Docker’s invitation
That invitation serves a different purpose from the session list. A presentation can introduce an approach; a conversation can probe whether its assumptions fit a smaller team’s constraints.
Useful questions distinguish the builder’s perspective from the operator’s: What must be configured? What failed during adoption? Which parts require ongoing maintenance? What evidence can another developer inspect afterward? The invitation itself does not establish who was available for individual discussions or what answers attendees received.
Developer Takeaway: Check the Session Details Against Your Team’s Questions
The announced subjects are relevant to teams evaluating AI deployment, agent security or development integrations. To allocate limited conference time—or decide which speakers and materials merit follow-up—apply a simple filter:
- Name one unresolved decision. For example, whether an agent needs offline execution or how its actions will be audited.
- Match the decision to a specific session description. A broad AI label is insufficient.
- Define the evidence needed. Request prerequisites, a reproducible example, operational limitations or a failure demonstration.
- Separate conversation from validation. Treat a useful discussion as a lead for further evaluation.
For this September program, whether recordings, runnable examples or follow-up access are available remains open. The concrete next question is: Which advertised session could supply evidence for the team’s next development decision?