Selective advisory · Q3–Q4 2026 Île-de-France · --:-- local

SA / 01 Salah Awad · Enterprise & AI Architect

Salah Awad — AI systems built to hold under pressure.

I design and build the systems behind consequential AI — agentic where the path is unknown, deterministic where accuracy matters — for environments that must survive audits, outages and security reviews.

6 years as CTO 19+ years building 3 working languages
Agentic systemsTarget-state architectureSovereign AIMCP securityCloud transformationApplied AI

Evidence

Built, not advised on.

Every figure below is something I designed and shipped, not a team I was adjacent to. Most of them count systems and design decisions rather than servers — that is deliberate. Client and product names are withheld; the engineering is the point.

34AI & agentic capabilities shipped

Inference runtimes, orchestration loops, tool surfaces, retrieval stacks, evaluation harnesses and speech pipelines — each with a named production implementation.

2Production MCP servers built

Enterprise APIs exposed to agents as curated, per-domain tool contracts over stdio and streamable HTTP, behind federated identity and a manifest-gated escape hatch.

7Model providers behind one abstraction

Self-hosted and hosted runtimes selected by configuration, so changing model vendor is an environment variable rather than a rewrite.

11Retrieval & data stores in production

Lexical, dense-vector, graph, relational and columnar stores — combined into hybrid retrieval measured by a dedicated evaluation package.

33Architecture patterns evidenced

Strangler extraction, shared identity, two multi-tenancy models, versioned APIs, staged pipelines, credential-custody BFFs and offline deployment modes.

10+Languages in one AI pipeline

Automated translation, speech synthesis and video generation, hand-built and tuned for multilingual industrial training.

180+Repositories under active index

A working code fleet spanning inference services, agent orchestrators, retrieval infrastructure, platform charts and mobile clients.

6Consecutive years as CTO

From 2019 to 2025, with full ownership of the architecture and the organisation throughout.

1,500+Accounts under one target architecture

Proof the designs hold at scale: a single inventory, incident and governance model spanning a four-figure account estate, 2,500+ machines, 600+ managed databases and 600+ container clusters.

Selected systems

Architecture measured in constraints survived.

Four systems, four very different boundaries. The common thread is architecture that turns high-stakes constraints into something teams can operate, inspect and trust.

SYSTEM / 01 Operating at scale

A single operations plane for a four-figure cloud estate.

Canonical inventory, incident correlation and governance across 1,500+ accounts, 2,500+ machines, 600+ RDS databases and 600+ ECS and EKS clusters — with bounded AI remediation wired into the operating model.

Constraint
No single team owns the whole estate
Architecture
Shared inventory + incident spine + agentic operations
Outcome
One coherent control plane across cloud, network and security
1,500+cloud accounts under one target architecture
SYSTEM / 02 Sovereign

Industrial AI with no route to the public internet.

A portable inference and media pipeline spanning cloud, on-premise and fully air-gapped sites — including translation, speech and video generation in 10+ languages.

Air-gapped deployment50% faster training
SYSTEM / 03 Trust bounded

Enterprise tools exposed to agents — without exposing the enterprise.

Two production MCP servers with federated identity, curated domain tools, manifest-gated escape hatches and an immutable trail of every action.

Model Context Protocol2 production servers
SYSTEM / 04 Real time

Voice intelligence tuned for the language people actually speak.

Real-time Levantine Arabic transcription with diarization, hallucination suppression, domain correction, sentiment, risk and quality scoring — fully local.

Local bilingual inferenceAudio stays inside

The Practice

Agentic where it earns its keep.
Deterministic everywhere else.

The most expensive mistake in enterprise AI right now is reaching for an agent when a pipeline would have been cheaper, faster and certifiable. I build both, and the judgement of which to use is most of the architectural value.

Track A — Agentic AI

When the path cannot be enumerated in advance.

Agents are engineered software, not prompt chains. That means an explicit orchestration loop, a designated termination tool, an iteration ceiling, typed tool contracts, bounded result sizes and a persisted trail of every action taken — so the system can be audited after the fact rather than trusted in the moment.

01 Tool surfaces & Trust Boundaries
Model Context Protocol (MCP) servers exposing enterprise APIs as curated, per-domain tools over stdio and streamable HTTP, behind federated identity with a manifest-gated escape hatch.
02 Orchestration & State
Supervisor-pattern multi-agent systems with schema-typed structured output, critic and judge loops, and slot-filling conversational state machines with typed, localised schemas.
03 Neuro-Symbolic Guardrails
The model proposes intent, deterministic code resolves every value against an immutable fact store, and an exact verifier rejects invalid output before it executes.
04 Vendor & Model Portability
Provider-agnostic abstraction across self-hosted and hosted runtimes (OpenAI, Anthropic, Bedrock, vLLM), so switching model providers is a configuration change rather than a rewrite.
Track B — Classical & Applied AI

When the task is bounded and accuracy is measurable.

Most of the value being shipped in production today is not agentic at all. It is speech, language, retrieval and scoring — tasks with ground truth, evaluation harnesses and a number you can put in front of an auditor. This is the unglamorous half that actually survives procurement.

01 Speech & Conversation Intelligence
Real-time transcription with speaker diarization, voice-activity segmentation, domain-dictionary correction, hallucination suppression, and sentiment, risk, empathy and quality scoring — including dialect-level work in Levantine Arabic.
02 Hybrid Retrieval That Is Measured
Lexical BM25 fused with dense vectors by Reciprocal Rank Fusion (RRF), tunable chunking, cross-encoder reranking, and dedicated evaluation harnesses so retrieval quality is a verified metric.
03 Multi-Modal Language Pipelines
Neural machine translation, text-to-speech, and programmatic video generation composed into staged pipelines with human-in-the-loop gates designed in as a stage, not bolted on.
04 Sovereign & Air-Gapped Deployment
Quantised open-weight models on local inference runtimes, GPU-semaphore concurrency control, CPU degradation paths, and air-gapped packaging for estates with zero egress.

Interactive Architecture Tool

AI Architecture Suitability Matrix

Toggle your enterprise constraints below to calculate whether your workload requires a Bounded Pipeline, a Supervisor Multi-Agent System, or a Neuro-Symbolic Guardrail.

1. Execution Path & Step Predictability
2. Tool Blast Radius & Side Effects
3. Ground Truth & Evaluation
4. Latency Budget & SLA
RECOMMENDED ARCHITECTURE

Bounded Deterministic Pipeline

Your constraints indicate a deterministic pipeline with measurable ground truth. Do not use an autonomous agent loop here: a structured pipeline with explicit evaluation harnesses will be 10x faster, cheaper, and fully auditable by compliance.

Mandatory Architectural Control:

Implement Reciprocal Rank Fusion (RRF) with BM25 + dense vectors and automated regression benchmarks in CI.

Innovations

The practice, with the measurements behind it.

Recent systems I built, led or designed, each chosen because it tests a claim made on this page against a measurement. Names are withheld; the measurements are not.

Incident intelligenceBuilt

Incidents investigated against the estate’s own history.

For a global aerospace, defence and space group, I built a unified cloud operations portal: 650+ commits and roughly 240,000 lines in eight months. Its AI layer investigates incidents with a frontier model served through Amazon Bedrock, grounds each investigation in hybrid keyword-and-vector search over past incidents, groups similar incidents semantically, and gives the assistant tool access to the ITSM, observability, network, identity and cloud systems, while user actions are kept in an append-only audit trail.

650+ commits in 8 months
Sovereign inferenceBuilt

An 80B-class model at 256K context on two consumer GPUs.

I run a private AI fabric of two consumer GPUs, 24 GB and 32 GB, joined by a direct 2.5 GbE link. A 3-bit quantised 80B-class coding model is split layer by layer across both cards at its full 256K context; it passed a needle test at close to 250K tokens and decoded at a median above 90 tokens per second across 230 real requests. The same pool sends image, video and 3D render jobs to whichever host is idle, and no inference is paid for.

256K context, no paid inference
Knowledge captureBuilt · then led

Expert know-how captured without letting the model invent it.

I built an AI interviewer, and later led the team extending it, that turns a shop-floor expert’s spoken know-how into a structured training standard. Its extraction step is instructed to keep only what the expert stated, explicitly affirmed or explicitly asked the interviewer to suggest, and a 17-rule deterministic validator, not the model, decides whether the result is good enough. Optional retrieval over public occupational-safety and skills sources may steer the questions, but it reaches extraction only in a reference mode that forbids taking values from it, and the natural-language search the team added shows the model field names only, never customer data.

17-rule deterministic validator
Neuro-symbolic designBuilt

Layouts the model proposes and geometry decides.

I built a spatial layout engine in which a local model proposes the plan and a backtracking solver, with exact collision, clearance and reachability checks, places every object; a vision model may choose between layouts that already passed but can never overrule the verifier. On its own benchmark of 75 generated scenes, from sparse to dense, the solver placed every scene without collision or refusal. A sibling pipeline turns a 2D plan into a path-traced 3D scene; a diffusion pass then refines materials and light only in the late steps of denoising, so the geometry stays where the solver put it.

75/75 scenes, zero collisions
Calibrated decisionsBuilt

Probabilities, not prose, from local models.

I built a decision engine that asks a local model a lettered multiple-choice question and reads the probability of a single answer token. It calibrates that probability per model by temperature scaling, averages a reversed-order pass to cancel position bias, and scores itself on accuracy, Brier score and calibration error. On a labelled set of about 100 developer decisions it scores above 85% with a 7B model, at around 20 ms per question, and 99% with a 27B model. Because it is wire-compatible with a commercial decision API, that vendor’s SDK runs unchanged against local models.

~99% with a 27B model
Retrieval evaluationBuilt

Retrieval tuned against a gold set, not a demo.

I built a code-search server for agents that fuses BM25 and dense retrieval by reciprocal rank fusion and can rerank with a cross-encoder. It is measured against a 110-query gold set, nearly half mined from commit history, with labels anchored to files rather than chunks so it survives re-chunking and embedder swaps. The measurements showed the dense lane alone was far weaker than BM25, and the reranker lifted NDCG@10 by more than half, from 0.46 to 0.71. An earlier multi-agent orchestration layer was cut so the server could focus on retrieval.

NDCG@10 0.46 → 0.71
Decision methodologyDesigned

One grammar for people, continuous representations for engines.

I designed a decision methodology that describes every product, space, customer profile and bundle on the same six typed axes. People work with closed, human-readable vocabularies; engines work with continuous representations of the same axes (multimodal embeddings, perceptual colour vectors in CIE L*C*h° with covariance, material feature tensors and a hierarchical spatial scene graph), so fit and coherence are optimised rather than looked up. On top sit a mixed-integer assortment optimiser under grammar constraints, a 3D layout solver, active Bayesian preference elicitation, sequential testing and an information-theoretic positioning engine. Its reference outcomes: a fit score of 92/100, a coherence score of 88/100, every required slot filled, and an 18% higher margin than a manual pick.

Fit 92/100, +18% margin vs manual
Agent tool surfacesBuilt

A tool gateway that lets agents borrow a peer GPU, safely.

I built a Model Context Protocol gateway for each GPU host that gives coding agents eight typed tools and, deliberately, no shell. A node can borrow its peer’s capacity only through size-bounded, hash-verified snapshots run in a network-less sandbox. The model starts automatically only after a VRAM admission check that fails closed. With the serving engine’s prefix caching, time-to-first-token on a 5K-token context fell from 1.2 s to under 40 ms.

First token: 1.2 s → <40 ms
Grounded generationBuilt

Images built from the quote, not from a prompt.

For a vertical AI platform, I built image generation that conditions every scene on the product photos in the priced proposal, with a negative prompt derived per scene from the catalogue; in a small internal test (six renders of one scene), duplicate copies of quoted products disappeared, though it does not make the model count reliably. The production model was chosen by a vision model scoring per-product fidelity on a four-proposal comparison (5.2 against 2.0 and 0.1 out of 10), and product swaps are stitched back so that every pixel outside the edited region stays byte-identical.

Fidelity 5.2 vs 2.0 vs 0.1
Neuro-symbolic guardrailsBuilt

The model chooses; the catalogue owns every price.

For the same platform, I built proposal generation in which a single JSON-mode model call sits inside seven deterministic stages. Those stages discard any product not in the candidate set, overwrite every price and name from the catalogue, and repair budgets and overlap between tiers. The conversational brief that feeds it keeps a fact only if the customer’s own words support it. For made-to-order manufacturing, a pure rule engine decides fit, tolerances, pricing and approvals, and the model may only choose among options that already passed.

1 model call, 7 deterministic stages
GenAI operationsBuilt

Generative AI on self-hosted GPUs, run like a billable service.

I built the layer that lets open-weight language and diffusion models share self-hosted GPUs as a billable service. A coordinator drains the language model before diffusion claims the card; a durable queue with typed failure codes is built so that competing workers never run the same render and a render is billed at most once, only after delivery; and an ambiguous submission quarantines its GPU until the queue proves it absent. If the embedding model answering is not the one that built the index, search falls back to keywords rather than returning wrong neighbours. The cost attribution I led charges each call to the business action that triggered it.

Billed at most once, after delivery
Agent verificationBuilt

The model that produces the work never grades it.

I built a ticket-to-merge pipeline in which one vendor’s coding agent works on an isolated branch, a different vendor’s agent audits the diff against a schema, and only deterministic lint and test gates can merge. So far only its individual stages have been exercised, in dry-run mode: triage correctly declined a non-code ticket and the merge gate ran the affected test suite; no ticket has yet gone through coding and cross-vendor audit, and it is not trusted with production merges. The same principle runs a research tool in which two agent engines each try to refute what the other found. Organisations that cannot be shown to exist are dropped, real ones with stale details are corrected, and stale details proved far more common than fabrication.

Stages validated in dry run
Output assuranceBuilt

Generated speech, text and video, checked before anyone sees them.

I build objective gates for generated output instead of relying on spot checks. A tiered translation-quality estimator that can run air-gapped uses a local LLM judge, and that judge caught a terminology mistranslation every structural check had passed. A round trip transcribes synthesised narration back and ranks each line by word error rate; it exposed French voices dropping final consonants. For films, every frame is decoded and scanned, with hashed provenance, before delivery. The quality estimator is built and validated but not yet enabled in production.

Every frame decoded before delivery
Industrial engineering AIBuilt

From CAD drawings to data a workshop can use.

I built an on-premise pipeline, entered in a regional industrial AI challenge, that reads a CAD assembly and its drawings and produces standards-based calculations, Pareto design variants, corrected geometry and operator skills. Engineering rules and closed-form formulas produce the numbers, the models only read, classify and phrase, and every output cites its drawing page or standard.

Every number from a rule
Local-model analyticsBuilt

Small local models over large operational data.

I built an observability layer for a multi-tenant Kubernetes platform. It redacts tokens and personal data before anything is embedded, runs eleven statistical and vector analyzers, and lets a local model narrate root causes, while operator feedback mutes noisy signatures. For delivery data, I made a map-reduce over a backlog of 3,000+ tickets converge: capping items in code, rather than trusting the model’s grammar, raised compression to about 4× per round. Every ticket key the model returns is checked against the source.

~4× compression per round
AI-native engineeringPractice

Coding agents, governed like an engineering organisation.

I run coding agents as a governed process: a written spec and a test-first plan come before any code, agents work in parallel in isolated worktrees, and independent reviewers and a second model audit the result. So far that adds up to 120+ specs and 100+ plans across 25+ repositories. On a 200k+ line AI platform, architecture rules live in executable boundary and drift tests. Across a multi-repository production estate, agents may run read-only cluster and cloud commands freely, but every change to clusters, releases, cloud resources or remotes needs explicit approval, guided by a durable memory of verified root causes.

120+ specs across 25+ repositories

System Topologies

Interactive Architecture Studio.

Reference patterns from systems I have designed and built, reduced to their essentials. The code is illustrative, not a verbatim extract from a client codebase. Click on any node to inspect trust boundaries, contracts, and failure modes prevented.

REFERENCE TOPOLOGY

Agentic Multi-Agent & MCP Trust Boundary

Zero Trust · Defense-in-Depth
NODE TELEMETRY & SPEC

Model Context Protocol (MCP) Gateway

Curated tool surface exposing enterprise systems as typed, named per-domain JSON-RPC contracts over streamable transports, strictly decoupling raw execution rights from model access.

TRUST BOUNDARY ENFORCEMENT Tokens scoped to individual tools rather than user's blanket rights. Escape hatch gated by explicit manifest.
PRODUCTION FAILURE PREVENTED Prevents prompt-injection-driven SSRF and unauthorized write mutations across backend datastores.
tool_manifest.json SCHEMA / CONTRACT
// JSON-RPC Tool Contract
{
  "name": "query_inventory",
  "description": "Bounded query of cross-account asset metadata",
  "inputSchema": {
    "type": "object",
    "properties": {
      "account_id": { "type": "string", "pattern": "^[0-9]{12}$" },
      "resource_type": { "type": "string", "enum": ["ec2", "eks", "rds"] }
    },
    "required": ["account_id", "resource_type"]
  }
}

Capabilities

What I am hired to design & deliver.

Bridging executive strategy with production engineering. Each discipline below addresses a critical enterprise risk — de-risking AI adoption, modernising legacy estates, and ensuring compliance in high-stakes environments.

01

Agentic AI systems

Business Impact: Eliminates runaway compute costs and unpredictable drift with deterministic verification and audit-ready governance.

Agents built as engineered software rather than prompt chains: an explicit orchestration loop, a designated termination tool, iteration ceilings, typed tool contracts, bounded results, and an audit trail that makes an agent’s behaviour reconstructable months later.

  • MCP tool surfaces
  • Multi-agent orchestration
  • Tool-contract design
  • Termination & guardrails
  • LLM-as-judge loops

Measured in: shell-less MCP gateway, governed coding agents, cross-vendor verification

Read: agentic AI decision boundaries
02

Applied & classical AI

Business Impact: Deploys high-accuracy speech, translation and hybrid search with measurable ground truth that passes enterprise procurement.

The half that survives procurement: speech recognition, speaker diarization, conversation analytics, neural translation, speech synthesis, hybrid retrieval and rules-based scoring — bounded tasks with ground truth, evaluation harnesses and accuracy you can put in front of an auditor.

  • ASR & diarization
  • Conversation intelligence
  • Hybrid RAG
  • NMT & TTS
  • Evaluation harnesses

Measured in: gold-set retrieval, generated-output QA, expert interviewer

03

Trustworthy & sovereign AI

Business Impact: Air-gapped and on-premise deployments that safeguard confidential IP and guarantee strict ISO & GDPR compliance.

Where the trust boundary sits matters more than which model you picked. The model proposes intent, deterministic code resolves every value against a fact store, an exact verifier rejects invalid output — and the whole stack runs on-premise or fully air-gapped when data cannot leave the perimeter.

  • Neuro-symbolic design
  • On-premise inference
  • Air-gapped deployment
  • Human-in-the-loop gates
  • Model portability

Measured in: private GPU fabric, neuro-symbolic layouts, calibrated local models

Read: sovereign and air-gapped AI
04

Target-state & enterprise architecture

Business Impact: De-risks multi-year platform investments with defensible, cost-scored option analysis and clear board roadmaps.

Current-state assessment, genuinely competing architectural options rather than one preferred answer dressed up with alternatives, and an explicit scoring framework — security, availability, ecosystem interoperability, usability, scalability, total cost of ownership — then a defensible decision and the roadmap to execute it.

  • Future-state assessment
  • Option analysis
  • Decision frameworks
  • Technology roadmaps
  • Reference architecture

Measured in: gold-set retrieval, fidelity-scored model selection

05

Solution design & integration

Business Impact: Replaces fragile spaghetti integrations with governed service contracts, modern API gateways, and scalable message buses.

The architecture between the systems: a centralised service bus weighed against a decentralised federated model where each department keeps its own infrastructure behind standardised contracts; document, case and process engines; message routing, transformation and validation; and the registry and audit spine that makes any of it governable.

  • ESB vs. federated mesh
  • API gateways
  • BPM & case management
  • Content & records platforms
  • Service contracts

Measured in: incident intelligence, GenAI service operations, shell-less MCP gateway

06

Secure multi-layer architecture

Business Impact: Defense-in-depth security preventing data leakage, prompt-injection exploits, and unauthorized API mutations.

Defense-in-depth designed on the assumption that each control eventually fails: federated identity, tenant isolation, encrypted credential custody, constrained agent tool surfaces, supply-chain gates in CI, network policy, and immutable audit across every layer.

  • OIDC / SAML / LDAP
  • Tenant isolation
  • Agent tool-surface security
  • SBOM & supply chain
  • Audit & compliance

Measured in: shell-less MCP gateway, incident intelligence, governed coding agents

Read: MCP security architecture
07

Platform & operations architecture

Business Impact: Reduces infrastructure TCO (FinOps) and slashes MTTR by automating incident triage across massive cloud estates.

Designing the plane a large estate is actually run from — canonical inventory, an incident model that survives ownership boundaries, landing-zone governance — then wiring foundation models and agentic DevOps tooling into it so incidents are triaged, explained and remediated rather than merely alerted on.

  • AIOps & auto-remediation
  • Multi-account governance
  • Migration factory
  • FinOps & ROI
  • Estate observability

Measured in: incident intelligence, local-model ops analytics, GenAI service operations

08

Fractional CTO & delivery

Business Impact: Accelerated technical velocity, unbiased vendor selection, and audit-proof due diligence for boards and founders.

Technical due diligence, engineering organisation design, roadmap and backlog governance, vendor and partner strategy, and the unglamorous discipline of getting a distributed team to ship on a date.

  • Due diligence
  • Org design
  • Roadmap governance
  • Vendor strategy
  • Interim leadership

Measured in: governed coding agents, incident intelligence

Record

Where the experience was earned.

Organisations are described, not named — clients, employers, products and programmes alike. The capability transfers; the confidentiality holds.

  1. 2025 — PRESENT ACTIVE ENGAGEMENT

    Global aerospace, defence & space group — 83,000 people

    Program Director, Cloud Transformation · Operations Lead

    Architecting and leading a group-wide cloud transformation: the target-state design, the migration-factory governance framework, the evolution of the operating model toward DevOps, SRE and product-centric delivery, and financial sustainability through FinOps and ROI tracking rather than assumption.

    I designed the group's operations platform end to end — a single inventory, incident and governance model that holds across a four-figure account estate and its network and security layers — and then wired managed foundation models and agentic DevOps tooling into it, so incidents are correlated, triaged, explained and automatically remediated rather than merely alerted on. The interesting problem was never the machine count; it was designing an architecture that stays coherent when no single team owns the whole estate.

    83,000 Group Workforce Target-State Architecture Applied AI in Operations AIOps Auto-Remediation
  2. 2023 — 2025

    Industrial AI venture — corporate-incubated

    Co-Founder · Chief Technology Officer & CIO

    Designed and built an AI-powered industrial training platform from the ground up: a secure, modular ecosystem deployed across Azure, AWS, GCP and on-premise air-gapped environments, multi-tenant SaaS alongside private deployments for sensitive organisations, aligned to ISO and GDPR requirements. Personally coded much of the AI pipeline — automated translation, speech synthesis and video generation across more than ten languages — while acting as CIO over IT governance, cybersecurity and client conformity assessment. Extended reality and digital-twin methods cut training time by half.

    10+ Language AI Pipeline Air-Gapped Sovereign AI Digital Twins & XR 50% Training Time Reduction
  3. 2020 — 2023

    EMEA enterprise software vendor

    Chief Technology Officer

    Owned the technology strategy and stack across regional offices of an EMEA digital-transformation software vendor, leading teams of project managers, functional consultants and engineers across three offices. Delivered enterprise content services, business process automation, deep archival and data-governance platforms for financial services, government and healthcare — including semantic search with recommendation, records and legal-hold classification, PII and PCI handling, streaming-backed viewers, multi-source API gateways spanning CRM, e-signature and mainframe systems, and a core microservice platform of gateway, registry, storage, notification and scheduling services.

    3 Regional Offices Semantic Search & Archival Core Microservices Platform
  4. 2019 — 2020

    National startup accelerator & incubator

    Chief Technology Officer · Program Director

    CTO across an accelerator and incubator ecosystem, and program director for internationally funded agri-food and cleantech programmes. Set the technical direction for startups building on mobile, web, AI and blockchain stacks, drove each cohort from proof of concept through MVP to market-ready product, and built partnerships with major cloud and enterprise vendors to underpin the ecosystem.

  5. 2019

    Independent consultancy — GCC

    Senior Digital Transformation Consultant

    Technical architecture and technology selection for e-government programmes, directing a 28-engineer delivery team and defining architecture plans built to reduce total cost of ownership, alongside marketing-automation programmes for regional banks and enterprises.

  6. 2009 — 2019

    Global capital-markets software publisher

    Senior Product Manager · Project Manager · Senior Developer

    A decade inside one of the largest capital-markets software publishers, ending as technical infrastructure product owner for the flagship trading, treasury, risk and post-trade platform. Owned the infrastructure roadmap across cloud, virtualisation, operating systems, compilers, databases and hardware; led the technical operation moving a monolith to SaaS on public cloud; ran a cross-functional transformation migrating 500+ physical machines and replatforming the OS and database estate with zero downtime and 40% more capacity; cut hardware cost 30% and certification time 60%; and delivered a data-masking product and a global QA automation framework executing over 200,000 tests daily.

    500+ Physical Machines Migrated 200K+ Tests Daily Zero Downtime Replatform
  7. 2007 — 2009

    Regional banking software firm

    Team Leader · Senior Software Developer

    Led delivery of an internet banking application integrated with core banking web services, architected as a three-tier system with message-broker load balancing, plus stock-exchange reporting integration and a card rewards platform.

  8. 2017 — PRESENT

    Developer community leadership

    Community Lead — Beirut

    Leading a developer community of more than 7,000 engineers, hosting 55+ code labs, hackathons and technical events, including the first TechCrunch event in the MENA region.

Working Stack

What I actually build with.

Compiled from the live code fleet rather than a wish list — the technologies appearing in systems I have designed, written or run in production.

AI & inference

Open-weight LLM serving · quantised local runtimes · OpenAI · Anthropic · Azure OpenAI · Gemini · Groq · provider abstraction layers · Model Context Protocol · multi-agent orchestration · structured output · LLM-as-judge · prompt systems · evaluation harnesses

Retrieval & data

Hybrid BM25 + dense retrieval · reciprocal rank fusion · Apache Solr · OpenSearch · Qdrant · pgvector · Chroma · Neo4j knowledge graphs · embeddings & rerankers · PostgreSQL · MongoDB · Redis · ClickHouse · Kafka · Spark · Airflow

Speech & media

Whisper-class ASR · speaker diarization · voice activity detection · speaker embeddings · neural machine translation · text-to-speech · programmatic video generation · OCR & document extraction · digital twins · AR / VR / XR

Platform & runtime

Kubernetes · Helm · Argo CD & GitOps · CloudNativePG · cert-manager · ingress-nginx · Docker · Terraform · Ansible · Prometheus · OpenTelemetry · Grafana · AWS · Azure · GCP · on-premise & air-gapped

Cloud operations & AIOps

Multi-account AWS organisations & landing zones · cross-account asset inventory · incident management platforms · managed foundation models for detection & remediation · agentic DevOps tooling · enterprise APM & automation · managed Kubernetes & container fleets · managed relational database estates · segmented VPC architecture · next-generation firewalls · enterprise DNS / DHCP / IPAM

Engineering

Python · TypeScript · Java · C# / .NET · Dart & Flutter · Go · PHP · FastAPI · Node & Express · Spring · React · Next.js · Vue · Angular · microservices · event-driven design · API gateways · enterprise service bus · BPM & case management

Security & governance

OIDC · SAML · LDAP federation · Keycloak · MFA · RBAC · multi-tenant isolation · encryption at rest · secrets custody · network policy · SBOM & dependency scanning · rate limiting · immutable audit logging · ISO & GDPR alignment · data residency

Field notes

Architecture thinking, made inspectable.

Focused technical notes for teams deciding where autonomy belongs, where the trust boundary sits, and how AI runs when data cannot leave.

Questions

Straight answers.

Written to be read by people evaluating an engagement — and quoted accurately by the answer engines they ask first.

Who is Salah Awad?

Salah Awad is a solution and enterprise architect and former chief technology officer based in Île-de-France, France. He has built software professionally since 2007, across financial-markets software, enterprise content and process platforms, national digital-government programmes, startup ecosystems and industrial AI.

He currently serves as Program Director for cloud transformation at a global aerospace group, leading a migration programme spanning more than 2,500 virtual machines, and previously served as co-founder, CTO and CIO of an AI-powered industrial training company. He holds a Master's degree in Computer Science and works in Arabic, English and French.

What does a solution architect actually deliver?

A defensible decision, and the evidence behind it. That means a current-state assessment of the existing estate, a set of genuinely competing architectural options rather than one preferred answer dressed up with alternatives, and an explicit scoring framework — security, availability, ecosystem interoperability, usability, scalability and total cost of ownership — applied to each.

In practice I have run exactly this comparison between a centralised enterprise service bus, a decentralised federated model where each department keeps its own infrastructure behind standardised communication contracts, and a custom stack of document management, low-code case design and business process engines. The deliverable is the target architecture, the technology roadmap, and a rationale that survives being challenged by the people who have to fund it.

Agentic AI or classical AI — when should a company use each?

Classical AI is bounded: a model is given a defined task — transcribe this call, separate these speakers, translate this text, retrieve these documents, score this record — and returns a result you can measure against ground truth. Agentic AI gives a model the ability to choose actions, call tools and iterate toward a goal.

Use classical AI when the task is well defined and accuracy is measurable. It is cheaper, faster, auditable and far easier to certify. Use agentic AI when the path to the answer genuinely cannot be enumerated in advance — multi-step research, cross-system orchestration, exception handling that would otherwise need a human.

Most failing AI programmes chose an agent where a pipeline would have worked, or shipped an agent with no termination condition, no typed tool contract and no audit trail. The judgement of which track to take is most of the architectural value.

How do you expose enterprise APIs to AI agents securely?

Never by handing an agent a generic HTTP client. Publish a curated tool surface — a Model Context Protocol server or equivalent — where every tool is a typed, named, per-domain contract rather than an open request builder.

Put the agent's identity behind the same identity provider as your human users so every call is attributable. Scope tokens to the tool rather than to the caller's full rights. Gate any generic escape-hatch tool behind an explicit manifest. Bound and truncate tool results. Log every invocation with its arguments to an immutable audit trail. The trust boundary belongs between the model proposing an action and the deterministic code that authorises it.

What is secure multi-layer — defense-in-depth — architecture for AI?

It is designing on the assumption that every control eventually fails, and layering independent controls so no single failure is fatal.

For AI systems the layers are: network and deployment isolation, up to fully air-gapped operation where policy requires data to remain inside the premises; federated identity with multi-factor authentication and role-based access control; per-tenant data isolation; a constrained tool surface for any agent; deterministic verification of model output before it takes effect; encryption of data at rest and of stored credentials; rate limiting and abuse controls; supply-chain gates such as software bills of materials and dependency scanning in CI; and immutable audit logging across all of it.

Can large language models run fully on-premise or air-gapped?

For regulated, defence, sovereign and industrial workloads with strict residency, confidentiality or connectivity constraints, on-premise or air-gapped deployment may be required. Quantised open-weight models on a local inference runtime can handle transcription, translation, extraction, summarisation, classification and retrieval-grounded answering while keeping inference data inside the controlled perimeter when egress, telemetry and artifact flows are correctly configured.

The architectural effort goes into the provider abstraction, so the same application runs against a local runtime or a hosted API by configuration; a CPU-only degradation path for sites with no accelerator; concurrency control so a single GPU is not overrun; and packaging the entire stack for environments with no internet egress.

What does conversation and contact-centre AI involve in practice?

Considerably more than calling a transcription API. A production pipeline needs voice-activity detection to segment audio, speaker diarization to establish who spoke when, a speech recognition model tuned for the actual dialect in use rather than textbook language, domain-dictionary correction for the vocabulary specific to that business, a model-based correction and hallucination-suppression pass, and text normalisation before any analysis begins.

Only then does the interesting layer run: sentiment, risk, empathy and quality scoring, referral suggestions, and searchable conversation history. I have built this stack end to end for Levantine Arabic — real-time, speaker-identified, with a bilingual right-to-left operator interface and local model inference so recordings never leave the operator's infrastructure.

How do you operate a cloud estate spanning over a thousand accounts?

At four-figure account counts the binding constraint stops being any individual workload and becomes coherence: knowing what exists, who owns it, what changed, and what is currently broken.

That requires a single operations plane above the accounts rather than per-account tooling — a canonical cross-account inventory of compute, container, cluster and database resources; an incident model that survives ownership boundaries; and governance applied at the landing-zone level rather than negotiated account by account. The network and security estate has to be integrated into that same plane — segmented virtual networks, next-generation firewalls, and enterprise DNS, DHCP and IP address management — or the inventory is fiction. Only once that spine exists is automation worth adding.

What is AIOps, and can AI actually resolve incidents automatically?

Alerting is not operations. Once a canonical inventory and a single incident plane exist, managed foundation models and agentic DevOps tooling can be wired directly into them — to correlate signals across the estate, triage an incident to its owning service, explain the probable root cause in language an on-call engineer can act on, and execute a bounded remediation rather than paging a human to run a runbook by hand.

The engineering discipline is identical to any other agentic system: bounded action surfaces, deterministic verification before anything changes, and an immutable audit trail of every automated action taken. An agent that can restart a service must not be able to delete one.

What kind of engagements do you take on?

Target-state architecture and technology roadmaps. Agentic and classical AI system design, and review of AI architecture that is already in flight. Secure multi-layer platform architecture for regulated environments. Cloud transformation and migration-factory programme design, including FinOps and ROI governance. Fractional or interim CTO engagements covering technical due diligence, engineering organisation design and delivery governance.

Engagements run in English, French and Arabic, across Europe, the Middle East and North America.

Contact

DIRECT ADVISORY & CTO INQUIRIES · 24-HOUR RESPONSE

Tell me what has to survive.

The most useful first message describes the constraint, not the technology: the audit you have to pass, the outage you cannot have, the data that cannot leave the building, or the date that will not move.

Tip: Press Ctrl+Enter to send

Direct to Salah Awad's inbox. No automated marketing sequences, no third parties.