A rocket gets no rehearsal. When the engines light, the vehicle is committed — every stage has to ignite in sequence, in flight, with the payload already aboard. There is no version of the mission where you land, fix the second stage, and try again.
Hold that image, because it's the exact shape of the engineering problem you face when your product is a live trading platform. Now ask yourself the question this case study answers: when every release goes straight to production, in front of tens of thousands of active traders moving real money — how do you ship fast without breaking trust?
Here's how we did it, stage by stage.
The Client
GenesisFX is a licensed, regulated FX and crypto trading broker — copy trading through TradeLocker, multi-chain crypto deposits, and a partner/affiliate program, serving an active and fast-growing trader base. Rocket Now serves as GenesisFX's embedded platform development partner: a continuous, multi-month engagement across their entire product surface, with Claude Code as the primary engineering environment, working alongside their team on everything from the trading core to custody to community.
Embedded is the operative word. When a platform is live and compounding, a fixed-scope vendor hands you a deliverable and leaves; an embedded partner stays in the cockpit. GenesisFX needed the second kind.
The Challenge: Passengers Already Aboard
Most software teams get a luxury they never notice: a staging environment where mistakes are free. GenesisFX had no such luxury. The platform was already flying — real deposits, real withdrawals, real copy-trades syncing against a live broker — and growing by 1,000–2,000 new users every week while we worked.
Under those circumstances, the engineering doctrine writes itself: when there's no net, then correctness isn't a phase of the project — it is the project. Reliability and security had to be built into every release the way a rocket's staging is built into the vehicle: decided before ignition, proven in flight.
The Ascent: Eight Stages, One Vehicle
Stage 0–1 — Foundation and stabilization. The first burn is always about control authority. We hardened the trading and transfer pipeline under live load: copy-trading latency and sync fixes to close the gap between signal and execution, transfer reliability between internal wallets and trading accounts, and pre-flight gates — a "storm mode" that holds trades correct even when the upstream broker itself has a bad day. When the market gets violent, then the platform gets conservative, automatically.
Stage 2 — The dealing desk gets a cockpit. Operations staff had been working directly against the database — hand-flying the vehicle. We built a dedicated dealing-desk portal: deposit and withdrawal approval workflows, KYC review tooling, commission oversight. When an operator needs to act, then there's an instrument for it — full audit trail, zero raw database work.
Stage 3 — TreasurX: purpose-built custody. Crypto custody is where trading platforms most often improvise, and improvisation is how custody fails. TreasurX replaced ad hoc wallet handling with purpose-built rails: multi-chain deposit detection and automated hot-to-cold sweeps across BTC, ETH, BASE, SOL, TRON, USDC, and USDT, with security hardening applied in deliberate tiers — withdrawal allowlists, time-locked webhooks, IP egress filtering, payout limits with auto-halt, custody audit logging, and TOTP MFA on admin routes. Each tier is a lock that assumes the one before it might someday fail.
Stage 4 — The proactive audit. This is the stage we're proudest of, because it inverts the industry's default posture. When most platforms wait for incidents to surface one angry ticket at a time, we went looking first: a Claude-assisted audit across the full production database — 32,000+ user profiles, 119,000+ deposits, 140,000+ internal transfers, 1.2 million+ login records — hunting fraud patterns and systemic engineering bugs before either could become a customer-facing incident. The audit surfaced coordinated abuse patterns across accounts, commissions, and identity verification, plus the quiet correctness bugs (race conditions, missing idempotency, audit-trail gaps) that only reveal themselves at scale — and produced a prioritized remediation plan executed alongside GenesisFX's compliance team. When you audit before the alarm, then the alarm never rings.
Stage 5 — A charting engine of their own. We built a custom real-time charting engine — candlesticks, EMA, Bollinger, Ichimoku, ATR, drawing tools, position overlays, a branded Genesis theme — cutting reliance on third-party embeds. v1.0 shipped and was iterated the same month on live trader feedback, because the traders were right there.
Stage 6 — Partner and growth infrastructure. The affiliate engine that funds growth got the same correctness treatment as the trading core: commission calculation with idempotency guarantees, audit reporting, partner dashboards, and lifecycle segmentation so marketing speaks to each trader where they actually are in the journey.
Stage 7 — GenStream, launching now. A live-streaming and community layer — trader broadcasts, chat, trade and tip notifications — extending GenesisFX from a place you trade into a place you belong.
The Results
- Active users grew from ~44,000 to ~57,000 during the engagement's intensive phase — with ~5,000 daily actives and 1,000–2,000 new users joining weekly
- Every feature field-tested immediately against a live, scaling production user base — real-world validation on each release
- A continuous embedded partnership spanning the trading platform, admin console, custody system, charting engine, partner API, security program, and streaming infrastructure — one team, one vehicle, every stage
"[Quote from GenesisFX leadership — pending their review.]" — [Name, Title], GenesisFX
Why It Worked: One Right Step, Compounded
Here's the principle underneath all eight stages, and it's the same principle we bring to every Rocket Now engagement: a single step in the right direction is worth exponentially more than many steps in the wrong one. Each phase collapsed the space of possibilities into one committed, correct burn — stabilize before you build, build the cockpit before you scale the custody, audit before the incident — and each burn made the next one cheaper. That's what an embedded partner with AI-native tooling actually buys you: when Claude Code carries the implementation weight, then your senior judgment gets spent where it compounds — on sequencing, correctness, and trust.
When your platform is already flying — passengers aboard, no rehearsal, growth compounding weekly — that's precisely when you need a partner who ships like every release is a stage ignition. That's the flight we flew with GenesisFX. The vehicle is still climbing.
Building something that's already live? That's our favorite kind of problem. → RocketNow.com
Editor's note — before publishing:
- GenesisFX compliance/board sign-off (regulated brokers often restrict public marketing claims — confirm a public case study is approved at all)
- Verify growth figures and the "licensed and regulated" phrasing with their compliance team
- Replace the placeholder quote with an attributable one from GenesisFX leadership
- Fraud-audit details are intentionally aggregate and non-identifying; keep them that way in any edits