Custom LLM for Perth and Western Australia

Perth runs on AWST, which puts us two hours ahead of you for most of the year and three once the eastern states go to daylight saving. It is not a detail to gloss over. It is the biggest practical difference between working with us and working with a local firm, and most eastern vendors simply do not mention it. Our approach is to take the inconvenience rather than hand it to you. Perth meetings are booked in your business hours, which means our afternoon and, for your early slots, our evening. The overlap window is spent on decisions and workshops rather than status updates that should have been written down. There is one modest compensating advantage and we will not oversell it: work you hand over at close of business Perth time has often moved by the time you open, because we started hours ago. That is real, but it is not a reason to hire us.

Sometimes, and we will say so. If your engagement needs frequent unscheduled contact, regular site attendance, or someone who can be in a room at short notice, a Perth firm has a structural advantage and no amount of good intentions from us overcomes it. Where we are the better answer is narrower and more specific: you want the model running on your own hardware, inside your own segment, with no cloud dependency, and you want the people writing the design to be the people who will build it. That work is done on screens and in your network. It does not improve because somebody caught a flight to Perth.

Yes, and this is the part of the pitch that is genuinely strong rather than merely reassuring. When a site has limited or unreliable connectivity, we deploy the model weights and the inference stack on hardware at the site itself, so queries are answered locally with no cloud round trip. Once it is deployed it does not need an internet connection to work, not a slow one, not an intermittent one, none. The same architecture is the answer where OT network segmentation means cloud connectivity is not permitted regardless of whether it is available. Hardware is sized against your actual concurrency and query volume during the assessment, and the honest constraint is cost: local inference means buying GPUs, and we would rather show you that number early than discover your appetite for it late.

No, and no. Yes AI holds no membership of the Defence Industry Security Program, no security clearances, no cleared personnel and no ITAR-compliant facility. We cannot handle classified or export-controlled technical data, and we will not take work that requires it. This matters more here than the marketing suggests, because the words in this category are deliberately slippery: a vendor can truthfully say they build "air-gapped deployments", so can we, and let you infer that this satisfies DISP. It does not. The requirement runs to the supplier, its facility and its people, not just to the network diagram. If you need a DISP member, you need a different supplier.

It can help around it, and we are firm about the boundary. Under the Work Health and Safety Act 2020 (WA), with industrial manslaughter provisions in force, safety judgements need a competent human making them, full stop. What AI legitimately does is reduce the administrative load competing with those judgements: drafting an inspection report from field notes and photos, tracking which certifications expire when, assembling incident documentation, surfacing the maintenance history relevant to today's job. The honest framing is that this gives your safety people more time to think and gives you a better paper trail. Any vendor offering you AI that makes a safety determination should be shown the door, and if we ever propose it, show us the door too.

The federal Privacy Act 1988 (Cth) and the Australian Privacy Principles are the baseline for private-sector businesses, and they govern personal information regardless of what processes it, including disclosure to an overseas model provider, which is a disclosure and needs treating as one. Self-hosting largely sidesteps that particular question by removing the provider. Australian Consumer Law applies to anything your AI says to a customer. WA-specific: the Work Health and Safety Act 2020 (WA) most shapes design in this market, particularly where automation touches safety-critical processes or the records evidencing them. The Privacy and Responsible Information Sharing Act 2024 (WA) introduces a privacy regime for the WA public sector and is being phased in, relevant if you hold WA government work or act as a contracted service provider. We map the ones that actually apply to your use cases rather than reciting the list. This is general information on how these obligations typically apply, not legal advice, and we will say plainly when a question needs your lawyers rather than us.