Skip to content
T.E.N.E.G.T.A
Language

Founder-Led · Specialist Network

How We Work

T.E.N.E.G.T.A doesn't believe in the 'large team for everything' model. We build around each project exactly what it deserves — direct technical leadership from the founder, and additional specializations from a carefully curated network selected based on the nature of the challenge.

Founder & principal architect

Sadek Al-Etr

Founder · AI Engineer & Cybersecurity Specialist

Builds intelligent systems. Then tries to break them. Then builds them again.

An AI engineer and cybersecurity researcher from Damascus, holding a BSc in Information Technology Engineering — AI Major from Damascus University. What distinguishes Sadek isn't that he does all three things — it's that he understands how each one affects the others. When he designs an AI system, he's already thinking about how to attack it. When he assesses an application's security, he understands its architecture from the inside. When he builds an interface, he knows the cost of doing it wrong. Over 4+ years of freelance work, he has delivered projects spanning computer vision systems, intelligent financial analysis bots, penetration assessments for multiple web applications, and full backend architectures. He holds (ISC)² SSCP, IBM Cybersecurity Analyst, and eWapt v3 certifications in advanced web application penetration testing. T.E.N.E.G.T.A was born from a simple conviction: organizations that build with intelligence and think with an attacker's mindset are the only ones that last.
"A secure system isn't one that's hard to break — it's one designed from day one on the assumption that someone is trying."

The Intersection You Rarely Find in One Person

Most AI engineers don't understand security. Most security experts don't build systems. And very few of them also design. Sadek works at the triple intersection — and that's what makes the final product different.

  • AI Engineering

    ML · Computer Vision · Predictive Models

  • Cybersecurity

    Penetration Testing · OWASP · Zero-Trust

  • Software Engineering

    Backend · APIs · Systems Architecture

Where we stand

  • On AI without a decision layer

    A 94% accurate model in production beats a 99% model in a notebook — because operational decisions aren't built on metrics, but on what a manager can actually do with the output.

  • On Security as an add-on

    I refuse to build a system whose decisions I can't explain to the person who'll trust it — security isn't a final audit, it's an assumption on day one of design.

  • On The large team for everything

    Every project deserves the specialization it needs — not a fixed org chart. A curated specialist network per challenge beats ten generalists on every contract.

Credentials & stack

Certifications

  • (ISC)² SSCP · (ISC)²
  • IBM Cybersecurity Analyst Professional · IBM
  • eWapt v3 — Web Application Penetration Testing · eLearnSecurity
  • IBM Machine Learning Professional · IBM
  • Google Data Analytics · Google
  • Google UX Design · Google
  • Deep Learning Specialization · Coursera
  • Algorithms Part I & II · Princeton/Coursera

Technology domains

  • AI & ML

    PythonPyTorchCNNsRNNsVision TransformersOCRMLflowPandasNumPy

  • Cybersecurity

    Burp SuiteOWASP Top 10Penetration TestingSQLi/XSS/IDOR/CSRFNetwork SecurityVulnerability Assessment

  • Software Engineering

    DjangoFlaskREST APIsReactJSFlutter/DartSQLJavaScriptC++

  • Design

    FigmaAdobe XDUI/UXMotion GraphicsPrototyping

Specialist network

We work with a curated network of domain specialists — each engaged per project based on what the challenge actually requires, not what's on an org chart.

  • Founder on Every Project

    You won't talk to an account manager. You'll talk to the person who writes the code and understands the problem.

  • Specialization over Generalization

    Every project needs a different kind of expertise. We bring the right specialization to each challenge — not a single team spread across everything.

  • Built with an Attacker's Mindset

    Every system we build passes through security thinking from day one — because the person building it also understands how it breaks.

How we engage

  • How we assess every project

    We start by understanding the real problem behind what's described — then clarify whether the challenge is technical, operational, or architectural, and which metrics define success.

  • How we staff specialists

    We select from our specialist network who has experience in your sector and system type — while the founder remains accountable for architectural decisions and delivery.

  • What we don't take on

    We don't take projects without a clear operational owner, 'model delivery' without a production path, or security requests bolted on after the build is done.

How we think

  • The Problem Behind the Problem

    Before any line of code, we ask: what's really hurting? Not what you describe — but what makes you describe it. The right solution to the wrong problem is still wrong.

  • Security is an Architectural Decision, Not an Add-on

    We don't add security at the end of a project. We think about how to attack a system before we begin building it — because fixing a vulnerability after deployment costs multiples of preventing it in design.

  • Clarity over Cleverness

    Clever code that no one else understands isn't a virtue — it's a burden on whoever comes after. We write self-explaining code and save cleverness for problems that truly deserve it.

Start the conversation