NVX Launchpad & Exchange — Web3 that has to satisfy a regulator

Real-world assets, real-world rules

A real-world-asset launchpad is where a tokenised asset meets people who want to buy into it. That makes it a financial product first and a Web3 product second — and in Indonesia, one supervised by an actual regulator. The engineering consequence is that "move fast" is bounded by requirements that don't negotiate.

In this domain, compliance isn't a checkbox bolted on at the end. It's a constraint on the data model, the audit trail, and who is allowed to do what.

The launchpad: web, mobile, and the server behind them

I built the user-facing launchpad frontend for both web and mobile, and the Node.js backend powering it.

Web

The RWA launchpad runs on React with Express and Sequelize over PostgreSQL, with AWS integration and state handled through Redux and Zustand. It shipped with an admin CMS alongside it.

Mobile

The mobile client is React Native on Expo, bringing the launchpad to the phone. Serving web and mobile from the same platform is the part that rewards getting the API boundary right early.

The admin system nobody sees

I built the internal admin management system from the ground up — React frontend, Node.js backend. Internal tools tend to be treated as second-class, but on a regulated platform the admin system is the control surface: it's how operations staff act on the platform at all.

Keeping the exchange alive

Alongside new construction, I developed, maintained, debugged and improved the NVX Exchange platform — an older codebase in PHP and Vue.js — with platform stability as the explicit goal.

Two products, two eras of technology, one team. Working across both is a useful corrective to greenfield instincts: an exchange in production has users with money in it, so the bar for a change is "will this hold" rather than "is this elegant".

Compliance, security, and documentation

• Indonesian regulatory integration — I integrated regulatory requirements into the NVX system so the platform could operate compliantly in its market.
• ISO 27001:2022 — I contributed to the company's successful implementation of the information-security standard, focused on cybersecurity. That means engineering practice being examined against an external standard, not just a policy document being filed.
• API documentation — I developed and managed the platform's API documentation in Swagger UI (Express.js), Markdown and PDF, so that integrators and internal teams worked from something current.

How the work ran

Delivery was agile: sprints tracked in Jira, collaboration with QA through user acceptance testing, and implementation against UI/UX specifications in Figma for both web and mobile. Working to a designer's spec across two platforms is its own discipline — the design is the contract, and mobile is where it usually needs the most translation.

React · React Native · Expo · Node.js · Express · Sequelize · PostgreSQL · AWS · PHP · Vue · Swagger · ISO 27001:2022