Developing an Investment Learning Platform With Courses, Labs, and a Trading Simulator
Seekho Invest connects educational content with practical market simulation through a multi-application architecture covering courses, labs, subscriptions, notifications, portfolios, orders, trades, and realtime ticks.
- Frontend
- Next.js
- Backend
- NestJS
- Realtime
- Socket.IO and Redis
- Data
- PostgreSQL and Prisma
Joining education and simulation without mixing their responsibilities
Seekho Invest combines several demanding product areas: course delivery, lesson progress, quizzes and labs, subscription access, notifications, and a simulated market with accounts, orders, trades, holdings, dividends, cash ledgers, and leaderboards.
The monorepo separates the customer frontend and API while keeping shared development scripts and continuous integration around the platform. The backend uses scheduled and realtime services for market ticks, Redis for coordination, and Prisma models for both learning and financial-simulation state.
Keeping educational progress and trading state consistent in one product
Course progress can tolerate different timing and consistency rules than orders, positions, cash movements, and realtime prices. The platform needs to join these experiences for the learner while preserving clear service boundaries and testable state transitions.
Deliver courses, lessons, quizzes, labs, and progress tracking.
Support simulated accounts, orders, trades, holdings, dividends, and leaderboards.
Control features through memberships and subscription tiers.
Keep realtime market updates testable without depending on live exchange hours.
Engineering choices that shaped the system
The architecture separates learning, commercial access, and simulation domains while connecting them through a shared identity and product experience.
Model learning and simulation as separate domains
Course, lesson, quiz, lab, and progress models remain distinct from orders, trades, holdings, cash, dividends, and portfolio snapshots.
Different state requires different boundariesUse realtime services where timing matters
Socket.IO gateways, tick services, candle aggregation, and Redis support current market state without turning every product request into polling.
Realtime should be purposefulEnforce access through feature and tier guards
Membership, subscription, and feature-access services control premium capabilities at the API layer.
Commercial rules belong in backend guardsMake market behavior reproducible in CI
The documented CI workflow runs against PostgreSQL and Redis while mocking simulator ticks so tests do not depend on live PSX data or market hours.
Determinism protects deliveryA learner journey from knowledge to controlled practice
The platform turns educational progress into guided practice without presenting simulated outcomes as real trading.
Learn
Work through structured courses, lessons, quizzes, and text or video material.
Practice
Use guided labs to apply concepts in controlled tasks.
Simulate
Place virtual orders and observe positions, cash, holdings, and market movement.
Review
Track progress, results, portfolio history, and achievements.
A multi-domain fintech learning platform
- Next.js learning and simulator frontend
- NestJS modular API
- Course, lab, and progress engine
- Realtime simulated market services
- Subscription and feature access controls
- Automated unit and integration test infrastructure
An integrated codebase for structured learning and simulated market practice
The repository demonstrates a substantial platform where learning progress, gated product access, and realtime simulation can evolve as separate domains while remaining part of one user account.
Numbered practical lab experiences present in the frontend
Socket.IO tick and market-state services
PostgreSQL and Redis test services with mocked ticks
Course, lesson, quiz, lab, and achievement workflows
Order, trade, holding, cash, dividend, and leaderboard models
CI designed to test simulator behavior without live-market dependency
What development teams can reuse from this work
- Educational state and financial-simulation state need different consistency and testing strategies.
- Realtime infrastructure should be limited to workflows that truly require current shared state.
- Feature access is safer when enforced in backend guards rather than UI visibility alone.
- Market simulation becomes testable when time and ticks can be controlled in CI.
About the project and its evidence
Does Seekho Invest place real stock-market orders?
The inspected code documents a learning platform and trading simulator. This case study does not claim brokerage execution or connection to a live exchange.
What realtime technology is present?
The backend includes Socket.IO gateways and Redis-backed simulator services for ticks, candles, orders, portfolios, and public ticker behavior.
How is the simulator tested outside market hours?
The repository documentation states that CI mocks simulator ticks and runs with PostgreSQL and Redis service containers, avoiding dependence on live PSX data or market hours.
Build learning platforms that connect content with controlled practice.
Waka connects product thinking, interface design, development, and launch support in one delivery flow.