21 years of building critical systems — from microcontroller firmware to sovereign LLM infrastructure.
From bare-metal PCB to sovereign LLM — every layer mastered in-house, nothing outsourced. One technical point of contact who understands the full stack.
Meet the team behind 4YA — full bio, projects, and how we work.
This timeline is not a résumé. It describes the capabilities the firm accumulated, period by period, and what each enables today. A skill only enters this list if it has served in production, not merely been learned.
The order matters: we came to artificial intelligence from below — from hardware, real time and systems that are not allowed to fail. This explains our architectural choices, notably the preference for edge processing.
Microcontroller firmware, board design, memory and power constraints. This period enforced a discipline you do not learn in business software: you cannot restart a device remotely, so the code must be right the first time.
Image processing on constrained hardware, then architectures distributed across several sites. This is where our V32 approach comes from: analyse as close to the camera as possible rather than uploading everything, because bandwidth and latency are scarce resources.
Designing and operating multi-tenant platforms for international markets. This period brought what embedded work does not teach: continuous deployment, monitoring, version management and long-term operating cost.
4YA was founded in 2020 in Marrakech. The structuring choice was sovereignty: building systems whose data stays in Morocco, at a time when most offerings ran through foreign services. That choice shaped the entire stack that followed.
SecurePOS and the V32 module went into production, followed by open-weights model deployment on controlled infrastructure and autonomous agents in real operation. This is when the firm moved from services to publishing: we operate our own products, with real users.
Few teams cover the same span: from circuit board to language-model orchestration. That span is not a showcase argument — it has a practical consequence. When a vision system must run on a low-power unit, or a till must keep taking payments with the network down, the answer does not come from the application layer.
It is also what lets us say no. A share of the requests we receive is solved without artificial intelligence, through a process fix or a simple integration. Placing the problem at the right layer saves more time than any model.