AI development company for Perth mining, resources, agritech, energy & fintech.

We do not operate a Perth office. Aiinfox runs from our Mohali, India HQ and a Frisco, TX office. For Perth clients, we deliver with the strongest AWST overlap of any of our Australian engagements — 2.5 hours' difference between IST and AWST, year-round, with no daylight saving complication. The same senior engineers run twice-weekly demos in Perth business hours. For on-site engagements at St Georges Terrace, the Perth CBD, West Perth, Subiaco, or resources operations offices (kickoff, milestone reviews, security walk-throughs), we travel to Perth 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.

The strongest overlap in our Australian portfolio, structurally and year-round. Indian Standard Time is UTC+5:30. Australian Western Standard Time (AWST) is UTC+8 — and Perth does not observe daylight saving, so AWST stays UTC+8 every day of the year. That makes the IST-to-Perth gap exactly 2.5 hours — the smallest of any major Australian city, and dramatically smaller than Sydney or Melbourne in their summer (when AEDT extends to UTC+11 and the gap stretches to 5.5 hours). Our 11:30am IST is your 2pm AWST, our 5:30pm IST is your 8pm AWST — five to six hours of clean native daily overlap with the Perth working day. Daily standups and twice-weekly demos run inside your business hours. Written async updates land before your morning.

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. APP 8 (cross-border disclosure of personal information) matters disproportionately for Perth resources operators with head-offices in Singapore, London, Houston, or elsewhere — we explicitly map the data flow and the safeguards in place, and 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 Perth clients without an in-state residency requirement — full Bedrock model catalogue including Anthropic Claude, the most mature AWS service coverage in Australia. 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; for resources operators with no-egress data-sharing agreements, we self-host Llama 3 on vLLM inside your Australian VPC for zero third-party inference.

Yes. For BHP, Rio Tinto Iron Ore, Fortescue, Woodside-adjacent operators and the broader Perth METS cluster, we structure engagements around the data-sharing-agreement constraints typical in the sector — most customer contracts forbid egress of operational telemetry, drill-hole and ore-body data, well-log information, geophysical surveys, and proprietary processing data to third-party endpoints. Self-hosted Llama 3 on vLLM inside the customer VPC is the default for that pattern, with AWS ap-southeast-2 (Sydney) as the runtime region. We have shipped document intelligence for permits, environmental approvals, and compliance filings, computer-vision QA for plant inspections, and predictive maintenance ML across the broader resources sector. For cross-border data flows into Singapore, London, or Houston head-offices, we map APP 8 and the relevant data-sharing safeguards explicitly in your DPA.

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 Perth defence-adjacent supply-chain operators or PROTECTED-classified WA 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. 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 resources-sector compliance work typically reach AUD 220,000 to AUD 420,000 — the resources-sector self-hosted-inference and custom-eval work tends to be at the higher end of that range. Pilots are usually AUD 15,000 to AUD 28,000 with acceptance criteria written into scope. Perth 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.