In 2026, the "Local AI" movement is no longer just a niche hobby for hardware enthusiasts. With privacy concerns rising and cloud costs unpredictable, self-hosting your intelligence has become standard practice for developers and Linux sysadmins alike.
Today, we’re looking at how to combine the power of Ollama with the robustness of n8n to build a truly private automation stack. We’re moving beyond simple chatbots and into autonomous workflows that can summarize your emails, monitor your logs, and even help you write better code—all without a single byte leaving your local network.
Why Self-Host AI Automation?
- Zero Latency: No API round-trips to Virginia or Ireland.
- Privacy: Your data, your logs, your secrets stay on your hardware.
- No Subscriptions: One-time hardware cost, zero monthly fees.
- Full Control: Use any model you want, from Llama 3.x to Mistral or DeepSeek.
The Stack
- OS: Any modern Linux distribution (Ubuntu 24.04+ or Debian 13 recommended).
- Ollama: The easiest way to run LLMs locally.
- n8n: The "Zapier for self-hosters" with built-in AI nodes.
- Docker: For easy deployment and isolation.
Step 1: Install Ollama
If you haven't installed Ollama yet, it's a single command:
curl -fsSL https://ollama.com/install.sh | sh
To verify it's working and pull a versatile model (like Llama 3):
ollama pull llama3
ollama run llama3 "Hello, world!"
Step 2: Deploy n8n with Docker
We’ll use Docker Compose to get n8n up and running. Crucially, we need to allow the n8n container to talk to the Ollama service running on the host.
Create a docker-compose.yml:
version: '3.8'
services:
n8n:
image: n8nio/n8n:latest
restart: always
ports:
- "5678:5678"
environment:
- N8N_HOST=localhost
- N8N_PORT=5678
- N8N_PROTOCOL=http
volumes:
- n8n_data:/home/node/.local/share/n8n
# This allows n8n to reach Ollama on the host machine
extra_hosts:
- "host.docker.internal:host-gateway"
volumes:
n8n_data:
Launch it:
docker compose up -d
Step 3: Create Your First AI Workflow
- Open n8n at
http://localhost:5678. - Add an Ollama node to your workflow.
- Configure the Credentials: Set the URL to
http://host.docker.internal:11434. - Select your model (e.g.,
llama3). - Connect it to a trigger—like an HTTP Request or a Cron job.
Practical Example: The "Log Watcher" Workflow
Imagine you want a summary of your system logs emailed to you every morning, but you don't want to send raw logs to a cloud AI.
- Node 1 (Execute Command):
tail -n 100 /var/log/syslog - Node 2 (Ollama): Prompt: "Summarize these logs and highlight any security warnings or critical errors."
- Node 3 (Email/Discord): Send the output to your preferred channel.
Performance Tips for 2026
- GPU Acceleration: If you have an NVIDIA GPU, make sure you have the
nvidia-container-toolkitinstalled so Docker can leverage CUDA. - Model Quantization: Stick to
4-bitor6-bitquantizations for a good balance of speed and intelligence. - VRAM Matters: For 7B or 8B models, 8GB of VRAM is the sweet spot. For 70B models, you’ll want 24GB+ (or a Mac Studio).
References & Further Reading
Self-hosting your AI isn't just about the technology; it's about reclaiming ownership of your tools. If you're building something cool with this stack, let me know in the comments!
Happy hacking!
