One core or several. You choose.
Brands do not have to share every layer. We map where common services create leverage and where independent boundaries protect the business.
Shared core
One foundation for several brands
Share platform services while configuring currencies, payment methods, promotions and access for every brand.
Fewer duplicate systems to maintain as the portfolio grows.
Dedicated environments
Independence where the business needs it
Separate settings, operations and recovery plans by legal entity, licence or market.
More autonomy per business and less shared operational risk.
Hybrid model
Share only where it pays
Keep selected brands on one core while giving other businesses their own environment and operating boundary.
Reuse where it creates leverage without forcing one model on every brand.
| Compare models | Shared core | Dedicated environment | Hybrid |
|---|---|---|---|
| Platform core | Shared across selected brands | Dedicated to the business | Shared or dedicated by brand |
| Currencies, payments & promotions | Configured per brand | Configured in its own environment | Configured per brand and environment |
| Operations | One shared view with brand access | Independent operational control | Shared view where chosen |
| Legal entity / licence | Boundary agreed in scope | Dedicated boundary | Boundary defined per brand |
| Recovery planning | Shared baseline | Per environment | By selected environment |
| First stage | One module or shared foundation | One dedicated environment | Selected scope |
| Planning window | 3–4 months* | 3–4 months* | Confirmed after scope |
| Commercial scope | Confirmed after discovery | Confirmed after discovery | Confirmed after discovery |
*The 3–4 month planning window is for one brand and market with agreed scope, usable data and provider access. We confirm the commercial scope after those dependencies are reviewed.
Whichever model you take
Double-entry wallet
The only thing that can move money, in every model.
Two-person rule
Nine action types need two named approvers. Including for us.
Audit trail
Append-only. Corrections supersede, they never overwrite.
Per-entity isolation
One environment per licence, with its own keys and data residency.