In the era of AI-first business<\/b>, relying on restrictive SaaS automation limits is a strategic vulnerability. When you build on rented land, you face per-execution pricing. You deal with API rate limits. You also risk third-party data snooping.<\/p>\n
You aren’t building an ecosystem. You are building a dependency.<\/p>\n
At Thinkpeak.ai<\/b>, we believe in transforming static operations. We want to build dynamic, self-driving ecosystems<\/b>. That starts with owning the infrastructure that powers your logic.<\/p>\n
Self-hosting n8n<\/b> via Docker is the “hello world” of this transformation. It offers significant advantages:<\/p>\n This guide is not a quick tutorial. This is an enterprise-grade blueprint. We will deploy a secure, scalable, and AI-ready n8n stack using Docker Compose<\/b>.<\/p>\n Before we touch the config files, you need the right infrastructure. It must handle Bespoke Internal Tools<\/b> and heavy data lifting.<\/p>\n A standard $5\/month VPS is insufficient for 2026. You need more power to run n8n alongside a database and a local AI agent. We recommend the following specs:<\/p>\n Ensure your server runs a fresh install of Ubuntu 24.04 LTS<\/b>. You will need:<\/p>\n Most tutorials suggest using the default SQLite database. Do not do this<\/b>. SQLite locks under heavy concurrent loads.<\/p>\n A “Self-Driving Ecosystem” generates heavy loads. We will use PostgreSQL<\/b> from day one.<\/p>\n Create your project directory:<\/p>\n Here is the production-ready configuration<\/b>. We separate the database, the application, and the reverse proxy (Traefik). This ensures automatic SSL management.<\/p>\n The Your .env File:<\/b><\/p>\n Critical Security Warning:<\/b> The N8N_ENCRYPTION_KEY<\/b> encrypts your credentials in the database. This includes API keys for Slack or Google Sheets. If you lose this key, you lose access to all your connected accounts. Back this up immediately.<\/b><\/p>\n Does configuring reverse proxies feel like a distraction? Thinkpeak.ai: The Automation Marketplace<\/b> offers pre-architected workflows. These templates skip the DevOps setup.<\/p>\n Explore the Marketplace<\/a><\/p>\n This is where our AI-first philosophy<\/b> comes alive. By adding Ollama<\/b> to your stack, you can run “Digital Employees.” These are autonomous agents capable of reasoning without sending data to OpenAI.<\/p>\n Add this service to your Note: Remove the deploy block if your VPS does not have a GPU. It will run on CPU, but slower.<\/i><\/p>\n You now have a private, free-to-use intelligence layer inside your automation stack.<\/p>\n Your “self-driving ecosystem” will grow. A single n8n instance might choke on heavy loads. This happens when processing thousands of leads from a Cold Outreach Hyper-Personalizer<\/b> campaign.<\/p>\n To scale, we switch to Queue Mode<\/b>. This involves adding Redis<\/b> to manage job queues. We also deploy separate Worker containers<\/b>.<\/p>\n Add Redis to docker-compose.yml:<\/b><\/p>\n Add the Worker Service:<\/b><\/p>\n Update the Main n8n Service:<\/b><\/p>\n Add these environment variables to your main This architecture allows you to scale horizontally. Need more power? Simply spin up more worker containers.<\/p>\n Need a system that scales to millions of rows? Our Bespoke Internal Tools & Custom App Development<\/b> service builds infrastructure like this for you. We architect the backend and the scaling logic.<\/p>\n Consult with Thinkpeak Engineering<\/a><\/p>\n A robust system protects itself. Instead of relying on manual backups, we will use n8n to back up n8n. This recursive automation<\/b> is a hallmark of the Thinkpeak.ai approach.<\/p>\n The Strategy:<\/b><\/p>\n This ensures your intellectual property is safe. Even if your server fails, your business logic remains secure in the cloud.<\/p>\n You have now deployed a stack that rivals the internal tooling of Fortune 500 companies. You have:<\/p>\n This is more than just “hosting software.” You have built the engine for your company’s proprietary software stack.<\/p>\n However, maintaining this stack requires vigilance. Updates can break things. Databases need maintenance. Security patches are critical.<\/p>\n Ready to automate but not ready to be a SysAdmin?<\/b><\/p>\n Thinkpeak.ai<\/b> bridges the gap. Need speed? Browse our Automation Marketplace for plug-and-play workflows. Need scale? Hire our Bespoke Engineering team.<\/p>\n We build Digital Employees<\/b> and custom low-code apps. We ensure every piece of software you own talks to each other intelligently.<\/p>\n Start Building Your Self-Driving Ecosystem Today<\/a><\/p>\n Yes, the Docker Setup works on Windows, Mac, and Linux. However, your automations stop when you close your laptop. For business-critical operations like the Inbound Lead Qualifier<\/b>, a 24\/7 VPS is mandatory.<\/p>\n We used Docker Volumes<\/b> ( Yes, provided you use Basic Auth<\/b> and SSL via Traefik. For extra security, you can configure Traefik to only allow access from your office IP address or VPN.<\/p>\n Postgres, Traefik, Redis ve yerel yapay zeka ile g\u00fcvenli, \u00f6l\u00e7eklenebilir kendi kendine bar\u0131nd\u0131rma i\u00e7in ad\u0131m ad\u0131m n8n Docker kurulumu - kurumsal kullan\u0131ma haz\u0131r.<\/p>","protected":false},"author":2,"featured_media":16648,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[103],"tags":[],"class_list":["post-16649","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-business-process-automation"],"_links":{"self":[{"href":"https:\/\/thinkpeak.ai\/tr\/wp-json\/wp\/v2\/posts\/16649","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/thinkpeak.ai\/tr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/thinkpeak.ai\/tr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/thinkpeak.ai\/tr\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/thinkpeak.ai\/tr\/wp-json\/wp\/v2\/comments?post=16649"}],"version-history":[{"count":0,"href":"https:\/\/thinkpeak.ai\/tr\/wp-json\/wp\/v2\/posts\/16649\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/thinkpeak.ai\/tr\/wp-json\/wp\/v2\/media\/16648"}],"wp:attachment":[{"href":"https:\/\/thinkpeak.ai\/tr\/wp-json\/wp\/v2\/media?parent=16649"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/thinkpeak.ai\/tr\/wp-json\/wp\/v2\/categories?post=16649"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/thinkpeak.ai\/tr\/wp-json\/wp\/v2\/tags?post=16649"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
Prerequisites: The Hardware for Your Digital Workforce<\/h2>\n
1. VPS Specifications<\/h3>\n
\n
2. The Software Environment<\/h3>\n
\n
Step 1: The Enterprise Architecture (Postgres over SQLite)<\/h2>\n
mkdir thinkpeak-stack\ncd thinkpeak-stack\ntouch docker-compose.yml .env<\/code><\/pre>\nThe Base docker-compose.yml<\/h3>\n
version: '3.8'\n\nservices:\n traefik:\n image: traefik:v3.0\n command:\n - \"--api.insecure=true\"\n - \"--providers.docker=true\"\n - \"--providers.docker.exposedbydefault=false\"\n - \"--entrypoints.web.address=:80\"\n - \"--entrypoints.websecure.address=:443\"\n - \"--certificatesresolvers.myresolver.acme.tlschallenge=true\"\n - \"--certificatesresolvers.myresolver.acme.email=${SSL_EMAIL}\"\n - \"--certificatesresolvers.myresolver.acme.storage=\/letsencrypt\/acme.json\"\n ports:\n - \"80:80\"\n - \"443:443\"\n volumes:\n - \"\/var\/run\/docker.sock:\/var\/run\/docker.sock:ro\"\n - \".\/letsencrypt:\/letsencrypt\"\n networks:\n - n8n-network\n\n postgres:\n image: postgres:16-alpine\n restart: always\n environment:\n - POSTGRES_USER=${DB_USER}\n - POSTGRES_PASSWORD=${DB_PASSWORD}\n - POSTGRES_DB=${DB_NAME}\n - POSTGRES_NON_ROOT_USER=${DB_USER}\n volumes:\n - postgres_data:\/var\/lib\/postgresql\/data\n networks:\n - n8n-network\n healthcheck:\n test: [\"CMD-SHELL\", \"pg_isready -U ${DB_USER} -d ${DB_NAME}\"]\n interval: 5s\n timeout: 5s\n retries: 5\n\n n8n:\n image: n8nio\/n8n:latest\n restart: always\n environment:\n - DB_TYPE=postgresdb\n - DB_POSTGRESDB_HOST=postgres\n - DB_POSTGRESDB_PORT=5432\n - DB_POSTGRESDB_DATABASE=${DB_NAME}\n - DB_POSTGRESDB_USER=${DB_USER}\n - DB_POSTGRESDB_PASSWORD=${DB_PASSWORD}\n - N8N_BASIC_AUTH_ACTIVE=true\n - N8N_BASIC_AUTH_USER=${N8N_USER}\n - N8N_BASIC_AUTH_PASSWORD=${N8N_PASSWORD}\n - N8N_HOST=${SUBDOMAIN}\n - N8N_PORT=5678\n - N8N_PROTOCOL=https\n - WEBHOOK_URL=https:\/\/${SUBDOMAIN}\n - N8N_ENCRYPTION_KEY=${ENCRYPTION_KEY}\n ports:\n - \"127.0.0.1:5678:5678\"\n volumes:\n - n8n_data:\/home\/node\/.n8n\n networks:\n - n8n-network\n depends_on:\n postgres:\n condition: service_healthy\n labels:\n - \"traefik.enable=true\"\n - \"traefik.http.routers.n8n.rule=Host(`${SUBDOMAIN}`)\"\n - \"traefik.http.routers.n8n.entrypoints=websecure\"\n - \"traefik.http.routers.n8n.tls.certresolver=myresolver\"\n\nvolumes:\n n8n_data:\n postgres_data:\n\nnetworks:\n n8n-network:\n driver: bridge<\/code><\/pre>\nStep 2: Security & Environment Variables<\/h2>\n
.env<\/code> file is your control center. It keeps your credentials out of your repository. It also allows you to rotate keys<\/b> easily.<\/p>\n# Domain Configuration\nSUBDOMAIN=n8n.yourcompany.com\nSSL_EMAIL=admin@yourcompany.com\n\n# Database Secrets\nDB_USER=n8n_user\nDB_PASSWORD=REPLACE_WITH_SECURE_PASSWORD\nDB_NAME=n8n_db\n\n# n8n Auth\nN8N_USER=admin\nN8N_PASSWORD=REPLACE_WITH_SECURE_PASSWORD\nENCRYPTION_KEY=REPLACE_WITH_RANDOM_STRING_32_CHARS<\/code><\/pre>\nStep 3: Integrating Local AI (Ollama)<\/h2>\n
docker-compose.yml<\/code> under services<\/code>:<\/p>\n ollama:\n image: ollama\/ollama:latest\n container_name: ollama\n volumes:\n - ollama_data:\/root\/.ollama\n networks:\n - n8n-network\n deploy:\n resources:\n reservations:\n devices:\n - driver: nvidia\n count: 1\n capabilities: [gpu]<\/code><\/pre>\nConnecting n8n to Ollama<\/h3>\n
\n
http:\/\/ollama:11434\/api\/generate<\/code>. We use the service name ollama<\/code> because they share the Docker network.<\/li>\n{\n \"model\": \"llama3\",\n \"prompt\": \"Summarize this email for the sales team: {{ $json.body }}\",\n \"stream\": false\n}<\/code><\/pre>\nStep 4: Scaling for Enterprise (Queue Mode)<\/h2>\n
redis:\n image: redis:alpine\n restart: always\n networks:\n - n8n-network<\/code><\/pre>\n n8n-worker:\n image: n8nio\/n8n:latest\n command: worker\n restart: always\n environment:\n - DB_TYPE=postgresdb\n - DB_POSTGRESDB_HOST=postgres\n - DB_POSTGRESDB_PORT=5432\n - DB_POSTGRESDB_DATABASE=${DB_NAME}\n - DB_POSTGRESDB_USER=${DB_USER}\n - DB_POSTGRESDB_PASSWORD=${DB_PASSWORD}\n - EXECUTIONS_MODE=queue\n - QUEUE_BULL_REDIS_HOST=redis\n - QUEUE_BULL_REDIS_PORT=6379\n - N8N_ENCRYPTION_KEY=${ENCRYPTION_KEY}\n networks:\n - n8n-network\n depends_on:\n - postgres\n - redis<\/code><\/pre>\nn8n<\/code> block:<\/p>\n - EXECUTIONS_MODE=queue\n - QUEUE_BULL_REDIS_HOST=redis\n - QUEUE_BULL_REDIS_PORT=6379<\/code><\/pre>\nStep 5: The “Self-Healing” Backup Strategy<\/h2>\n
\n
Conclusion<\/h2>\n
\n
Frequently Asked Questions (FAQ)<\/h2>\n
Can I run n8n locally on my laptop instead of a VPS?<\/h3>\n
How do I update n8n without losing data?<\/h3>\n
n8n_data<\/code>), so your data is persistent. To update, run docker-compose pull<\/code> to download the latest images. Then run docker-compose up -d<\/code> to recreate containers with new code.<\/p>\nIs it safe to expose n8n to the internet?<\/h3>\n
Resources<\/h2>\n
\n