Platform / Architecture
A layered architecture with explicit responsibility boundaries
GIGX is deliberately structured so that every layer has one owner. Investor interfaces belong to the broker partner, infrastructure and connectivity belong to GIGX, and execution belongs to the market.
Layered view
| Layer | Responsibility | Owner |
|---|---|---|
| Investor interface | Mobile app, web platform, white-label portal | Broker partner |
| API gateway & integration | Authentication, rate limiting, versioned contracts | GIGX |
| Core services | Onboarding, orders, portfolio ledger, risk, suitability, compliance events | GIGX |
| Market connectivity | Order routing, execution reporting, market-data ingestion | GIGX |
| Market infrastructure | NGX equities, NGX derivatives, payment rails, market-data providers, CSD | External |
Engineering principles
Service interfaces first
Market data, orders, portfolio, compliance, notifications, identity and payments are each defined as an interface with swappable providers.
Event-sourced audit
Every sensitive action emits a structured event with actor, role, resource and before/after state.
Relational core
Investors, positions, orders, executions, limits and compliance records are modelled relationally, not as opaque documents.
Server-side authorisation
Permissions are enforced in server code and database policies. Hidden interface elements are never the control.
Deterministic order lifecycle
Orders move through explicit states, and every transition is recorded with a timestamp and actor.
Replaceable demo providers
The demonstration environment uses simulated providers that can be swapped for live feeds without touching product code.
Demonstration environment
This platform runs against a clearly labelled demo environment. Prices and market activity are simulated for demonstration and are never presented as live exchange data.
Speak with the GIGX team
We work with licensed brokers, investment firms and market infrastructure operators.