AI development company for Brisbane resources, agritech, QLD Health-adjacent & defence-adjacent.

We do not operate a Brisbane office. Aiinfox runs from our Mohali, India HQ and a Frisco, TX office. For Brisbane clients, we deliver with a clean native four-hour afternoon AEST overlap (Queensland does not observe daylight saving, so the overlap is the same year-round) and the same senior engineers run twice-weekly demos in Brisbane business hours. For on-site engagements at Eagle Street, the CBD, Fortitude Valley, or South Brisbane offices (kickoff, milestone reviews, security walk-throughs), we travel to Brisbane on a scheduled cadence rather than maintaining a sub-scale local team. The senior engineer on your kickoff call is the senior engineer through launch — no swap-outs to a local junior pool.

Strong, and arguably the cleanest overlap in our Australian portfolio. Indian Standard Time is UTC+5:30, Brisbane AEST is UTC+10 year-round (Queensland does not observe daylight saving), so our 9:30am IST is your 2pm AEST — a clean four-hour afternoon overlap with the Brisbane working day every weekday, same in summer and winter. No twice-yearly DST shift to manage, no Sydney-Melbourne calendar drift in October and April. Daily standups and twice-weekly demos run inside your business hours. Written async updates land before your morning. For engagements needing morning Brisbane coverage as well, we extend to early-IST starts on a planned cadence.

Yes. Our engagement defaults are aligned with the Privacy Act 1988, the 13 Australian Privacy Principles, and the Notifiable Data Breaches scheme. DPAs are signed before any personal information is shared, and we run a Privacy Impact Assessment for engagements processing personal information at scale or involving sensitive information. For APP 8 (cross-border disclosure of personal information) — which matters disproportionately for Brisbane resources operators with head-offices in Singapore, the UK, or the US — we explicitly map the data flow and the safeguards in place; your DPA spells out exactly where personal information is processed and which third-party endpoints (if any) receive it. For NDB obligations, the incident response playbook includes the 30-day assessment window and the OAIC notification path.

Your call on the region. AWS ap-southeast-2 (Sydney) is the broadest-catalogue AU primary region and the default for most Brisbane clients without an in-state residency requirement. AWS ap-southeast-4 (Melbourne) is the alternative for clients preferring a Victorian region. Azure Australia East (Sydney) and Azure Australia Central (Canberra) are supported for federal-adjacent work. GCP australia-southeast1 (Sydney) is the standard GCP option. For inference, we route Claude or GPT-4o to an Australian or US region depending on your DPA, or we self-host Llama 3 on vLLM inside your Sydney or Melbourne VPC for zero third-party inference. No Australian personal information silently crosses the border unless your DPA explicitly permits it.

Yes. For QLD Health-adjacent healthtech operators serving the Royal Brisbane and Women's Hospital, the Princess Alexandra, and the broader QLD Hospital and Health Services network, we layer the Queensland Health Information Standard (IS18 and the broader QLD Government information security baseline) onto the federal Privacy Act 1988 baseline. The Queensland Hospital and Health Boards Act information-sharing obligations are mapped into the engagement scope. Deployments default to AWS Sydney or Melbourne inside customer-controlled Australian clouds; every PHI touchpoint is audit-logged with input, output, prompt version, and operator identity for IG officer review at the contracting Hospital and Health Service.

Aiinfox itself does not currently hold an IRAP assessment — we are a foreign engineering provider, not an Australian-hosted SaaS, so IRAP assessment of our own platform is not the relevant control. What we do for Brisbane defence-adjacent supply-chain operators or PROTECTED-classified Queensland work is structure the engagement to fit inside an existing IRAP-assessed cloud boundary (typically AWS Australia or Azure Australia with the appropriate classification). The deployment runs inside the customer's IRAP-assessed environment; our engineers connect over a privileged-access path that the customer's security team controls. Self-hosted Llama 3 on vLLM is supported for engagements that cannot egress to managed inference APIs. If your engagement requires our own IRAP assessment, we will say so on the first call rather than pretending otherwise.

Most v1 engagements at Aiinfox land between AUD 40,000 and AUD 180,000 fixed-price for a focused build — an AI agent, a RAG system, a voice pipeline, or a bespoke ML model. Larger multi-quarter engagements with fine-tuning, custom evals, and APRA-aware or QLD Health IS18-aligned compliance work typically reach AUD 220,000 to AUD 400,000. Pilots are usually AUD 15,000 to AUD 28,000 with acceptance criteria written into scope. Brisbane clients invoice in AUD via bank transfer or USD by preference. We are a registered Indian entity invoicing as a foreign corporation — GST does not apply on B2B services supplied from India to Australia (general rule; your tax adviser should confirm).

Yes — takeover audits are routine. Step one is reading the code, the data pipelines, the eval results (if any exist), the prompts, and the cost telemetry. Step two is shipping the smallest valuable change to prove we understand the system in a way the previous vendor did not. Step three is the longer-term plan — incremental stabilisation, a parallel rebuild, or shutting it down and starting over. Most Australian takeovers we have seen did not need a full rewrite; they needed evals, guardrails, observability, and a senior engineer who stayed on the build past the discovery phase. We will be honest on the first call about which is the right move.