The software, infrastructure and services behind my day-to-day work and this site, each with the reason it earned its place.
By Matthews WongUpdated
My main way of writing software: an agentic coding tool in the terminal, with project skills, hooks and MCP servers that know this repository's rules.
How AI tools reach real systems. At work I build the MCP Console and Gateway that every MCP server runs through.
The shell on my Mac, where nearly all of the work starts.
Everything is versioned, including the infrastructure config and the content of this site.
The default for both front end and back end, so types cross the network boundary instead of stopping at it.
This site and most web apps I ship: App Router, server components and static rendering by default.
The UI layer for the web apps and the ERP front ends.
Styling that lives next to the markup, with the design tokens in CSS variables.
The back end for ERP work: modules for accounts payable and receivable, approvals and invoicing.
The database under the ERP systems, where row locks, constraints and an audit trail matter more than raw speed.
Data work and scraping, as in the Observer KPU election information project.
Every service ships as an image, including this site.
Build, push to the GitHub Container Registry and deploy over SSH on every push to main.
DNS and the edge in front of this site, caching static assets while HTML stays fresh.
The reverse proxy on the VPS, terminating TLS and redirecting to the canonical host.
The VPS this site runs on.
An inexpensive Indonesian VPS I use for side projects; I wrote a review of it.
Metrics, logs and alerting for every production server I run, in one pane.
Load testing; my thesis used it to benchmark a production logistics platform.
Every page in English and Indonesian, with the locale always in the URL.
The films on the home, about and projects pages are React compositions rendered to video.
The Archipelago, the walkable 3D version of this portfolio at /play.
Captures the project screenshots and renders the profile deck.
The model API behind the site's chat assistant.
Delivers the contact form's email from the server.