Platforms
Platforms, licensed and white-labelled
Ten years of software built for enterprise engagements and acquired through the group, available to license and operate under your own brand. Built by the same practice that would otherwise build it for you from scratch.
Every platform page states what is white-labelled and what is not, what it runs on, who operates it after deployment, and the licensing model. No capability is described that the running software does not have.
The white-label programme
Technical evaluation
Against your requirements, run by engineers on both sides. If the software does not do what you need, this is where you find out.
Deployment
Your infrastructure, ours, or hybrid. The choice changes the support model and the cost, and both are stated before you commit.
Branding and integration
Configuration, brand, and the integration work into the systems you already run.
Operate
Run it yourself, or under managed services on a written responsibility split.
The catalogue
| Platform | What a licensee operates | Build status | Licensing model |
|---|---|---|---|
| Identity & accounts identity · sessions | One account across every surface a programme runs — web, mini-app and service-to-service. | LIVE | Annual licence + monthly active identities |
| Engagement & social systems quests · crews · leaderboards | The mechanics that make a programme habitual: streaks, quests, crews, duels, leaderboards and referral. | LIVE | Annual licence + monthly active users |
| Telegram & messaging apps mini-app · bots | A programme inside the messenger your audience already has open: mini-app, bot, notifications. | LIVE | Annual licence + volume |
| Wallet — service, mobile & extension wallet · balances | Balances and the credit path as a service. Native and extension clients are stated direction, not shipped software. | IN BUILD | Annual licence + accounts |
| Swaps & redemption gateway swap · spend · redeem | The path from a programme balance to something a participant actually wants. | IN BUILD | Annual licence + volume |
| Bridges & settlement settlement · cross-chain | Open settlement, and movement between chains. Stated direction — there is no bridge to license today. | NORTH STAR | Engagement, not a licence |
| Exchange & OTC infrastructure trading · settlement | A venue or dealer desk: order handling, matching, settlement instructions and an operator console. | INVENTORY PENDING | Annual licence + volume |
| Custody & wallet keys · approvals | Holding assets for clients: key management, approval policy, and the audit log behind both. | INVENTORY PENDING | Annual licence + seats |
| Token issuance & tokenization issuance · register | Issuing an instrument: contracts, transfer restriction and a register of holders. | INVENTORY PENDING | Per issuance + annual |
| Loyalty, points & rewards ledger · redemption | A points ledger with redemption, for retail, sports and travel programmes. | LIVE | Annual licence + volume |
| Distribution & community systems allowlisting · campaigns | Compliant distribution and programme operations — the era’s tooling rebuilt for a compliance-first buyer. | IN DESIGN | Annual licence |
| Agent coordination runtime integration | Integration of FlashyOS into an enterprise stack, at its published status. related party — see disclosure | LIVE | Engagement + licence |
| AI operations & data tooling evaluation · retrieval | Operationalising models: retrieval, evaluation harness, decision logging. | IN BUILD | Annual licence + seats |
| Learning & certification platform LMS | Licensed LMS for institutions training staff. Consumer certification for a general audience is a separate, distinct business and stays there. | IN BUILD | Annual licence |
- LIVE
- Serving production traffic today.
- IN BUILD
- Code exists, under active construction.
- IN DESIGN
- Designed with a working prototype, pre-build.
- NORTH STAR
- Stated direction, no code yet.
- INVENTORY PENDING
- Legacy asset; capability not yet verified against the running software (D-A).
What the build status means
The status vocabulary is the group’s own, used verbatim across Flashy Group and this practice — one asset cannot carry two different statuses on two properties. Every row states the evidence behind its status on the product page.