The Singapore replica is a synced container, and its URL never moved

Head office writes to one container in Frankfurt: the reporting app, its SQLite file under /hoody/databases/, the exec scripts that read it. Branch offices in Singapore, São Paulo, and Denver read a copy on a box in their own region. Every fifteen minutes a cron entry POSTs /api/v1/containers/{id}/sync to each copy. Only the changed blocks cross the network. The copy keeps its container ID and its URLs, so the dashboard bookmark in Singapore has pointed at the same hostname since the day it was copied.

Writes go to Frankfurt. Reads stay local. Nobody wrote replication logic; the replica isn't a database feature, it's a container feature.

A database service prices read replicas per region, per replica, on top of the primary. Here, three regions are three flat-rate servers you already rent, and the replica is one more container on each.