Building WorthMap: A Cloud-Native Wealth-Tracking Platform on Google Cloud

This article walks through how we architected WorthMap on Google Cloud, the engineering decisions behind it, and why a single small team was able to deliver a globally-available, multi-platform product. It is also a representative example of the custom software development and cloud engineering work we deliver for clients.

The Problem We Set Out to Solve

Most people hold their wealth across many disconnected places: brokerage accounts, bank balances, retirement funds, property, bonds, dividends and recurring expenses. There was no single, trustworthy place to see the whole picture update in real time and across every device. We wanted a product that felt instant, kept a complete and auditable history of every transaction, and worked identically on web, iOS and Android from one codebase.

Architecture: A Google Cloud-Native Platform

We built WorthMap as a Google Cloud-native application from day one. Choosing a managed, serverless-leaning stack let a lean team focus on product engineering instead of infrastructure operations. The core components are:

• Managed, consistent data: WorthMap's system of record runs on Google Cloud (GCP) infrastructure, giving us a horizontally-scalable, strongly-consistent database with high availability. Financial data demands correctness — it lets us keep strict transactional integrity over a full FIFO transaction history without sacrificing scale.
• Cloud-native API on Google Cloud: Our customer API is a stateless, containerised service on Google Cloud (GCP) infrastructure that scales with demand. It enforces concurrency-controlled, single-use snapshot reads so the database is never a bottleneck under fan-out load.
• Managed authentication: User identity, sign-in, token verification and password flows are handled through Google Cloud's managed authentication, integrated as middleware on every protected request — secure authentication without us building and maintaining a credential store.
• Scheduled data pipelines: Nightly jobs enrich the platform with market and instrument data, keeping valuations and analytics current without impacting the interactive request path.

One Codebase, Three Platforms

This shared-codebase approach is one of the biggest force-multipliers in the project: a feature is written once and validated everywhere, which is how a small team keeps three platforms at feature parity.

Why It Matters for the Work We Do

WorthMap is proof that HKMSP operates as a genuine software engineering shop, not just an advisory one. The same disciplines we applied to our own product — Google Cloud architecture, scalable database design, secure authentication, CI-driven cross-platform delivery and ongoing operations — are exactly what we bring to client engagements in cloud, DevOps and custom software development.