Custom LLM for Adelaide and South Australia
Most pages selling AI into Adelaide open with the defence primes and the space sector. Here is ours instead: Yes AI is a small Melbourne consultancy, we are not a DISP member, we hold no security clearances, and we cannot touch classified or export-controlled material. What we do build is self-hosted LLM deployment over unclassified, commercially sensitive information, which is where almost all of the defence supply chain's actual paperwork lives.
Read This Before You Read Anything Else
The defence supply chain is the most pitched and least honestly pitched market in South Australia. So the disclosures go at the top of the page rather than in a capability statement you have to extract three meetings in.
We Are Not a DISP Member
Yes AI holds no membership of the Defence Industry Security Program, no security clearances, no cleared personnel, no IRAP assessment, no ITAR-compliant facility and no position on a government panel. We cannot handle classified, PROTECTED or export-controlled material. If your requirement genuinely needs any of that, we are not your supplier, and you should learn that from a web page rather than from us in month three.
We Do Not Have an Adelaide Office
No Adelaide premises, no SA staff, no local account manager, no "local engagement capability". We are a Melbourne consultancy that delivers remotely. Adelaide is half an hour behind us, which makes this the easiest interstate engagement in the country to run, but it is still remote, and calling it something else would be the first lie in a relationship that depends on us not telling you any.
What Is Left Is Still Most of the Work
Strip out everything classified and everything export-controlled, and what remains inside a defence supply-chain business is enormous and thoroughly unglamorous: tenders, quality records, non-conformance histories, work instructions, supplier onboarding, certification tracking, audit evidence. None of it touches controlled technical data. All of it is quietly consuming your senior people.
What We Can Actually Build for Adelaide
Self-hosted LLM deployment over unclassified, commercially sensitive information. The model runs on infrastructure you control, inside your security boundary, governed by your controls and your own cleared staff, not ours, because we do not have any.
Tender and Bid Documentation
Defence and government tendering produces a body of writing that largely repeats itself, and the cost is measured in the senior people who disappear for a fortnight to assemble it.
- Retrieval across previous bids, capability statements and past performance
- Draft responses grounded in what your business has actually said before
- Consistency checking across a long response written by many hands
- Compliance-matrix tracking against the tender schedule
Supplier and Subcontractor Quality Records
Quality management in the supply chain is a documentation problem long before it is an engineering one. The record exists; nobody can find the right one at the right moment.
- Non-conformance and corrective action history made searchable
- Supplier approval and onboarding documentation retrieval
- Audit evidence packs assembled from records scattered across systems
- Certification and expiry tracking across a supplier base
Procedures and Work Instructions
Unclassified process knowledge, how this business does things, written across hundreds of documents and several generations of staff who have since left.
- Plain-language querying of procedures and work instructions
- Onboarding acceleration for new staff and contractors
- Change control: finding every document a process change touches
- Knowledge capture before experienced people retire or move on
Corporate and Back-Office Functions
The functions that exist in every business regardless of what it manufactures, and where the return is easiest to measure honestly.
- HR policy, enterprise agreement and procedure enquiries
- Finance and procurement process documentation
- WHS documentation and incident-record assembly for human review
- Contract and purchase-order term retrieval
Health and Medical Research Administration
Adelaide research institutions run on ethics approvals that define exactly what may happen to participant data. That is a constraint a public AI platform cannot satisfy and a self-hosted deployment can.
- Deployment inside your own infrastructure, within the ethics-approved boundary
- Protocol, HREC submission and grant documentation drafting support
- Research knowledge retrieval across a large document library
- Data-handling documentation prepared for your privacy officer and HREC
Wine, Food and Export Administration
South Australian wine and food exporters carry a documentation load that multiplies with every label and every destination market. It is repetitive, high-consequence, and nobody enjoys it.
- Export documentation preparation and checking
- Label approval and geographical indication rule navigation
- Food safety and HACCP documentation retrieval
- Vintage and batch record search across seasons
How an Adelaide Engagement Runs
Remotely from Melbourne, on your infrastructure, inside your security boundary, governed by your controls and your people.
The Classification Question, First
Before scope and before price: is the data unclassified? If any part of what you want the model to read is classified, export-controlled, or otherwise needs a cleared supplier, we say so and stop. That conversation takes one call rather than one quarter.
Remote Scoping From Melbourne
Systems review, data assessment and architecture are done on screens. Adelaide is thirty minutes behind us, which is the smallest time-zone problem in the country. If a workshop genuinely needs a room, we fly over and it appears as a line item you can see and decline.
Pilot on Your Infrastructure
The model is deployed on hardware or a private cloud tenancy you control, inside your network. Your security controls apply to it because it sits inside your boundary, and your own staff operate it. We are not in the room, for unclassified work, we do not need to be.
Production and Handover
Scaled across the teams that need it, with operating documentation written so your people can run it without a permanent retainer to us. We will say plainly when the honest answer is that you no longer need us.
Sovereignty You Can Verify, Not Accreditation We Do Not Have
The genuine product story does not need a defence costume. The models are open-weight and self-hosted, so your data never reaches an offshore model provider, because in this architecture there is no model provider.
Self-Hosted, No Offshore Model Provider
The deployment runs on infrastructure you control. There is no API call out to a US model vendor, because the weights sit on your side of the boundary.
- Open-weight models running on your hardware or your private cloud tenancy
- No prompt, document or embedding leaves your network
- Your access controls, your logging, your retention policy. It is your environment
- Appropriate for unclassified, commercially sensitive information
- Not appropriate for classified, PROTECTED or export-controlled material
Integration With Systems You Already Run
The AI layer connects to the document and record systems your business already has. Where a system will not let its data out, we tell you before you buy rather than after.
- SharePoint and Microsoft 365 document libraries
- Common document and records management platforms
- Quality management and non-conformance systems
- An honest read on which of your systems will be the blocker
Related AI Solutions
On-Premises LLM Deployment
The technical detail behind a deployment that runs entirely on hardware you own, with no external network dependency.
View on-premises options →Sovereign AI Australia
What data sovereignty actually means once you remove the marketing, and what it does not mean.
Learn about sovereign AI →Custom LLM for Healthcare
For research institutes and health organisations working inside ethics approvals and the Privacy Act.
See healthcare AI solutions →Frequently Asked Questions
Are you a DISP member?
No. Yes AI holds no membership of the Defence Industry Security Program, no security clearances, no cleared personnel, no IRAP assessment and no ITAR-compliant facility, and we hold no position on a government panel. We are a small Melbourne consultancy. We state it this bluntly because pages selling AI into Adelaide routinely imply the opposite with phrases like "DISP-compatible architecture" and "we engage cleared personnel where required", and a defence contractor reading that is entitled to assume the words mean something. If your requirement needs a DISP member, you need a different supplier, and no architecture diagram from us changes that.
Can you work with ITAR or export-controlled technical data?
No. Export-controlled technical data, whether under ITAR, the US export administration rules, or Australia's defence trade controls regime, requires a supplier with the relevant authorisations, facilities and vetted personnel. We have none of them. We will not take that work, and if it surfaces mid-engagement we will stop and tell you rather than quietly proceed. The corollary is the point of this page: the unclassified corporate documentation of a defence supply-chain business is not export-controlled, and that is the work we are proposing to do.
So what defence-adjacent work can you actually do?
The unglamorous majority of it. A supplier into the defence chain runs on tender responses, capability statements, supplier quality records, non-conformance histories, corrective actions, work instructions, certification registers, audit evidence, HR policy and procurement paperwork. Almost none of that is classified or export-controlled. It is ordinary commercially sensitive business information that happens to belong to a business with a defence customer. It is also the work quietly consuming your engineers and your bid team. A self-hosted model over that material, inside your own network, is a real project with a measurable return, and it requires no clearance from anyone at Yes AI because we never see the data.
Do you have an Adelaide office or local team?
No. No Adelaide premises, no South Australian staff, no local account manager. We are based in Melbourne and deliver to Adelaide remotely, which is genuinely easier here than anywhere else in the country, Adelaide runs half an hour behind us and both states shift for daylight saving, so the gap never widens. Meetings happen on video, in your business hours, with the same people from the first call to handover. If an engagement genuinely needs us in a room for a workshop, we fly over and it appears as a line item you can see and decline. If what you actually need is somebody who can be at your site on Thursday, hire an Adelaide firm and we will say so in the first call.
Does South Australia have its own privacy Act?
No, and it is the most genuinely interesting compliance fact in the state. South Australia has no state privacy legislation. SA public sector agencies operate under Premier and Cabinet Circular PC012, which sets out a set of Information Privacy Principles as an administrative instruction rather than a statute. It binds agencies as a matter of government policy; it is not a statutory right an individual enforces the way they would under an Act. The practical consequence for an AI project is that if you are an SA agency, or contracted to one, you should stop looking for the state Act and read PC012 and your contract instead, because the binding obligation usually arrives through the contract. Federally, the Privacy Act 1988 (Cth) and the Australian Privacy Principles still apply to private-sector businesses within their scope, and the Australian Consumer Law applies to anything your AI says to a customer. This is general information on how these obligations typically apply, not legal advice. We work alongside your lawyers rather than in place of them.
How does this work for a research institute operating under ethics approvals?
Human research ethics approvals typically specify how participant-derived data may be used, stored and disclosed, and most do not contemplate that data being sent to a third party for a purpose absent from the consent form. That makes public AI tools a genuine problem for research data, and it is one of the clearest cases for self-hosting: a model deployed inside your own infrastructure keeps the data within the boundary the approval already describes, because nothing leaves. We will help you document the data-handling approach for your privacy officer and your HREC, but the approval is theirs to give and the environment is yours to control. We do not hold it, and we do not see it.
Sources and further reading
- Australian Privacy Principles (Office of the Australian Information Commissioner)
- The Privacy Act 1988 (Office of the Australian Information Commissioner)
- Infosec Registered Assessors Program (IRAP) (Australian Cyber Security Centre)
- Consumer guarantees under the Australian Consumer Law (Australian Competition and Consumer Commission)
The Honest Version of the Adelaide Pitch
No DISP membership, no clearances, no Adelaide office, and a self-hosted LLM over your unclassified documentation that runs entirely inside your own security boundary. If that is not what you need, you will hear it in the first call rather than the third invoice.