
Running Ollama locally means hosting open-weight large language models such as Llama, Qwen, Mistral, Gemma or gpt-oss on your own laptop, workstation or server. Prompts and documents never leave your network, there are no per-token fees, and it works offline. For Australian organisations it simplifies Privacy Act and data sovereignty questions for sensitive work.
Key takeaways
- Ollama is open-source (MIT licence) software that downloads and runs open-weight models with one command, on macOS, Windows and Linux.
- It exposes a local API, including an OpenAI-compatible endpoint, so many existing tools can point at it with small changes.
- The strongest business cases are sensitive documents, high-volume batch work and offline or restricted environments.
- Hardware sets the ceiling: memory decides which model sizes you can run, and a GPU decides speed.
- Most organisations end up hybrid: local models for sensitive or high-volume work, cloud models where frontier capability matters.
What is Ollama?
Ollama is an open-source platform for running large language models on your own hardware. Think of it as a package manager for AI models: you pull a model, run it and talk to it locally.
- Install OllamaDownload for Mac/Windows/Linux
- Pull Modelollama pull llama3.1
- Run LocallyProcesses on your CPU/GPU
- No Data LeavingCan run fully offline
| Feature | What it means |
|---|---|
| MIT licence | Ollama itself can be used commercially. Check each model's own licence |
| Offline operation | Works without internet once models are downloaded |
| Multi-platform | macOS, Windows, Linux |
| GPU acceleration | NVIDIA CUDA, AMD ROCm, Apple Metal |
| API | Local REST API plus an OpenAI-compatible endpoint |
| Model library | Llama, Qwen, Mistral, Gemma, DeepSeek, gpt-oss and many more |
In August 2025 OpenAI released open-weight gpt-oss models, which are available through Ollama, a sign of how far local deployment has moved into the mainstream.
Why should Australian organisations run Ollama locally?
1. Privacy and data sovereignty
Sending personal information to an overseas AI provider is a cross-border disclosure under APP 8 of the Privacy Act 1988, and you stay accountable for how the recipient handles it. Running models on your own infrastructure in Australia removes that disclosure for the workloads you keep local.
| Cloud AI API | Local AI (Ollama) | Impact | |
|---|---|---|---|
| Where data is processed | Provider's data centres, often overseas | Your machine or server | Local |
| Retention | Set by provider terms | You control | Owned |
| Foreign legal access | Possible, depending on provider | Limited to your own jurisdiction | Reduced |
| Compliance work | Vendor assessment, APP 8 documentation | Internal security controls | Simpler |
Keeping data on your hardware avoids training use of your prompts, overseas disclosure questions and lengthy vendor assessments for those workloads. See our data sovereignty guide.
2. Cost at volume
Cloud APIs charge per token. Local models cost hardware, electricity and support time. Once usage is steady and high, such as batch document processing or always-on internal assistants, local deployment can cost less over a few years. Model it on your own usage data: current monthly API spend, expected growth, hardware, power and the staff time to run it.
3. Speed and reliability
A local model has no internet round trip, no provider rate limits and no dependency on a provider's uptime. You do take on responsibility for your own uptime.
4. Capable open models
Open-weight models have improved quickly. Leading open models now handle summarising, drafting, extraction, classification and coding well, though the strongest frontier cloud models still lead on the hardest reasoning tasks. Test on your own work before deciding.
What's your primary use case?
- General chat, drafting, summarisingLlama 3.1 8B, Qwen or Gemma in the 7-12B range
- Coding assistanceQwen2.5-Coder or another code-tuned model
- Long or complex documentsA larger model (30B-70B) if your hardware allows
- Multilingual contentQwen or Mistral families
- Harder reasoninggpt-oss or a DeepSeek R1 distilled model
5. Control
You choose the model, adapt it to your domain, integrate directly with your systems, upgrade on your schedule and configure it for your regulatory needs.
How do you set up Ollama?
- Step 1Download and installGet Ollama for your OS
- Step 2Pull a modelDownload a model sized for your hardware
- Step 3Test interactive chatRun your first prompt
- Step 4Use the APIConnect your applications
Step 1: Install
macOS and Windows: download the installer from ollama.com and run it.
Linux:
curl -fsSL https://ollama.com/install.sh | sh
In a corporate environment, check with IT first. Installation may need admin rights and approval.
Step 2: Pull a model
ollama pull llama3.1:8b
This downloads Meta's Llama 3.1 8B model, a quantised download of roughly 5GB that runs on a typical 16GB business laptop. For lower-spec machines, try llama3.2 (3B).
Step 3: Chat
ollama run llama3.1:8b
Try summarising a non-sensitive document, drafting an email or explaining a policy.
Step 4: Use the API
Ollama listens on http://localhost:11434. It has its own API and an OpenAI-compatible endpoint under /v1, so many tools built for OpenAI can be pointed at it.
curl http://localhost:11434/api/chat -d '{
"model": "llama3.1:8b",
"messages": [{"role": "user", "content": "Hello!"}]
}'
What hardware do you need to run Ollama?
Memory decides which models fit. A GPU or Apple Silicon decides how fast they run.
| Model size | Practical memory | Impact | |
|---|---|---|---|
| 3B parameters | Simple tasks, classification | 8GB | Most modern laptops |
| 7-8B parameters | General purpose | 16GB | Most business laptops |
| 13-14B parameters | Better quality drafting | 32GB | Workstation class |
| 70B parameters | High quality, slower | 64GB+ or large GPU memory | Server or high-end desktop |
Ollama runs on CPU alone, but slowly for anything beyond small models. A modern NVIDIA GPU or an Apple Silicon Mac with plenty of unified memory makes interactive use comfortable. For shared team use, a dedicated server with GPU memory sized to your chosen model is the usual pattern. Our private AI infrastructure team specifies this for production.
Where does local AI work best in business?
Document Q&A with RAG
Retrieval-augmented generation lets staff ask questions of your own documents. With Ollama and a local vector store, documents never leave your infrastructure.
- DocumentsYour PDFs, Word docs, emails
- Embed LocallyConvert to vectors
- Store LocallyA local vector database
- QueryAsk questions
- AnswerGrounded responses with sources
Good fits include contract and policy review, internal knowledge search, compliance documentation and confidential reporting.
Code assistance
Code-tuned local models help with completion, explanation, documentation and review without sending proprietary code to external servers.
Internal assistants
Assistants that handle sensitive internal queries, connect securely to internal systems and run without per-query costs, with a person approving anything that reaches a customer.
Should you use local AI, cloud AI or both?
What type of work is it?
- Sensitive or confidential dataLocal (privacy)
- High-volume batch processingLocal (cost at volume)
- Hardest reasoning or newest capabilitiesCloud frontier models under business terms
- Real-time voice or visionCloud specialised APIs, or local if data is sensitive
- Prototype or experimentEither, depending on data
What Australian rules make local AI attractive?
- Privacy Act 1988, APP 8: local processing avoids cross-border disclosure for the workloads you keep onshore.
- Automated decision-making transparency: from 10 December 2026, privacy policies must describe automated decisions that significantly affect individuals. Local systems make documenting how they work easier.
- APRA CPS 234: regulated financial entities must maintain information security proportionate to threats. Keeping AI inside your security perimeter helps.
- Health information: sensitive information under the Privacy Act and state health records laws. Local processing reduces exposure.
How do you take Ollama from laptop to production?
- Week 1PilotInstall on approved machines, test with non-sensitive data
- Week 2-3Use case validationMeasure quality against current tools on real tasks
- Week 4-6Infrastructure planningSize hardware, plan network and security review
- Week 7-8Production deploymentDeploy to servers, integrate, add logging and access control
- OngoingOperateModel updates, monitoring, new use cases
For production, plan for access control through your identity provider, request logging, monitoring, backups, a model update process and a named owner. A laptop pilot proves value. Production needs the same operational discipline as any other system.
How Solve8 can help
We design and run private AI on your infrastructure in Australia or New Zealand (your cloud or your own servers): hardware sizing, model selection, RAG over your documents, access control and ongoing operation. Across our consultants' careers, including enterprise data systems work in BHP, Rio Tinto and Senex Energy environments, we have deployed technology inside tightly controlled networks. See private AI infrastructure, our offline AI corporate guide, or talk to us.
