Team

The Team Behind Our IT Projects

You work directly with the people who plan, build, and operate. We keep roles clear, document decisions, and make sure systems remain understandable in daily use.

Technology
AWSAzureGoogle CloudKubernetesDockerTerraformGitHub ActionsCloudflarePostgreSQLRedisNext.jsReactNode.jsPythonn8nOpenTelemetryGrafana

How We Make Decisions

Good software is built when requirements are understood, trade-offs are made visible, and decisions are documented. Three principles shape how we work with you:

Technical curiosity with restraint

Curiosity matters, reliability matters more. We choose tools so your product stays maintainable long-term and your team enjoys working with it.

  • Technology decisions guided by maintainability, security, performance, and operations
  • Cloud and infrastructure with substance: Docker, Kubernetes, AWS, or Azure, fit to your setup
  • Automation that saves time day-to-day: CI/CD, monitoring, alerts, and n8n workflows instead of manual routines

If a new library looks exciting but risky, we state the risks openly and propose a robust alternative.

Honest communication

You get plain language instead of buzzwords. We talk early about risks, dependencies, and trade-offs, document decisions clearly, and sometimes say “stop” when a request would do more harm than good.

Solution oriented

When something breaks, we look for causes, not someone to blame. We reproduce issues, ship clean fixes with tests and monitoring, and improve the foundation so the same bug does not come back.

A look at our core team

Here are the people and roles that take responsibility in projects: architecture, delivery, operations, security, and automation.

Founder & Lead Architect

Aziz Ajaghfouf

“Value appears when technology solves a concrete problem in operations or processes.”

AWSAzureKubernetesTerraformApache KafkaPython

Favorite moment: a release that feels boring because the foundation is solid.

Senior AI & Automation Engineer

Alexander Haus

“Artificial intelligence creates value only when the backend behind it is stable. An AI model is only as useful as the data pipeline that feeds it.”

Python / FastAPIAWS CloudApache KafkaPyTorch / RAGKubernetesDocker

Favourite moment: showing a client that a clean Python script can solve the problem faster than the most expensive AI model.

AI Engineer & Solution Architect

Mohamed-Ali Masmoudi

“A prototype can be built over a weekend now. The remaining 20 percent decide whether it becomes a product.”

TypeScriptVue / ReactLLM / RAGLangChain / LangGraphPostgreSQL / pgvectorDockerCloudflare PlatformOpenShiftAzure

Favourite moment: when a complex technical problem turns into a solution that feels simple for the user.

Senior Enterprise Cybersecurity Architect

Malik Kimani

“Security should not get in the way of day-to-day operations, but gaps in controls can put them at risk. My job is to strike that balance in architecture and code.”

AWS & Azure SecurityTerraform (IaC)Kubernetes SecuritySIEM & SOAR

Favourite moment: Running 'terraform apply' to deploy a security architecture where the development teams' access needs have been considered from the start.

Full-stack Web Developer & Application Security

Jan Weber

“Security is not a box to tick at the end of a project. It belongs in the architecture from the start. Good code is resilient by design.”

TypeScript (Node.js/React)PostgreSQL / RedisSnyk & SonarQubeOWASP Security Tools

Favourite moment: Reviewing a pull request where performance and security have already been thought through, making the review straightforward.

Head of Project Management

Andreas Schneider

“Good project management is almost invisible. It gives developers room to focus and keeps decision-makers informed about where the project stands.”

Jira & ConfluenceResource & Budget PlanningScrum & KanbanRisk Management

Favourite moment: When 'That's just how the system evolved' finally becomes 'We replaced that last week.'

Experiences that matter

Michael Tietz

“We've worked with Aziz and his team since 2018. They're approachable, easy to work with, and dependable. We really value their support, whether we're dealing with a complex technical issue or something that comes up in our day-to-day work.”

Managing Director, Stevia Group

Luca Fernandes

“We used to rely on a lot of manual handoffs between sales and fulfillment, which left room for errors. The new automation is well documented and saves us a great deal of time in our day-to-day work.”

E-Commerce / Wholesale, L’Oréal

Kerim Hammad

“We can raise an issue without having to work out the technical answer ourselves first. The responses are easy to understand, and we know what happens next. That makes working together day to day much easier.”

Marketing & Communications, Aktiv Apotheken OHG

Michael Tietz

Managing Director, Stevia Group

“We've worked with Aziz and his team since 2018. They're approachable, easy to work with, and dependable. We really value their support, whether we're dealing with a complex technical issue or something that comes up in our day-to-day work.”

Luca Fernandes

E-Commerce / Wholesale, L’Oréal

“We used to rely on a lot of manual handoffs between sales and fulfillment, which left room for errors. The new automation is well documented and saves us a great deal of time in our day-to-day work.”

Kerim Hammad

Marketing & Communications, Aktiv Apotheken OHG

“We can raise an issue without having to work out the technical answer ourselves first. The responses are easy to understand, and we know what happens next. That makes working together day to day much easier.”

1 / 3

How we work

We work mostly remote, document decisions, and keep alignment short. What matters is that tasks, risks, and next steps stay visible.

  1. Remote first

    Async, documented, focused. Fewer meetings, more clear artifacts, fast decisions, and clean hand-offs.

  2. Quality in daily work

    Tests, reviews, and security are part of the workflow. We would rather ship smaller, traceable, and maintainable increments.

  3. Continuous learning

    We invest in research, share learnings, and modernize intentionally, without chasing every trend.

Want responsibility?

If you like taking responsibility, documenting clearly, and building reliable systems, we will probably work well together.

Experienced environmentResponsibilityRemote firstClear standardsContinuous learning

Technical Focus Areas in the Team

How experience and responsibility are distributed across projects.

Cloud Architecture & Platform Operations

Our cloud and systems engineers plan infrastructure that can be operated, changed, and understood. AWS, Azure, Linux, containers, and Infrastructure as Code are used where they improve operations and maintainability.

Cloud ArchitectsSystems EngineeringDevOps CulturePlatform EngineeringIT Operations
Learn more →

Data Processes & Automation

Our automation and data specialists start with the actual workflow. From there, they build integrations, workflows, and LLM applications that make data easier to use and reduce manual work.

Data EngineeringPromptingProcess ConsultingAI IntegrationBackend Development
Learn more →

Full-Stack Development & UX/UI

Design and development work closely together: user journeys, interfaces, data models, and performance are considered as one system. The result is digital products that feel clear and remain technically maintainable.

Full-Stack DevReact / Vue.jsUI/UX ResearchE-Commerce ArchitectureAgile Teams
Learn more →

Security & Compliance

Our security work starts with baselines, access, monitoring, and traceable processes. We review risks from an attacker-aware perspective and translate regulatory requirements into measures that remain manageable in operations.

Security ReviewsIAMHardeningIncident ReadinessCompliance Advisory
Learn more →

Get
to know us personally

Frequently asked questions

In a short call we clarify whether collaboration makes sense technically and organizationally.

Who will I work with day-to-day?

Directly with the people who plan and ship. No account-manager ping-pong, clear ownership, short feedback loops, fast decisions.

How does collaboration work in practice?

Transparent updates, clear priorities, and regular reviews. You always know status, decisions, risks, and next steps.

Are you more ‘consulting’ or ‘delivery’?

Both, practical by default. We start with clarity (strategy/roadmap) and then deliver in clean sprints, including operations and iteration.

Do you work remote or on-site?

We work mostly remote. Workshops and kick-offs can happen on-site when it makes sense for the work.