Custom LLM for Sydney Enterprises

No. Yes AI is a Melbourne consultancy. No Sydney premises, no NSW staff, no dedicated account manager down the road, no quarterly workshops at an office we do not have. We are telling you on the page rather than after you have signed, because the alternative, a serviced-office address and a "local team" that is a phone number, is common enough in this industry that being straight about it is apparently a differentiator. What you get instead is the same senior people for the whole engagement, in the same time zone, on video like every other professional relationship your business already runs that way. If an engagement genuinely needs us in a room in Sydney, for a large workshop or a board presentation, we fly up and it appears as a line item you can see and decline.

Wherever you decide, because you host it. This is the part worth being precise about, since it is where AI vendors are at their vaguest. Yes AI does not own or operate a data centre, not in Sydney, not anywhere. We are not a hosting company and we are not going to imply we are one by naming facilities we have no relationship with. What we build is a deployment that runs on infrastructure you already control: your own hardware on your own premises, or your own cloud tenancy in an Australian region, under your account and your billing. The data residency answer is therefore yours to give and yours to verify, which is a considerably stronger position than taking ours on trust.

Usually, but we are not going to quote you a number we have not measured on your workload, and you should be suspicious of anyone who does. Network round-trip time to a US region is real physics and it is not small, so removing it helps. But total response time for a retrieval-based system is dominated by things that have nothing to do with geography: how many documents you retrieve, how large the model is, what hardware it runs on, and how many people are querying at once. A badly sized local deployment is slower than a well-run offshore API, and we have no interest in selling you the first while implying it beats the second. If latency genuinely matters to your use case, we measure it during the assessment against your actual queries and show you the distribution rather than a headline figure.

No, and this is the most important sentence on the page for an APRA-regulated reader. Self-hosting does not discharge a prudential obligation. It changes the shape of the problem. Under CPS 234, information assets managed by a third party are explicitly in scope, so an offshore model provider holding your data is something you must assess and defend; bringing the model inside your own boundary moves that asset into an environment you already assess, but you still have to secure it, and now you own the whole of that job. Under CPS 230, the calculus is similar: a model provider your critical operation depends on may be a material service provider, and removing the provider removes that particular assessment while leaving you accountable for the operation itself. Anyone telling you a deployment architecture makes a prudential standard go away is selling something. Your risk and compliance functions belong in this from week one, not shown the result.

Plans start at $2,999 per month, with tiers at $7,999 and $14,999 depending on model size, data volume and integration complexity. Pricing is the same regardless of which city you are in. There is no Sydney premium, and equally no Sydney discount, because the work is the same work. The full breakdown is on the pricing page rather than hidden behind a discovery call. What is genuinely variable is infrastructure: if you self-host on your own hardware, you are buying GPUs, and that number depends entirely on your concurrency and the model you land on. We would rather put that in front of you in the assessment than let it arrive as a surprise later.

For most private-sector Sydney businesses, federal law does the heavy lifting, the Privacy Act 1988 (Cth) and the Australian Privacy Principles, plus Australian Consumer Law for anything customer-facing. NSW-specific regimes bite when you touch the state sector: the Privacy and Personal Information Protection Act 1998 (NSW) covers NSW public sector agencies and can reach private businesses through contracted service arrangements. That catches more organisations than expect it. A NSW government contract can drag your AI project into a regime you had not budgeted for, and it usually arrives through the contract rather than the statute. We map which of these actually apply to your use cases rather than reciting all of them. This is general information on how these obligations typically apply, not legal advice.