Platform Reliability Architect
Five constants from the field: understand systems, reduce complexity, secure decisions, build what is missing, confront ideas with reality.
I design, secure and make complex digital systems governable: cloud platforms, Kubernetes, DevSecOps, observability and decision architecture.
I am a Platform Reliability Architect. Omnivya carries consulting and delivery when execution is required. This site documents my principles, public proof and reasoning, not a commercial catalog.
Taous is co-founder of Omnivya, IT Challenge / Omnivya Expert, My Dare and Sanad, in France and Algeria.
This site documents my reasoning. Execution structures and the field are carried jointly.
The career started in 2006. The path runs from operational fieldwork, including ADSL support, to architecture and technical leadership. Titles stacked; more importantly, scope widened: from component to system, from incident to irreversible decision.
Cloud, infrastructure, platform, DevSecOps and architecture stacked on the same question: how does a system stay readable, operable and governable as complexity grows?
Work spans France and Algeria. That is not geographic storytelling: it forces design for real regulatory, organizational and territorial constraints, rather than for an ideal market.
Progressive markers, readable without advanced styling. This is not an exhaustive CV.
Entry through operations and support, including ADSL fieldwork, in direct contact with failures and users.
Expansion into administration, infrastructure and environment preparation, from component to system scope.
Cloud architecture, infrastructure as code, DevSecOps and platform: broader decisions, longer-lived consequences.
Founding of Omnivya with Taous: execution structure to carry consulting and delivery without diluting the decision frame.
Omnivya; My Dare and Sanad in Algeria (IT Challenge / Omnivya Expert); open source.
Twenty years in the field shifted the center of gravity: fewer tools to collect, more decisions to secure. Technique remains necessary; it is no longer enough as the only answer.
The systems I work with rarely lack tools. They lack a shared map, decision criteria and the ability to act without growing invisible debt.
Designing, today, means first making the system understandable, and only then automating or industrializing further.
Omnivya is the execution group; Omnivya Expert is its services arm. Published reasoning (this site) and structured delivery stay deliberately separate: one clarifies; the other carries into missions.
Without an execution structure, ideas stay slides. Without clear principles, execution becomes a tool catalog. Omnivya and Omnivya Expert connect both for contexts of high technical and organizational complexity.
On the Algeria side: My Dare (coworking in Algiers), then Sanad (DZ-market tool via Omnivya Expert / IT Challenge).
Omnivya Expert anchors local build. My Dare anchors the field. Sanad stays a DZ-only tool — not the group’s flagship.
Curated public repositories, grouped by intent — not an exhaustive GitHub listing. Strategic descriptions live on this site; metadata may be enriched at build time.
Cloud-native proof: operators, observability and platform labs.
Cloud cost control and price readability.
Security, CI/CD and software supply-chain tooling.
Adjacent tools — useful, but outside the core platform pitch.
History and build proof, not active products.
To discuss a complex system, an intervention or a platform context: a qualified email is enough. Describe the context, constraints and the decision to secure.