South Africa is a local-first dating market. Members are looking for people in their city, in their language, and they are unusually attentive to whether a product takes safety seriously.
City-level discovery boundaries and multiple languages in onboarding are per-brand configuration. A product that shows someone matches four hours away, in a language they did not choose, has already told them what it is.
Per-market pricing in rand, through the payment methods the market expects, is configuration rather than a bespoke build — and it is the difference between a plan that converts and one that is technically available.
This market rewards products that show their work: verification marks displayed by default, scam warnings surfaced where money is discussed, and a reporting path that visibly leads somewhere. All three are configuration and platform behaviour on D8N rather than a design exercise.
DateZA is a local dating brand running on D8N in South Africa today, which is where the market-scoped discovery and multi-language onboarding work was proven.
If the answer you need isn’t here, ask us directly — we will tell you plainly when D8N is not the right fit.
Yes. DateZA is a local dating brand running on D8N in South Africa, and it is where the market-scoped discovery and multi-language onboarding work was proven. The platform's rand pricing and local payment routing come from running it.
Yes. Market and distance boundaries on discovery are per-brand policy, and local-first is the default for a brand configured this way.
Yes. Onboarding language is part of the brand definition, and multiple languages per market are supported.
Yes. Your name, domains, theme, copy, pricing, app store listings and member relationships are yours. The only D8N marks members see are the trust marks — Protected by D8N and D8N Verified — which exist because a visible mark is what makes verification worth passing.
Tell us the market, the audience and whether you are launching a new brand or adding D8N to an app you already run. Those three answers decide whether white label, the API, or a custom build is the right shape, and we will say plainly if it is none of them.