One Postgres cluster, three jurisdictions: how we keep payroll data isolated.

Per-tenant row-level security, region pinning, and the architectural choices behind running SG, NZ and HK payroll on a single cluster. The problem: one platform, three payroll rulebooks Running payroll across Singapore, New Zealand and Hong Kong looks simple from the outside. One company. One HR platform. One payroll close. But underneath, each market behaves differently. […]

Why we shipped AI Agents as a tenant primitive, not a feature.

The product decisions behind making AI a workspace, not a sidebar — grounded in your data, scoped by your RBAC, audited end-to-end. The feature we refused to build Most HR platforms treat AI like a chatbot. A small button in the corner. A floating assistant. A prompt box that can answer simple questions if the […]

Singapore’s Platform Workers Act: what HR systems actually need to do.

A practical guide to the new contributions and reporting requirements taking effect in 2026, and how ZingKey handles them out of the box. The shift: platform work is becoming a regulated employment-adjacent category Singapore’s Platform Workers Act changes how platform operators need to think about worker data, CPF handling, reporting and compliance. From 1 January […]

Closing month-end across SG, NZ and HK — in two days, not nine.

A walk-through of the regional payroll close pattern: pre-assembled exceptions, agent-drafted resolutions, native bank-file dispatch. The old month-end close problem For regional payroll teams, month-end is rarely one process. It is three overlapping processes, each with its own statutory rules, payroll calendar, bank-file format, approval flow and exception list. Singapore needs CPF, SDL, FWL, IR8A […]