What we mean by expertise
A list of technologies proves nothing. What matters is what runs in production, for real users, with the constraints that come with it: latency, cost, failures, compliance, multi-year maintenance.
4YA designs and operates its own products. The building blocks described here are not declared skills: they are the ones we maintain ourselves, daily, on systems that serve customers.
Our engineering domains
Computer vision and real-time processing
Continuous video-stream analysis on embedded hardware: intrusion detection, perimeter breach, abnormal behaviour. The constraint is not the model, it is holding latency across dozens of simultaneous streams without saturating the network link or the budget. Hence edge processing rather than cloud upload.
Autonomous agents and model orchestration
Agents that execute complete business processes, not chatbots that reply. The real difficulty is orchestration: managing state, recovering from errors, tracing every decision, and bounding what the model is allowed to do. We build these loops with LangGraph and n8n, on controlled infrastructure.
Sovereign and edge infrastructure
Deploying open-weights models on controlled infrastructure, local or Moroccan, with no dependency on a foreign API. Sovereignty is not a contract clause: it is decided the moment you choose where compute runs and where data rests.
Transactional and payment systems
Checkout, correlation with video, fiscal traceability, degraded-mode operation when the network drops. A POS system is not allowed to lose a transaction: reliability requirements are closer to embedded systems than to web apps.
Hardware, firmware and IoT
Board design, real-time firmware, field connectivity and over-the-air updates. This layer explains why our vision systems hold on constrained hardware: we know what happens below the operating system.
How we work
Scoping. We start from the actual process, not the technology. What is measured, what costs, what repeats. Many requests are solved without artificial intelligence — we say so when that is the case.
Proof of concept. A narrow scope, on your data, with a success criterion agreed beforehand. The goal is to know whether it works in your context, not to produce a flattering demo.
Industrialisation. Production rollout, monitoring, documentation and handover. A system you cannot operate without us is not delivered.
What we commit to
The code and models are yours. At the end of a project you hold the sources, the model weights where applicable, and the operating documentation. There is no hidden component locking you in.
Your data stays where you decide. Local or Moroccan infrastructure by default, in line with law 09-08 and CNDP requirements. No stream goes to a third-party API unless it is an explicit, documented choice.
No subcontracted engineering. The team that scopes is the team that builds and operates. You get one technical counterpart, not a chain of intermediaries.