The Distribution Layer
for Global Apps in North Africa
Carrier billing, mobile-money payment, and Arabic/French localization for six North African markets and 200M+ consumers — through one relationship, not six separate ones.
Mobile
SDK
REST
API
White-Label
App
A Model That
Already Works
Demand Isn't
the Problem
Global apps are already used organically across North Africa. What's missing isn't interest, it's infrastructure — card penetration is as low as ~10% in Egypt, and cash still dominates.
~10% card penetration in Egypt
Cash and cash-on-delivery still dominate spending
Carrier billing and mobile money close the gap

One Agreement
Reaches Six Markets
Instead of negotiating carrier billing, mobile-money rails, and localization country by country, publishers and distributors work through a single relationship spanning Morocco, Algeria, Tunisia, Libya, Mauritania, and Egypt.
Carrier billing and mobile-money payment
Arabic and French localization support
Local marketing across all six countries

Already Proven
Just Not By Us Yet
Anghami built MENA's leading music app on 35+ carrier-billing partnerships. Orange enabled Spotify's carrier billing in Morocco in 2023. Truecaller already serves 100M+ monthly users across the region with a live Telecom Egypt integration. The model works — Clementine packages it for six markets at once.
Anghami: 35+ carrier-billing partnerships
Orange enabled Spotify carrier billing in Morocco (2023)
Truecaller: 100M+ MAU, live Telecom Egypt integration
Altibbi's revenue-share deal with Libyana is live in Libya today

Let's Talk
North Africa
Bringing an app into North Africa, or looking to offer your customers
a bigger catalogue of global apps? One call is enough to see if we're a fit.
How Clementine
Gets You Live
One agreement. Three integration paths into North Africa's six markets.
- 01
Choose Your Path
- 02
We Handle Setup
- 03
Go Live
Mobile SDK, REST API, or White-Label App
Keep your own app and add our SDK, build on our REST API for a custom storefront, or launch fast with a ready-to-brand white-label app. Same catalogue and back-end for all three — pick the integration effort that fits your team.
Mobile SDK for your existing iOS/Android app
REST API for a custom storefront or bundle
White-label app, ready to brand and launch
One Catalogue, Three Ways In
Every path runs on the same catalogue, billing, and localization.
Choose based on engineering effort, not on what you get access to.
Mobile SDK
REST API
White-Label App
Why Work
With Clementine

Skip the Local Build
SDK, API, or white-label — pick the integration effort that fits your team, and let Clementine handle carrier billing, mobile money, and localization instead of building it yourself.

One Catalogue, Not Dozens of Deals
Distributors get a growing, pre-vetted catalogue of global apps across health, education, entertainment, gaming, and more, through a single commercial and technical relationship.

A Broker Model That Already Works
Carry1st and Tamatem already broker global game publishers into MENA markets through local payments and marketing. Clementine applies the same model across every category, not just games.

Frequently Asked
Questions
What does Clementine actually do?
Which markets does Clementine cover?
What's the difference between the SDK, API, and white-label options?
Why can't global apps just monetize North Africa directly?
Is Clementine live yet? Do you have existing clients or partners?
What does it cost to work with Clementine?
What kinds of apps is Clementine built for?

Global Apps.
Local Reach.
Book an Intro Call
Tell us about your app, or your distribution business — we'll walk through the fit together.