EdifyTrade
Broker Academy OS — brokers, IBs and trading educators each run their own branded academy on shared infrastructure. Public site, student portal, owner dashboard, hosted video, webinars, and a Practice Lab that teaches risk first.
A broker or IB network can launch its own branded academy without building one. Each brand's data stays separate, partners get a commission ledger, and risk warnings are part of the design rather than added at the end.
Problem
Brokers and IB networks need a branded education arm to acquire and retain traders, but the options are a generic LMS with no broker context, or a bespoke build per brand. Neither handles the parts that actually carry risk: tenant isolation, partner commission accounting, and the regulatory boundary between teaching and advising.
Role
- Sole engineer — architecture through platform implementation and deployment
- Built the multi-tenant model, brand resolution layer, and partner commission ledger
- Built the Practice Lab simulator, video/live-events subsystem, and growth engine
Approach
- Built one multi-tenant platform where each academy is a tenant with its own domains, members, branding, and catalog
- Host-based brand resolution maps each production, staging, and legacy domain to a brand definition — no per-tenant fork
- Seven role-scoped route groups so student, tenant-admin, partner, instructor, and super-admin surfaces have separate authority boundaries rather than one dashboard with hidden buttons
- Partner and IB commissions modelled as a double-entry ledger with an outbox for reliable downstream event delivery
- Practice Lab built as a simulator with its own position and journal models — structurally incapable of reaching a live broker account
- Hosted video through Mux with per-lesson video sources, plus live streams, attendance, and chat for webinars
- Brand and color regression gates in CI, so white-label integrity is enforced by the build rather than by review discipline
Outcomes
- Live product operating as a Broker Academy OS for brokers, IBs, and trading educators
- Two brands (EdifyTrade and Obvera) run from the same codebase and the same mobile app, proving the white-label path end to end
- Tenant isolation, partner accounting, and risk disclosure are structural properties of the data model, not configuration
- Demo path validated end to end with a documented evidence pack, and a public demo academy anyone can inspect without an account
- Three deployment paths from one platform: broker-operated academy, broker-sponsored partner/IB academies, or an independent IB education portal
- Brand layer with a CI regression gate — hardcoded brand strings and off-palette colors fail the build, so white-label tenants can't drift
- Practice Lab — simulated positions and journaling, deliberately separated from any live-execution path
- Growth engine on explicit ledgers — XP, points, and PV tracked as append-only records with reward rules, badges, and streaks
- Multi-tenant by construction: Tenant, TenantDomain, TenantMember, and TenantAffiliation models resolve a branded academy per custom domain
- Partner/IB economics as first-class data: commission plans plus a double-entry ledger (accounts, events, entries) rather than derived spreadsheets
- Hosted video via Mux plus a live-events subsystem (streams, attendance, chat) for webinars and replays
- 217 test files spanning unit, integration, and compliance-gate suites
What I refused to build
These constraints are part of the engineering signal: the work stayed useful because the unsafe shortcut paths stayed out.
- R-01Live-execution paths inside the Practice Lab — simulation is a separate model boundary, not a feature flag
- R-02Hardcoded brand strings in tenant-facing UI — a CI gate fails the build instead
- R-03Shipping legal copy ahead of counsel sign-off — legal implementation stays gated until review completes
- R-04Presenting seeded demo figures as traction — preview metrics are labelled illustrative
A live tenant academy running on the platform. Every surface below is served from the shared multi-tenant codebase under the tenant's own branding — the same path a broker or IB network gets on rollout.
White-label Expo/React Native companion app — courses and resume flow, XP progression, journal, and webinars. EAS build profiles are parameterised per tenant, so each brand ships its own assets and API target from one codebase.
Stack
Working with Asadi Labs
This is the kind of system Asadi Labs builds and runs for clients: fintech systems where product direction, architecture, execution, and governance all have to line up.