Start with
the problem

No. We separate the system into three independent planes from the design stage — management (the console), actual service control, and log retention. The latter two are built to keep running even while the management layer is down for updates, the licence has expired, or the building's upstream link fails.

No. We are edge-first — traffic logs and personal data stay on the client's premises, in line with PDPA, and each building keeps a fully separate database (shared-nothing).

No. Every write to a device passes a mandatory pipeline — read current state, dry-run, human approval, confirmed commit, verification — always with a rollback plan. Approval instructions are accepted from people only, as a defence against prompt injection.

Two — buy outright (the whole system lives on your premises and the licence is a cryptographically signed token with no dependency on an external server) and monthly subscription (fast to start, low upfront cost, automatic updates, multiple buildings from one console). You can switch later. Either way, tenant internet and statutory logging are never suspended regardless of licence status.

We run the new system in parallel with the old one first, test until we are confident, then cut over. We use industry-standard equipment that local technicians know well and spare parts are easy to source, so the seam is barely noticeable — and reversible if needed.

It depends on the unit count and how you currently collect internet fees. We assess for free first, and if the numbers don't justify it we will say so plainly — including when the honest answer is "you don't need to buy anything, just change how you work."