Entry point

Start Here

Architect, CTO and technical advisor on cloud, Kubernetes, Platform Engineering, observability, DevSecOps and complex systems architecture.

If your estate is hard to read, risky to change, or buried under tools, here is how I work, what I take on, and the proof I publish.

Problems I address

  • Systems that have become hard to understand as a whole.
  • Invisible dependencies that make every change risky.
  • Risks poorly prioritized, addressed too late or in the wrong place.
  • Platforms that accumulate tools without improving delivery.
  • Observability that cannot support decisions: many signals, little action.
  • Architectures that slow change instead of making it safer.

Method

A simple, iterative path. A living system does not become perfect on the first deployment.

  1. Understand the real system
  2. Map the dependencies
  3. Prioritize the risks
  4. Define a trajectory
  5. Advise or build
  6. Observe, learn and iterate

Areas of intervention

  • Cloud architecture
  • Kubernetes
  • Internal platforms
  • Observability and reliability
  • DevSecOps
  • Software supply chain
  • Dependency mapping
  • Technical governance

Public proof: projects

Technical and open-source projects published on this site. Not a commercial catalog.

External Metrics Exporter

Problem: Teams deploy on Kubernetes without reliable visibility on external dependencies or comparable signals across vendors.

Role: Author and maintainer

Approach: Expose actionable signals without imposing a new data model

View project →

Public proof: writing

Doctrine and guides that show the reasoning before going further.

Doctrine

De la métrique au runbook : construire des alertes réellement opérables

Une alerte est un contrat d’exploitation testable : six maillons relient le phénomène réel au runbook, et versionner du YAML n’en prouve aucun.

Read →

Technical guide

Azure Devops & MegaLinter Auto PR

Autofix your code using Azure DevOps & MegaLinter !

Read →

Technical guide

Documentation as Code

Read →

Reading paths

Ways in. Each path only lists content that already exists.

Platform and operations

For teams building and operating cloud native platforms.

  • Kubernetes
  • observability
  • GitOps
  • CI/CD
  • operations
  1. External Metrics ExporterRead

    Projet open source qui découvre les dépendances externes des workloads Kubernetes et expose un contrat Prometheus neutre vis-à-vis des fournisseurs.

  2. De la métrique au runbook : construire des alertes réellement opérablesRead

    Une alerte est un contrat d’exploitation testable : six maillons relient le phénomène réel au runbook, et versionner du YAML n’en prouve aucun.

  3. Les coûts cachés des images de conteneursOpen

    White paper Omnivya : impact CI/CD, registries, Kubernetes, sécurité et carbone des images trop lourdes.

  4. Azure Devops & MegaLinter Auto PRRead

    Autofix your code using Azure DevOps & MegaLinter !

  5. Documentation as CodeRead

Systems and risk

For regaining control over dependencies, decisions and cost of change.

  • risk
  • dependencies
  • architecture
  • supply chain
  • governance
  1. Azure Devops & MegaLinter Auto PRRead

    Autofix your code using Azure DevOps & MegaLinter !

  2. Documentation as CodeRead

  3. La face cachée de l’Infrastructure as CodeOpen

    White paper Omnivya : gouverner l’IaC pour éviter le chaos, avec sept piliers et retours d’incidents.

Omnivya

With Taous, we co-found Omnivya: she leads Omnivya and Omnivya Expert; I am CTO. Missions that need structured delivery capacity are carried by Omnivya Expert.

Open Omnivya Expert →

Omnivya white papers

White papers published with Omnivya on cloud, containers and IaC. Read on omnivya.fr.

The hidden costs of container images

How an extra 100 MB hits CI/CD, registries, Kubernetes clusters, security and carbon footprint, and how to slim images.

Read on Omnivya →

The hidden side of Infrastructure as Code

Govern automation to avoid chaos: incident lessons and seven pillars of mastered IaC.

Read on Omnivya →

All Omnivya white papers →

Where to continue

Thinking

Doctrine, field notes and architecture decisions.

Read →

Work

Intervention modes: Diagnose, Decide, Build.

View →

Projects

Technical and open-source proof.

View →

About

Background and working principles.

Read →

Contact

Talk through a context before engaging.

Write →
Discuss a complex systemSend an email