What we deliver in PNG
Our PNG engagements typically combine local on-site visits with continuous remote operation from our Suva (Fiji) and Adelaide offices. Customers get the responsiveness of an in-country provider for fly-in work, with the depth of a 30-year engineering team behind it.
- Proxmox VE clusters at remote sites, hardened against power and connectivity interruptions, with automatic local recovery rather than dependence on cloud failover.
- Linux server engineering for telco BSS/OSS, banking back-end, government and education systems.
- ISP billing & provisioning (Tarka), tuned for PNG’s mix of fixed wireless, fibre, satellite and LTE delivery.
- USSD-based mobile services for banking, mobile top-up, voucher redemption and government messaging, which remain critical channels in PNG given smartphone penetration.
- BGP, MPLS and network analytics for service providers carrying traffic across PNG’s varied terrestrial and submarine infrastructure (PPC-1, Coral Sea Cable, NextGen).
- Disaster recovery and backup designs that work without assuming reliable WAN bandwidth.
Designed for PNG conditions
Most reference architectures from global vendors quietly assume reliable power, low-latency connectivity and same-day hardware replacement. None of those are guaranteed in PNG.
Our designs explicitly accommodate the country’s reality: dual-feed UPS with generator failover; on-site spares for critical components; local-first failure domains so a remote site can keep running without the WAN; satellite-friendly protocols and bandwidth shaping; and runbooks written for engineers who may need to walk a junior local technician through a fix over a poor phone line.
Starlink and Versa SD-WAN in PNG
Starlink has changed the economics of remote-site connectivity in PNG more than any single development since the Coral Sea Cable. Sites that used to budget thousands of US dollars per month for a fixed-throughput VSAT link now run a Starlink terminal for a fraction of the cost and several times the bandwidth. The engineering question across our recent PNG work has been how to build something production-grade on top of it.
Raw Starlink is one satellite link. It outperforms most alternatives on price-per-megabit, but the underlay still has the satellite failure modes: brief obstruction-driven dropouts, weather fade, and occasional reroutes as the constellation shifts overhead. None of that is fatal for general web traffic, but it shows up on voice calls, real-time telemetry and SaaS applications sensitive to packet loss. Treating Starlink as the only link at a business-critical site is asking for an incident.
Most of our recent PNG engagements pair Starlink with one or two complementary underlays (4G, fixed wireless, microwave or a smaller legacy VSAT) under a Versa SD-WAN policy. Versa’s path-conditioning — forward error correction, packet duplication on sensitive flows, jitter buffer — masks the rough edges of Starlink for voice and video, and the SD-WAN policy steers each application to the underlay it tolerates best. When a Starlink terminal loses sky for ninety seconds in a rainstorm, the SIP trunks have already failed over to 4G; when the 4G tower is saturated at month-end, bulk replication is moving over Starlink.
The result is a remote-site WAN that delivers MPLS-grade behaviour over commodity links, with running costs PNG customers can actually budget. We have built this stack for mining and oil-and-gas sites, provincial government offices, ISP head-ends extending coverage into new districts, and corporate branches in cities where the local fibre carrier is unreliable. The same Versa policy applies whether the site sits in Port Moresby, Lae, Mt Hagen or a drill camp in the Highlands.
Mining, oil and gas — remote-site IT
Resource-sector sites in PNG often need to run weeks of autonomous IT operation between flights. We design for that: ruggedised server platforms, on-site Proxmox + Ceph clusters that can lose any one node without service interruption, and pre-staged DR procedures that on-site staff can execute without an internet connection.
Our Linux background means we can operate at the integration layer (SCADA bridges, telemetry pipelines, on-prem analytics) without the licence-cost overhead of trying to use a Microsoft stack for everything.