Metafive.ai FR Book a call

Back to home

Training 2026

The topics IT teams need to master this year: AI moving into production, regulation coming into application, and costs that need to be controlled. Each course is built on your own services and ends with deliverables you can use the next day.

In-house
6 to 12 participants from the same organisation, working on your real cases.
On site or remote
On site in the Paris region, or remote in half-day sessions.
Three languages
In French, English or Arabic; materials in French or English.
Tailored
Programme adjusted after a scoping interview; courses can be combined into tracks.

Assessment

Placement questionnaire before the course, knowledge assessment at the end, certificate of attendance. Workshop deliverables are reviewed by the trainer.

These courses do not prepare for official certification exams and are not legal advice: they focus on putting things into practice. Regulatory content is updated for every session.

Agentic AI: governance, security and guardrails

Putting AI agents into production in IT without losing control of what they do.

Why in 2026AI agents are leaving the pilot stage: they read data, call tools and act. The question is no longer "does it work?" but "who controls it, who is accountable, and how do we prove it".
Duration
2 days
Audience
CIOs, operations and architecture leaders, CISOs, platform teams.
Prerequisites
No technical prerequisites for the first day.
Frameworks
  • EU AI Act
  • ISO/IEC 42001
  • OWASP Top 10 for LLM Applications
  • agent-constitution (open source)

Objectives

  • Tell assistants, copilots and autonomous agents apart, and choose the right level of autonomy per use case.
  • Map the risks specific to agents: prompt injection, data leakage, unintended actions, costs.
  • Design guardrails: scope of action, identities and permissions, human sign-off, logging.
  • Measure the value and reliability of an agent in production.

Programme

Day 1 · Understand and frame

  • Use cases in IT: monitoring, incidents, compliance, reporting, documentation, code
  • Anatomy of an agent: model, tools, memory, orchestration
  • Risks and threats: prompt injection, exfiltration, model supply chain
  • Agent charter: what they may do alone, what requires a human

Day 2 · Go to production

  • Identities, secrets and least privilege for agents
  • Calculations in code, decisions with people: where determinism belongs
  • Agent observability: traces, costs, error rates, drift
  • Demonstration: the service level chain automated end to end

Hands-on work

  • Mapping your team's automatable tasks and the target level of autonomy
  • Writing the charter of an agent for one of your processes
  • Risk analysis of an existing or planned agent

What you take away

  • AI agent usage charter
  • Risk analysis grid
  • Automation roadmap

Back to the catalogue

The AI Act after the Digital Omnibus, and ISO/IEC 42001

Knowing what already applies, what was postponed, and building an auditable AI governance now.

Why in 2026The Digital Omnibus on AI (Regulation (EU) 2026/1744) postponed the high-risk regime to December 2027 and August 2028. Prohibited practices and the general-purpose AI rules already apply, and new transparency obligations arrive on 2 December 2026.
Duration
1 day
Audience
CIOs, compliance and legal leads, AI product managers, CISOs.
Prerequisites
None.
Frameworks
  • AI Act (Regulation (EU) 2024/1689)
  • Digital Omnibus on AI (Regulation (EU) 2026/1744)
  • ISO/IEC 42001
  • GDPR

Objectives

  • Classify your AI use cases against the AI Act risk categories.
  • Identify your role (provider, deployer…) and the obligations that follow.
  • Establish the actual timeline of obligations after the Omnibus.
  • Structure an AI management system based on ISO/IEC 42001.

Programme

Morning · The framework

  • Logic of the AI Act: prohibited practices, high risk, transparency, general-purpose AI
  • What the Omnibus changed: timeline, simplifications, interplay with GDPR
  • Roles and obligations: provider, deployer, importer, distributor

Afternoon · Governance

  • Inventory and classification of AI systems
  • ISO/IEC 42001: policy, roles, risk assessment, improvement
  • Documentation, logging and human oversight: the evidence to produce
  • 18-month action plan

Hands-on work

  • Inventory and classification of your organisation's AI use cases

What you take away

  • Register of AI systems
  • Timeline of obligations
  • Governance action plan

Back to the catalogue

Resilience and cyber regulation: DORA, NIS2, CRA

Linking the new obligations to architecture and operations, so you hold up when a link fails and can prove it.

Why in 2026DORA has applied since January 2025. The Cyber Resilience Act reporting obligations have applied since 11 September 2026. In France, the NIS2 transposition through the loi Résilience is still pending, but ANSSI urges organisations to prepare now.
Duration
3 days
Audience
CISOs and risk teams, business continuity, operations and architecture leads.
Prerequisites
Knowledge of your IT organisation and main suppliers.
Frameworks
  • DORA (Regulation (EU) 2022/2554)
  • NIS2 (Directive (EU) 2022/2555)
  • Cyber Resilience Act (Regulation (EU) 2024/2847)
  • ISO 22301
  • ISO/IEC 27001:2022
  • ReCyF (ANSSI)

Objectives

  • Know which regulations apply to your organisation, and since when.
  • Set up the incident management and reporting required by DORA, NIS2 and the CRA.
  • Control ICT third-party risk: contracts, register, exit strategies.
  • Map the requirements to ISO 22301 and ISO 27001 so you run a single programme.

Programme

Day 1 · DORA

  • Scope and role of the supervisory authorities
  • ICT risk management: framework, mapping, critical or important functions
  • ICT-related incidents: classification, major incidents, reporting
  • Digital operational resilience testing, including threat-led penetration testing
  • Third parties: contractual clauses, register of information, exit strategies

Day 2 · NIS2 and the Cyber Resilience Act

  • NIS2: essential and important entities, risk management measures, management accountability
  • Status of the French transposition and ANSSI's Référentiel Cyber France (ReCyF)
  • CRA: products in scope, reporting of actively exploited vulnerabilities and severe incidents
  • One detection and reporting chain for DORA, NIS2 and the CRA

Day 3 · Continuity, security and alignment

  • Business impact analysis, RTO, RPO, BCP and DRP (ISO 22301)
  • ISMS and Annex A controls (ISO/IEC 27001:2022)
  • Link with service levels: SLAs, OLAs and supplier contracts
  • Cross-compliance matrix and audit preparation

Hands-on work

  • Qualifying your organisation against DORA, NIS2 and the CRA
  • Review of a supplier contract against DORA
  • Crisis exercise including regulatory reporting

What you take away

  • DORA / NIS2 / CRA / ISO mapping matrix
  • Incident reporting process
  • Supplier clause checklist

Back to the catalogue

Service levels for AI: SLOs for LLMs and agents

Applying to AI services the discipline that makes platforms reliable: measure, commit, steer.

Why in 2026AI services are entering contracts and critical processes. Their reliability is more than availability: latency, answer quality, cost per request and dependency on model providers must also be measured and committed.
Duration
2 days
Audience
SRE and platform teams, AI product owners, service managers, architects.
Prerequisites
Basic knowledge of SLIs and SLOs, or the "SRE & SLOs" course.
Frameworks
  • Google SRE
  • ITIL 4: service level management
  • DORA: third parties
  • EU AI Act

Objectives

  • Define the SLIs of an AI service: availability, latency, quality, safety, cost.
  • Set realistic SLOs when the output is not deterministic.
  • Bring model providers into the SLA, OLA and UC chain.
  • Steer by error budget and by cost.

Programme

Day 1 · Measure

  • What changes with AI: non-determinism, model dependency, variable cost
  • Quality SLIs: automated evaluations, human sampling, refusal and hallucination rates
  • Perceived latency: time to first token, total time, queues
  • Cost per request and per useful result

Day 2 · Commit and steer

  • Composite SLOs and error budgets for AI
  • Contracts with model providers: what their SLAs actually cover
  • Fallback and redundancy: backup model, cache, degraded mode
  • Service review and dashboard for an AI service

Hands-on work

  • SLIs and SLOs for one of your AI services
  • Composite availability calculation including a model provider

What you take away

  • SLO sheet for an AI service
  • Quality evaluation grid
  • Template clauses for model providers

Back to the catalogue

Cloud and AI FinOps

Making cloud, GPU and inference costs visible and arbitrable before they drift.

Why in 2026AI spending (GPUs, tokens, inference) adds to the cloud bill and varies with usage. FinOps now extends to AI: unit cost, quotas and trade-offs must be set from the first day in production.
Duration
1 day
Audience
Infrastructure managers, architects, IT controllers, product owners.
Prerequisites
Use of at least one public or private cloud.
Frameworks
  • FinOps Framework (FinOps Foundation)
  • FinOps for AI

Objectives

  • Set up cost allocation: tagging, showback, chargeback.
  • Calculate a unit cost per service, per customer or per AI request.
  • Identify the savings levers for cloud and AI.
  • Arbitrate between cost, performance, quality and availability.

Programme

Morning · See

  • FinOps principles and roles
  • Cost allocation and tagging strategy
  • AI costs: training, inference, tokens, reserved or on-demand GPUs

Afternoon · Act

  • Levers: rightsizing, usage commitments, caching, model choice, quotas
  • The cost of availability: what one more nine costs
  • Governance, budgets and alerts, including for AI agents

Hands-on work

  • Analysis of a real cloud bill and a prioritised savings plan

What you take away

  • Tagging policy
  • Unit cost model for an AI service
  • Costed optimisation plan

Back to the catalogue

Sovereign and hybrid cloud architecture

Deciding where each workload belongs between public cloud, trusted cloud and private infrastructure, while keeping reversibility.

Why in 2026Data sovereignty, dependency on a few providers and regulators' focus on concentration risk are driving hybrid, reversible and documented architectures.
Duration
3 days
Audience
Architects, infrastructure and operations managers, tech leads.
Prerequisites
Infrastructure basics (network, storage, virtualisation).
Frameworks
  • SecNumCloud (ANSSI)
  • ISO/IEC 27017 and 27018
  • AWS and Azure Well-Architected
  • DORA: concentration risk

Objectives

  • Choose a service and deployment model using explicit criteria, sovereignty included.
  • Design a landing zone: accounts, network, identity, security, observability.
  • Calculate the availability of an architecture and match it to the target commitments.
  • Build a reversible, costed migration roadmap.

Programme

Day 1 · Scope and choose

  • Service models and shared responsibility
  • Placement criteria: criticality, data, latency, cost, reversibility, sovereignty
  • Trusted cloud and qualifications: what they guarantee and what they do not
  • Landing zones: account structure, network, identity, guardrails

Day 2 · Resilience and scalability

  • Zones and regions, active-active and active-passive redundancy
  • Composite availability: links in series and in parallel
  • Capacity tiers, load testing, scaling
  • Backup, replication, RTO and RPO per service

Day 3 · Migrate and stay reversible

  • Migration strategies and wave planning
  • Reversibility: formats, contracts, exit plans
  • Infrastructure as code and environment automation
  • Architecture governance: principles, decision records, reviews

Hands-on work

  • Placement matrix of your applications
  • Availability calculation for your current and target architecture
  • Outline of a migration roadmap

What you take away

  • Placement decision grid
  • Architecture document template
  • Composite availability calculator

Back to the catalogue

Platform Engineering and AI-assisted delivery

Delivering more often and more safely with an internal platform run as a product, and governed coding assistants.

Why in 2026Coding assistants and agents speed up writing software; without a platform, guardrails and measurement, they also speed up debt and incidents.
Duration
2 days
Audience
Platform and DevOps teams, developers, engineering managers.
Prerequisites
CI/CD and container basics.
Frameworks
  • DORA DevOps metrics
  • Team Topologies
  • CNCF Platforms White Paper

Objectives

  • Measure delivery performance with the DORA DevOps metrics.
  • Design a self-service internal platform and its golden paths.
  • Govern coding assistants and agents: rules, reviews, tests, security.
  • Organise teams around flow.

Programme

Day 1 · Deliver

  • Deployment frequency, lead time for changes, change failure rate, time to restore
  • CI/CD pipeline, progressive delivery, infrastructure and policy as code
  • Coding assistants and agents: real gains, risks, usage rules

Day 2 · Platform

  • Platform as a product: users, roadmap, adoption
  • Developer portal, service catalogue, golden paths
  • Team topologies and cognitive load
  • Platform reliability: internal SLOs

Hands-on work

  • Measuring your DORA DevOps metrics
  • Designing a golden path that includes a coding assistant

What you take away

  • DORA DevOps dashboard
  • Coding assistant usage rules
  • Platform roadmap

Back to the catalogue

SRE & SLOs

Measuring reliability from the user's point of view, setting objectives and steering trade-offs with the error budget.

Why in 2026The foundation of the other courses: without SLIs and SLOs, neither regulation, nor AI, nor contracts can be steered by measurement.
Duration
2 days
Audience
Run and SRE teams, product owners, operations managers.
Prerequisites
Hands-on use of a monitoring tool (Prometheus, Dynatrace, Zabbix, Centreon or similar).
Frameworks
  • Google SRE
  • OpenSLO
  • ITIL 4

Objectives

  • Choose SLIs that reflect the user experience.
  • Set SLOs and an error budget policy agreed by product and operations.
  • Implement alerts based on error budget burn rate.
  • Run blameless post-mortems.

Programme

Day 1 · Measure

  • Perceived reliability versus component reliability
  • Types of SLIs and calculation methods
  • Setting an SLO: history, expectations, cost of each extra nine
  • Error budget and its policy

Day 2 · Steer

  • Multi-window burn-rate alerting
  • Major incident management
  • Post-mortems and corrective actions
  • Measuring and reducing toil

Hands-on work

  • SLIs and SLOs for two of your services
  • Burn-rate alerts in your monitoring tool
  • Post-mortem of a real incident

What you take away

  • SLO sheets for your services
  • Error budget policy
  • Post-mortem template

Back to the catalogue

Service Level Management: SLAs, OLAs and UCs

Writing achievable service commitments, from the customer contract down to internal teams and suppliers.

Why in 2026DORA and NIS2 require control over suppliers; customers require quantified commitments. The SLA, OLA, UC chain is where both meet.
Duration
2 days
Audience
Service managers, IT contract and procurement managers, architects, operations managers.
Prerequisites
None; basic ITIL knowledge helps.
Frameworks
  • ITIL 4: service level management
  • ISO/IEC 20000-1
  • DORA: third parties

Objectives

  • Build the SLI → SLO → OLA → UC → SLA chain and explain every calculation in it.
  • Write a complete SLA: scope, service hours, measurements, exclusions, credits and penalties.
  • Align internal teams' OLAs and suppliers' UCs with the SLA.
  • Run data-driven service reviews.

Programme

Day 1 · Design the chain

  • Service catalogue and commitment tiers
  • Anatomy of an SLA, an OLA and an underpinning contract
  • Calculations: error budget, SLO margin, links in series and in parallel
  • Market SLA benchmark: cloud providers, banking sector

Day 2 · Formalise and govern

  • SLA / OLA / UC traceability and RACI matrices
  • Service credits and penalties
  • Auditable calculation methods, ITIL 4 and ISO/IEC 20000-1
  • Monthly service review and continuous improvement

Hands-on work

  • Breaking a real SLA down into OLAs and UCs
  • Writing an SLA sheet and its OLA sheets
  • Simulated service review with credits

What you take away

  • SLA, OLA and UC sheet templates
  • Traceability matrix
  • Commitment chain calculator

Back to the catalogue

Tracks

Courses combine according to your main challenge.

Let's talk about your platform

A first 30-minute conversation to understand your context: architecture, compliance stakes, commitments, deadlines.

Based in Paris – La Défense. On-site, hybrid or remote engagements.