Sovereign remote desktop, Sydney by default.
Silux Connect for Australia and New Zealand: Sydney-pinned data, AUD pricing, Australian-hours support. Privacy Act 1988 and the Australian Privacy Principles mapped into the contract. IRAP assessment on the roadmap. Built for ANZ MSPs, healthcare and government.
ap-southeast-2 (Sydney) by default. Melbourne secondary. Customer- pinned. Data and audit logs never leave Australia unless you opt in.
Invoiced in AUD with GST handled correctly. Annual purchase orders accepted. No surprise FX charges from a USD parent vendor.
Sydney-based support team. 09:00 to 18:00 AEST/AEDT. Overnight on-call. Critical-incident phone callback in 15 minutes 24/7.
Built for ANZ buyers
The ANZ remote-support market is small enough that vendor support tends to feel like an afterthought. North American vendors run Sydney out of a US billing entity, with support tickets routed to Pacific Time queues and quarterly business reviews held at hours that work for them. Silux Connect runs Sydney as a first-class region with an Australian support roster, AUD billing, and contract terms that name the Office of the Australian Information Commissioner (OAIC) explicitly. NZ customers are served from the same region with the Privacy Act 2020 referenced in the DPA.
For Australian MSPs, the procurement story is the unified product and the predictable cost. One licence covers remote desktop, RMM, MDM, scripting and AI ticket triage. A 5-technician shop typically saves $9,000-$14,000 AUD a year versus the ConnectWise stack or the TeamViewer Corporate tier. Per-tenant white-label means your clients see your brand. PSA hooks for ConnectWise Manage, Autotask, HaloPSA and Atera are included.
For Australian healthcare under the My Health Records Act and the Privacy Act, the architecture is the headline. Health data is encrypted end-to-end. Optional session recordings are saved on the technician's own computer and never leave your organisation. Notifiable Data Breaches Scheme handling is documented in our incident-response runbook with the 30-day OAIC notification window built in.
For state and federal government, the roadmap targets IRAP assessment at OFFICIAL: Sensitive in late 2026, with PROTECTED on a longer horizon if customer demand justifies it. In the meantime, we can deploy on-premises into your IRAP-assessed environment, with the agent code open-source under AGPL-3.0 and the relay shipped as a signed Helm chart you control.
Privacy Act 1988 and APPs mapped. Notifiable Data Breaches Scheme handling documented. IRAP OFFICIAL: Sensitive assessment on roadmap for late 2026. NZ Privacy Act 2020 referenced. ISO 27001 stage 1 Q4 2026.
Trust CenterMulti-tenant white-label so your clients see your brand. Per- technician AUD pricing. PSA hooks for ConnectWise Manage, Autotask, HaloPSA, Atera and N-able. Concurrency that scales with your roster, not your endpoint count.
For MSPsFrequently asked
By default Australian tenants are pinned to AWS ap-southeast-2 (Sydney) with ap-southeast-4 (Melbourne) available as a secondary. Data is not replicated outside Australia unless you explicitly opt in.
Yes. Our Privacy Policy and DPA reference the Privacy Act 1988 and the Australian Privacy Principles, and we honour Notifiable Data Breaches Scheme timelines. The OAIC is named as the relevant supervisory authority for AU customers.
Our roadmap targets IRAP assessment at the OFFICIAL: Sensitive level for late 2026. We currently deploy on AWS Sydney infrastructure that is itself IRAP-assessed at the PROTECTED level, which covers many state and local government use cases via the responsibility-shared model.
Yes. Support is delivered 09:00 to 18:00 AEST/AEDT by an Australia-based team, with on-call cover overnight. Critical incidents get a phone call from a human within 15 minutes regardless of time zone.
New Zealand customers can pin to Sydney by default or run on-premises. The Privacy Act 2020 is referenced in our DPA and we honour the Office of the Privacy Commissioner timelines. NZ-resident infrastructure is on the 2027 roadmap.