AI development company for Adelaide defence, space, wine industry, mining services & healthcare.

We do not operate an Adelaide office. Aiinfox runs from our Mohali, India HQ and a Frisco, TX office. For Adelaide clients, we deliver with a clean four-hour afternoon ACST/ACDT overlap (9:30am IST is 1pm ACST winter / 2pm ACDT summer) and the same senior engineers run twice-weekly demos in Adelaide business hours. For on-site engagements at Lot Fourteen, Osborne, Edinburgh Parks, the new Royal Adelaide Hospital, or the Barossa / McLaren Vale wine-industry sites (kickoff, milestone reviews, security walk-throughs), we travel to Adelaide on a scheduled cadence rather than maintaining a sub-scale local presence.

No — and we are explicit about that on the first call rather than after the contract is signed. The Information Security Registered Assessors Programme (IRAP) is the Australian Government's cyber-security assessment framework, and IRAP-assessment of a vendor's own platform is the standard control for Australian-Government and PROTECTED-classified cloud-hosted services. Aiinfox is a foreign engineering provider, not an Australian-hosted SaaS, so IRAP assessment of our own platform is not the relevant control structure. What we do for PROTECTED-classified Adelaide engagements is structure the work to fit inside an existing IRAP-assessed cloud boundary (typically AWS Australia or Azure Australia at the appropriate classification, with the IRAP assessment held by the cloud provider and your delivery prime); our engineers connect over a privileged-access path that your security team controls. If your engagement absolutely requires our own IRAP assessment, we will recommend an IRAP-assessed Australian prime rather than pretending otherwise.

Strong, and we won't get the half-hour offset wrong like Sydney consultancies sometimes do. South Australia observes ACST (UTC+9:30) in winter and ACDT (UTC+10:30) in summer — half-an-hour offset from Eastern-states Sydney and Melbourne. From Mohali IST (UTC+5:30), our 9:30am IST is your 1pm ACST winter / 2pm ACDT summer, giving a clean four-hour afternoon overlap with the Adelaide working day every weekday. Daily standups, twice-weekly demos, and most ad-hoc problem-solving sessions land inside that window. Written async updates land before your morning. For engagements needing morning Adelaide 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) — relevant for Adelaide wine-export and mining operators with head offices in the UK, the US, or Singapore — we 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.

Carefully and explicitly. The Defence Trade Controls Act 2012 controls the supply, brokering, and publication of certain defence-related and dual-use goods, software, and technology including specific cryptography, defence-related software, and dual-use technology categories. For Adelaide defence-electronics and naval-supply-chain engagements where DTCA-controlled technical data is in scope, we treat technical-data handling as a load-bearing constraint from day one. Self-hosted Llama 3 on vLLM inside the customer's Australian VPC is the default — no controlled technical data ever transits a managed-inference API endpoint. The engagement scope is structured so controlled material is clearly bounded, audit logs capture every prompt and tool call, and we will tell you on the first call if the scope requires Australian-national-only delivery (outside what Aiinfox can offer alone — we would recommend an Australian delivery prime).

Your call on the region. AWS ap-southeast-2 (Sydney) is the broadest-catalogue AU primary region and the default for most Adelaide 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 — Australia Central is relevant for PROTECTED-classified workloads. GCP australia-southeast1 (Sydney) is the standard GCP option. For inference, we route Claude or GPT-4o to an Australian region depending on your DPA, or we self-host Llama 3 on vLLM inside your Sydney or Melbourne VPC for zero third-party inference.

Yes. For SA Health-adjacent healthtech serving the new Royal Adelaide Hospital, the Women's and Children's Hospital, Flinders Medical Centre, and the broader SA Local Health Networks, we layer the South Australian information-sharing guidelines and the Code of Fair Information Practice (administered by the SA Privacy Committee) onto the federal Privacy Act 1988 baseline. 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 Local Health Network.

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 SA Health-aligned compliance work or DTCA-aware defence-adjacent 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. Adelaide 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).