Routing & resilience
Multi-site routing with dual-WAN failover, so a single ISP outage does not stop a branch from trading.
Network engineering
We design multi-site networks, secure them, and then stay on to run them. Four are in operation now, across property, distribution, hospitality and logistics.
Capability
Multi-site routing with dual-WAN failover, so a single ISP outage does not stop a branch from trading.
Separate networks for management, servers, staff, guests and devices — with only the traffic that has a reason to cross allowed to.
Encrypted tunnels between sites and for engineers, so support does not mean travel and does not mean opening the network to the internet.
Default credentials removed, unused services closed, management restricted to a network users cannot reach.
Device configurations and server data backed up on a schedule — and restored on a schedule, because that is the only way to know they work.
Alerting on the things that precede an outage — links, capacity, service health — with a documented change record.
In operation
Named where the client agreed to it. What is never published — for any of them — is topology, addressing or equipment inventory. That is a gift to whoever is scanning them, and no portfolio is worth it.
Commercial property
& retail group
A single estate carrying tenant, operations and management traffic. Each is segmented from the others, the core is redundant, and access between departments is granted by rule rather than by default.
Hap Suy Hardware Co.
Trading & distribution · 4 branches
Every branch runs two internet services with automatic failover, and all four are joined by encrypted site-to-site links carrying warehouse and ERP traffic to the central systems.
Hotel group
Guest wireless is a genuinely separate network from property operations — front desk, back office and building systems are not reachable from a guest device, and the administrative path never crosses into guest space.
Lazada
E-commerce & logistics
A high-throughput fulfilment operation where an hour offline is counted in undelivered orders. Redundant paths for order traffic, with operational and office networks kept apart.
Automation
Every manual routine is a future incident report. These are the two kinds we replace.
Work that happens in the chat app your team already has open, instead of a dashboard nobody logs into.
The jobs that must run whether or not anyone remembers them — and must prove they ran.
Credentials
Formal certification in the platforms we deploy — so the design decisions on your network were learned somewhere other than your network.
Enterprise routing, switching and campus network design.
Routing, firewalling, VPN and traffic management on RouterOS.
Vendor-neutral networking and systems fundamentals.
Hardening, segmentation, monitoring and incident response.
Assessment before proposal
Most networks do not need replacing. Knowing which parts do is the difference between a fix and a rebuild.