# Why Morocco is becoming Europe's AI engineering nearshore > A national AI plan in implementation, a data-center buildout and an offshoring sector moving into engineering. What the 2026 numbers mean for teams hiring here. _Mati Mouni, Sep 22, 2026._ ## From call centers to code: how Moroccan offshoring is changing We started Matious in Morocco in 2017 with two engineers. Back then, "offshoring in Morocco" mostly meant customer-service centers. The 2026 data shows how much that picture has changed. The sector is already large. At the end of 2024, Moroccan offshoring employed 148,500 people and generated MAD 26.22 billion in service exports, [according to TechAfrica News](https://techafricanews.com/?p=70529). The government's 2030 targets are about MAD 40 billion and 270,000 jobs, backed by agreements that include a training-grant scheme and a new Casablanca Tech Valley zone in Sidi Othman. The mix is shifting too. [Outsource Accelerator reports](https://news.outsourceaccelerator.com/morocco-offshoring-german-firms/) that German engineering firms such as Bertrandt and FEV Group are moving software development, testing and validation work into Moroccan technology parks. That is engineering work close to the core of a product, placed here by companies with demanding quality standards. It is a better signal than any marketing claim, ours included. ## Morocco AI 2030: talent and infrastructure targets In September the national AI strategy moved into implementation, [as Hespress and MAP reported](https://en.hespress.com/145114-145114.html). The 2030 targets are MAD 100 billion (about $10 billion) added to GDP, 50,000 direct and indirect jobs, and 200,000 AI talents trained and certified. New initiatives include the JAZARI institutes, a sovereign AI marketplace and Idarati AI, an agentic assistant for administrative procedures. Targets are targets. We would encourage any client to judge them by delivery over the next few years, not by the announcement. The direction still matters to anyone planning a team here. A training target of that size means more graduates with applied AI skills entering the market each year. And an administration building its own agentic systems creates local demand for the same skills we sell abroad, which gives experienced engineers good reasons to build their careers in Morocco. For a client, that is what makes it realistic to keep the same team into year three. The ecosystem is also more visible than it was. GITEX Africa 2026 in Marrakech, held April 7 to 9, drew more than 55,000 visitors, 1,500 exhibitors from 58 countries, 412 investors and over 4,600 business meetings, [Le Desk reported](https://ledesk.ma/encontinu/gitex-africa-2026-55-000-participants-412-investisseurs-et-4-600-reunions-daffaires-a-marrakech/). For transparency: Le Desk was a client; we ran its [ad operations](/work/ledesk). ## Data centers and data sovereignty: what it means for clients BMI research, [reported by Le360](https://en.le360.ma/economy/moroccos-data-center-capacity-set-to-surge-as-ai-and-cloud-investment-accelerates-report-says_MYVV3TMHRJHN7MNV3WDYZSZERQ/), counts 14 data centers in Morocco, with 140 MW of capacity under construction and 400 MW planned. Cloud spending is forecast to reach $981 million by the end of 2026 and about $2.7 billion by 2031. Since 2021, rules have required sensitive data to be hosted in Morocco. For most of our European and American clients this matters less than it might seem, and it is worth being precise about why. When a company in Paris or Boston works with our engineers, its production data normally stays where it already lives, in its own cloud accounts, and our engineers work inside those environments under the client's identity and access controls. The Moroccan hosting rules concern Moroccan sensitive data. They come into play when we build for Moroccan institutions, or for a foreign company launching a service in Morocco. That second case is where the buildout helps. More local capacity gives companies serving Moroccan users more options for keeping data in the country without compromising on infrastructure. ## Time zone, languages and data protection: the practical case The everyday argument is simpler than any national strategy. We work on UTC+0 all year, so our working day overlaps almost entirely with London, Paris and Berlin. Standups happen at the client's standup time. A bug reported mid-morning in Lyon is looked at by someone who is also at their desk. For clients on the US East Coast, our afternoon covers their morning, which is enough for a daily sync and same-day code review. Language matters more than people expect. We deliver in English, French and Arabic. For a French client, being able to run a product review in French, read regulatory documents in the original and write user-facing copy without a translation step removes friction nobody notices until it is gone. For Gulf and North African products, Arabic and right-to-left interfaces are home ground. We shipped [Daryo](/work/daryapp) in French, Arabic and English with full RTL support. On data protection, Morocco's Law 09-08 governs personal data. Morocco does not have an EU adequacy decision, so European clients sending personal data to a Moroccan team should put standard contractual clauses in place, as they would with most suppliers outside the EU. In team-extension work the cleaner pattern is to avoid the transfer altogether: engineers work in the client's environment, on anonymized or synthetic test data, and production access follows the client's own policies. Ask any partner how they handle this. The quality of the answer tells you a lot. ## Team extension vs. outsourcing vs. local hiring These are different tools for different jobs, and many companies end up using more than one. Local hiring gives you the most control and the deepest context. It is the right choice for roles that need to be in the room: leadership, people close to customers, anything that depends on in-person presence. Its limits are time to hire and the depth of the local market for specific skills. Project outsourcing works when the scope is well defined and the result can be handed over at the end, such as a new mobile app or a platform rebuild. You are buying an outcome. The risk is that knowledge leaves with the vendor, so insist on documentation and a proper handover. Team extension sits between the two. Engineers join your team, attend your standups, use your tools and work on your roadmap, while the partner handles recruitment, retention and employment. We offer it because several clients asked to keep our engineers full-time once a project was done. [LUBU Technologies](/work/lubu) is the clearest example. Since 2024 we have been their embedded software partner, building and maintaining the mobile app, frontend interfaces, backend services and APIs that connect their smart insoles to users, while their own team concentrates on hardware and clinical development. With [Frontier Car Group](/work/fcg), our engineers worked inside the team on marketing automation across its used-car marketplaces in several emerging markets. One shape that works well is a local tech lead and product owner on the client side, with an extended team in Morocco doing most of the build and owning parts of the system outright. ## How to evaluate a Moroccan engineering partner If we were on the other side of the table, these are the questions we would ask. - **Who exactly will work on my product?** Interview the engineers, not only the account manager. At Matious, clients meet and approve profiles before anyone starts. - **How long do your engineers stay?** Retention decides whether the person who learns your codebase in month two is still there in month twenty. - **Can I see comparable work?** Ask for case studies with architecture detail, and ask to speak with a current client. - **How will you handle my data?** Expect clear answers on access, environments, contractual clauses and offboarding. - **What happens when someone leaves?** There should be a documented handover and a replacement process with a timeline. - **Who owns the code and the accounts?** Repositories, cloud accounts and app-store accounts should be in your name from the first day. Then start with a small paid engagement on a real piece of your roadmap before committing to a large team. Two or three months of actual delivery will tell you more than any proposal. If you are weighing this for 2027, we are happy to [talk it through](/contact). ## Sources - [Morocco AI 2030 moves into implementation](https://en.hespress.com/145114-145114.html), Hespress / MAP, September 8, 2026 - [Morocco's data center capacity set to surge as AI and cloud investment accelerates](https://en.le360.ma/economy/moroccos-data-center-capacity-set-to-surge-as-ai-and-cloud-investment-accelerates-report-says_MYVV3TMHRJHN7MNV3WDYZSZERQ/), Le360, July 10, 2026 - [Morocco's offshoring sector and 2030 targets](https://techafricanews.com/?p=70529), TechAfrica News, January 29, 2026 - [German firms move software work to Morocco](https://news.outsourceaccelerator.com/morocco-offshoring-german-firms/), Outsource Accelerator, March 13, 2026 (updated September 16, 2026) - [GITEX Africa 2026: 55,000 participants, 412 investors and 4,600 business meetings in Marrakech](https://ledesk.ma/encontinu/gitex-africa-2026-55-000-participants-412-investisseurs-et-4-600-reunions-daffaires-a-marrakech/), Le Desk, April 29, 2026 ## Related - All articles: https://matious.com/insights.md - Case studies: https://matious.com/work.md - Start a project: https://matious.com/contact ## Canonical URL https://matious.com/insights/morocco-ai-nearshore-engineering-2026 --- _Matious - AI engineering studio, founded 2017, Mohammedia, Morocco._ Contact: contact@matious.com | +212 661 790 436 | https://matious.com/contact Machine-readable: [llms.txt](https://matious.com/llms.txt) - [agent instructions](https://matious.com/agents.md) - [sitemap](https://matious.com/sitemap.xml) Every page is also available as Markdown: send `Accept: text/markdown`, or append `.md` to the URL.