Now recruiting launch partners

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.

Bring Your App to North Africa
Bring Your App to North Africa
Mobile
<br/>
<em>SDK</em>
01

Mobile
SDK

REST
<br/>
<em>API</em>
02

REST
API

White-Label
<br/>
<em>App</em>
03

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.

  • check icon~10% card penetration in Egypt
  • check iconCash and cash-on-delivery still dominate spending
  • check iconCarrier billing and mobile money close the gap
Demand Isn't
<br/>
<em>the Problem</em>

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.

  • check iconCarrier billing and mobile-money payment
  • check iconArabic and French localization support
  • check iconLocal marketing across all six countries
One Agreement
<br/>
<em>Reaches Six Markets</em>

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.

  • check iconAnghami: 35+ carrier-billing partnerships
  • check iconOrange enabled Spotify carrier billing in Morocco (2023)
  • check iconTruecaller: 100M+ MAU, live Telecom Egypt integration
  • check iconAltibbi's revenue-share deal with Libyana is live in Libya today
Already Proven
<br/>
<em>Just Not By Us Yet</em>
star iconplan icon

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.

Book a Call
Book a Call

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.

  • check icon

    Mobile SDK for your existing iOS/Android app

  • check icon

    REST API for a custom storefront or bundle

  • check icon

    White-label app, ready to brand and launch

Talk to Our Team
Talk to Our Team

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

Mobile SDK

REST API

REST API

White-Label App

White-Label App

Why Work
With Clementine

Skip the Local Build

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

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

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.

shape

Frequently Asked
Questions

What does Clementine actually do?

Clementine is a distribution broker, not an app developer or a storefront operator. We sit between global consumer apps and North African distributors — telecoms, retailers, OEMs, app stores — and handle carrier billing, mobile-money payment, and Arabic/French localization, so publishers don't have to build any of it themselves.

Which markets does Clementine cover?

Morocco, Algeria, Tunisia, Libya, Mauritania, and Egypt. Egypt has the most developed carrier-billing infrastructure today; Libya and Mauritania are the least served and represent the earliest-stage opportunity.

What's the difference between the SDK, API, and white-label options?

The Mobile SDK drops into your existing app and handles local payments and localization while you keep your own front door. The REST API is a headless option for teams building their own storefront or bundle. The White-Label App is a ready-to-brand app you can put your name on and launch without building anything yourself. All three run on the same catalogue and back-end relationships — the difference is how much you want to build.

Why can't global apps just monetize North Africa directly?

It's an infrastructure problem, not a demand problem. Many of these apps are already used organically across the region. What's missing is a way to get paid — card penetration is as low as ~10% in Egypt, cash and cash-on-delivery still dominate, and few global apps have a carrier-billing or mobile-money relationship in any of these six markets. That's the specific gap Clementine closes.

Is Clementine live yet? Do you have existing clients or partners?

Not yet, honestly. Clementine is a new company at the early-partnership stage, and we're recruiting our first publishers and distributors now. The model itself is already proven elsewhere in the region — Anghami's 35+ carrier-billing partnerships, Orange's carrier billing for Spotify in Morocco, Truecaller's live Telecom Egypt integration, Altibbi's revenue-share with Libyana in Libya — we're packaging that same model across six markets, not claiming to have run it ourselves yet.

What does it cost to work with Clementine?

It depends on integration path, markets, and volume, since carrier billing, mobile money, and localization each carry different commercial terms. We structure every partnership individually rather than publish a flat rate card — get in touch and we'll put together a proposal for your specific case.

What kinds of apps is Clementine built for?

Categories like health and wellness, education, entertainment, dating and social, mobility and delivery, travel, kids' safety, productivity, and mobile gaming — the kinds of consumer apps our platform is built to carry. Fintech, neobank, and physical-goods e-commerce are outside our scope today.
shape
avatar

Book an Intro Call

Tell us about your app, or your distribution business — we'll walk through the fit together.

Book a Call
Book a Call