Đoàn Thành Đạt

An automated futures trading platform. Strategies are written, backtested, rented and executed inside one product, on nodes I operate.

• A signal hub evaluates strategies on five-minute cycles; a position monitor tracks every open position over dual WebSocket and REST and manages its stop, target and trailing exit.
• Strategies and backtesting ship as a zone behind the app itself — a user rents a strategy and never meets a marketplace.
• One httpOnly cookie carries identity across every surface, with subscriptions and wallets in the same provider.
• An MCP server exposes the account — trades, positions, quota, earnings — so it is readable from an AI client as well as a browser.

Market intelligence for Vietnamese traders. Not a feed to read — a place to check, ten times a day, and get the picture already assembled.

• Category-first architecture: every covered category — gold, FX, rates, crypto, macro — is the spine the crawler, the analysis layer, the API, the CMS and the app all organise around.
• I own the backoffice editors publish through, and the data-layer contract underneath it.
• Ingestion runs crawler and social sources through an AI filter into enrichment; every number that reaches a reader carries its source and its timestamp.
• It sells as a subscription, never ads and never broker commission — which makes neutrality and the revenue model the same decision.

A Vietnamese game publisher. I lead the frontend across every surface it ships — portals, portal games, the partner channel and the SDK that binds them.

• One Next.js app serves every game portal, selected by config, one deployment per title. Launching a game is deleting its maintenance flag.
• Kiếm Khách and Thương Lam are live on their own domains; the next title queues behind the same pipeline.
• The CPS partner portal talks to the affiliate API through its own server-side layer, and its public docs are an opt-in allowlist — an internal host cannot leak into one by accident.
• A publisher SDK across iOS, Android, Unity and Web, with its own documentation site and CMS behind it.