Devoxx Morocco 2026 will run on November 4–5 at the DoubleTree by Hilton Casablanca City Centre, marking the 13th edition of a conference that has become a fixture for the country’s Java community. The published programme points to a broader shift: Java remains the foundation, but the sessions increasingly address the systems built around it — containers, orchestration, distributed architecture, interoperability protocols and AI-enabled development.

Key Takeaways

  • Devoxx Morocco 2026 is scheduled for November 4–5, 2026, at the DoubleTree by Hilton Casablanca City Centre, Avenue Pasteur, Casablanca.
  • The 13th edition lists themes spanning Java, cloud, containers, cloud-native development, DevOps and culture, architecture, machine learning and AI, web, mobile, IoT and blockchain.
  • A standard conference pass costs MAD 2,500 plus 20% VAT and covers two days of sessions, lunch and coffee breaks.
  • Listed sessions point to cloud orchestration, microservices decision-making, multi-agent interoperability through Google’s A2A protocol and a Java SDK, and quantum-safe cryptography.
  • Public information does not confirm attendance figures, the full speaker roster or the final schedule; those details should be checked against the official programme.

What the 2026 edition confirms

The core logistics are settled. According to the official conference site, the event takes place on Wednesday and Thursday, November 4–5, 2026, at the DoubleTree by Hilton Casablanca City Centre on Avenue Pasteur. This is the 13th edition, positioned as a developer-learning event for Africa and the MENA region, with expert-led sessions, practical workshops and networking with international specialists.

A standard pass is priced at MAD 2,500 plus 20% VAT, including two days of sessions, lunch and coffee breaks, as listed on the registration page. Proposals for the call for papers were invited until July 5, 2026, with review beginning immediately after submission, according to the CFP platform.

The 13th edition matters in itself: it indicates a sustained community platform rather than a one-off technology expo. What the public record does not establish is scale. Attendance figures, the number of sessions, the share of Moroccan speakers and any economic impact on Casablanca are not confirmed in the available material and should not be inferred from the event’s regional positioning.

Why cloud-native anchors the agenda

Cloud-native engineering changes the unit of work. Instead of treating a Java application as the deliverable, teams operate a continuously running platform: containers, orchestration, service decomposition, deployment automation, resilience, observability, infrastructure as code and secure software supply chains.

Devoxx Morocco’s published themes explicitly include cloud, containers, cloud-native topics, DevOps and culture. The 2026 programme also lists a session titled “Bare-Metal Isolation: Engineering a Cloud Orchestrator for Next-Generation Workloads,” which signals interest in infrastructure design and workload isolation beyond basic deployment. Another, “Building an Everything Micro Architecture: Real Decisions, Real Code, Real Deployments,” suggests a practical treatment of microservices and distributed systems rather than an abstract one. The mobile event listing carries the programme details.

That emphasis is relevant for Moroccan companies that have already adopted microservices — or are weighing the move — and now face operational complexity, team boundaries, latency, reliability and cost. For engineering leaders, the cloud-native agenda translates into concrete questions:

  • Which workloads genuinely benefit from containers or microservices?
  • Can teams deploy safely without depending on a central operations bottleneck?
  • Are logs, metrics and traces usable during an incident?
  • How are cloud costs measured per product, team or customer?
  • Are pipelines, dependencies and images protected against supply-chain risks?
  • Does the organisation have the skills to operate distributed systems around the clock?

The strategic lesson is not that every Java monolith should be decomposed. Modernisation should follow business constraints, operational evidence and team capacity. Broader regional cloud and integration agendas are tracked in Onyx’s overview of global cloud and IT integration conferences.

AI engineering moves into Java architecture

AI is shifting from experimentation into application architecture. The harder problem for established software teams is integrating models, agents and data services into reliable products, not calling a model API from a prototype.

The programme includes “Breaking Down AI Silos: Building Interoperable Multi-Agent Systems with Google’s A2A Protocol and Java SDK,” a session whose description centres on agents, enterprise interoperability and a Java SDK. That framing points away from isolated AI demonstrations and toward systems in which multiple agents or services exchange tasks and capabilities.

For Java teams, AI engineering adds requirements that traditional application development did not carry:

  • Secure access to models and enterprise data.
  • Retrieval pipelines with traceable sources.
  • Evaluation sets covering accuracy, latency, safety and cost.
  • Monitoring for model failures and degraded responses.
  • Human approval for high-impact decisions.
  • Clear controls over personal, confidential and regulated data.
  • Fallback behaviour when external model services are unavailable.
  • Versioning for prompts, models, tools and knowledge bases.

A2A interoperability is particularly relevant to enterprise developers. If agent systems become compositions of specialised services, shared protocols may reduce vendor lock-in and let Java applications take part in wider AI workflows. Protocol adoption, however, is not proof of production maturity. Teams will need to test authentication, authorisation, observability, failure handling and data governance before deploying agent-based systems in sensitive Moroccan sectors such as banking, telecoms, public services and commerce. Onyx has published practical guidance on how to choose the right AI model for Moroccan startups.

The programme also lists “Quantum-Safe Java Without the Hype: What Developers Need to Know,” showing that the agenda extends past immediate AI enthusiasm into long-term cryptographic resilience.

A two-day modernisation agenda for Moroccan teams

Devoxx Morocco 2026 is most useful when treated as a focused modernisation agenda rather than a catalogue of tools.

For developers: strengthen Java fundamentals while building competence in container operations, cloud deployment, testing of distributed systems, observability and secure AI integration.

For engineering managers: define platform capabilities — automated delivery, reusable service templates, centralised telemetry, secrets management and reliability standards — before launching several modernisation projects at once.

For startup founders: resist copying enterprise architectures prematurely. A modular monolith with automated deployment and strong monitoring can be a better fit than a sprawling microservices estate. Onyx’s analysis of Morocco’s three-city innovation corridor is useful context for where engineering talent and demand are concentrating.

For investors and business leaders: assess engineering maturity through deployment frequency, recovery time, service reliability, cloud-cost visibility, security controls and the speed at which prototypes become maintainable products.

For universities and training providers: connect Java education with cloud operations, data engineering, cybersecurity, AI evaluation and production software practice. Security capability deserves particular attention, as Onyx’s guide to Morocco’s cybersecurity challenges makes clear.