RIYADH, SAUDI ARABIA · SYSTEMS PRACTICE

ENGINEER.
BUILDER.
RESEARCHER.

I’m Shawki Aladdin—an Egyptian software engineer, CTO at Digital Harbor, founder of gitroots, and an independent researcher. I build systems, study their limits, and work on problems that are technically difficult and worth solving.

SYSTEM ARCHITECTURECODE GOVERNANCEAPPLIED AIINFRASTRUCTURESATELLITE SECURITY

01 / ABOUT

I LEARN SYSTEMS
BY WORKING INSIDE THEM.

I’m interested in what happens after a clean architecture diagram meets production: changing requirements, imperfect integrations, security boundaries, failure, maintenance, and people.

My work spans enterprise applications, developer tools, infrastructure, and software products. I enjoy understanding how a system works internally, locating where its model stops matching reality, and turning that gap into something practical.

I don’t separate strategy from implementation. Even in technical leadership, I stay close to architecture, code, incidents, deployment, and the decisions that make software dependable.

01SOFTWARE ARCHITECTURE

Systems that remain understandable as they grow.

02SECURITY + GOVERNANCE

Precise access, identity, and safer collaboration.

03AI + AUTONOMY

Constrained agents operating inside real boundaries.

04INFRASTRUCTURE

Reliable software across distributed environments.

05DEVELOPER TOOLS

Automation that removes friction without hiding control.

06SPACE SYSTEMS

Resilient computing where intervention is difficult.

02 / FOUNDER PROJECT

gitroots

gitroots.com ↗

I founded gitroots after running into a permissions problem that repository-level access could not solve.

We needed junior developers, contractors, and external contributors to work on assigned parts of confidential codebases without exposing everything else. Their permitted changes still needed to remain compatible with—and synchronize into—the primary development workflow.

I researched the available approaches and couldn’t find one that adequately matched the problem. gitroots became the working answer: source-code governance by person, path, branch, and workflow.

  • Fine-grained path visibility
  • Branch governance
  • Approval workflows
  • Isolated collaboration
  • AI-agent boundaries
  • Controlled synchronization
gitroots / POLICY_TRACEILLUSTRATIVE
$ git push origin main

▣ REPOSITORY  odoo-erp
▣ ACTOR       contractor_07
▣ SCOPE       /addons/inventory/**
▣ TARGET      main

[ PUSH BLOCKED ]
main is protected by policy GR-204.
Open a sync request from your assigned branch.

✓ DECISION RECORDED  gr_8f2a91
█

EARLY ACCESS SNAPSHOT / OCTOBER 2026 · ADOPTION FIGURES, NOT REVENUE

05
COMPANIES
EARLY ACCESS
≈35
USERS
EARLY ACCESS
60
REPOSITORIES
UNDER GOVERNANCE
19,919
PATHS
PROTECTED
✓
GITHUB
INTEGRATION
01
ODOO GOLDEN PARTNER
EARLY ADOPTER

03 / SELECTED WORK

PRODUCTS, PLATFORMS,
AND OPERATING SYSTEMS.

OPERATING PRODUCT · EARLY ACCESS01

gitroots

Source-code governance for controlling what contributors and AI agents can see, change, and synchronize.

VISIT gitroots ↗
EXPLORATORY PRODUCT02

CryptoRadar

A concept for programmable, event-driven cryptocurrency monitoring: thresholds, notifications, automated responses, and trade simulation.

VISIT CRYPTORADAR ↗
PLATFORM INITIATIVE03

ByteRoast

A cloud infrastructure initiative for provisioning, automation, and unified management through one approachable product experience.

VISIT BYTEROAST ↗
PROFESSIONAL PRACTICE04

Enterprise + Odoo Engineering

ERP customization, integrations, APIs, infrastructure, distributed services, deployment workflows, and operational systems built under real business constraints.

DIGITAL HARBOR

04 / RESEARCH

AUTONOMOUS PATCHING
WHERE HELP IS FAR AWAY.

I’m exploring whether constrained autonomous AI agents can identify, evaluate, and remediate selected software vulnerabilities on satellites while staying inside strict safety boundaries.

Satellite software operates under a different set of assumptions: communication windows are limited, latency is high, compute is constrained, recovery is complex, and human intervention may be delayed or unavailable.

The long-term question is broader than patching: how can autonomous computing remain useful, explainable, and recoverable in environments where a bad decision is difficult to reverse?

RESEARCH PROFILE ↗
01INTERMITTENT LINK

Limited communication opportunities and high latency.

02CONSTRAINED COMPUTE

Finite processing, memory, power, and thermal budgets.

03SAFETY BOUNDARIES

Critical software requires conservative, auditable actions.

04RECOVERY

Failures must degrade safely and remain reversible.

CONTINUOUS LEARNING

Pursuing master’s-level study in artificial intelligence through the Woolf and Udacity pathway, with interests in machine learning, deep learning, responsible AI, autonomous systems, and foundational computer science.

05 / TECHNICAL PRACTICE

STRATEGY ABOVE.
IMPLEMENTATION BELOW.

At Digital Harbor, my work covers technical direction and the implementation details that determine whether a system actually holds together.

Digital Harbor is a Saudi technology company focused on enterprise software, Odoo ERP implementation, integration, and digital transformation. I lead engineering teams, design applications, shape infrastructure and delivery workflows, and stay involved in security, reliability, and difficult production problems.

LANGUAGES + FRAMEWORKS

Python · JavaScript · TypeScript · Node.js · React · Next.js · Flutter · Odoo

BACKEND + DATA

PostgreSQL · REST APIs · service integrations · real-time communication · application architecture

INFRASTRUCTURE + DEVOPS

Linux · Docker · Kubernetes · K3s · Nginx · CI/CD · GitLab · cloud automation

SECURITY + AI

Identity · authorization · code security · software supply chain · PyTorch · neural networks · autonomous agents

A working set, not a claim of equal mastery across every tool.

07 / OPEN EXCHANGE

COMPARE NOTES.
BUILD THE HARD THING.

I’m interested in conversations about secure collaboration, enterprise systems, developer infrastructure, autonomous AI, and resilient software. The useful starting point is usually a real problem, a concrete artifact, or a question that refuses to stay simple.