Ai Suite

AI-Suite

AI-Suite is intended to provide an end-to-end path from zero to working AI workflows and agents for developers and those who want to enable a local, private AI solution.

It provides an open, curated, pre-configured Docker Compose configuration file along with Python and Bash shell scripts that bootstraps fully featured Local AI Agents, personal AI Assistant and a Low/No Code environment on a self-hosted platform enabling users to focus on building solutions that employ robust AI workflows and agents.

Portions of AI-Suite extends Cole Medin's Self-hosted AI Package which is built on the n8n-io Self-hosted AI Starter Kit.

Curated by Trevor SANDY - https://github.com/trevorsandy.

What’s included

✅ Self-hosted n8n - Automation platform with over 400 integrations and advanced AI components.

✅ Self-hosted OpenClaw - a personal AI assistant_ you run on your own devices.

✅ Open WebUI - ChatGPT-like interface to privately interact with your local models and N8N agents.

✅ OpenCode - open source agent that helps you write code in your terminal.

✅ Ollama - Cross-platform LLM platform to install and run the latest LLMs.

✅ LLaMA.cpp - Cross-platform LLaMA.cpp HTTP Server platform to install and run the latest LLMs in gguf format.

✅ Supabase - Open source database as a service, most widely used database for AI agents.

✅ Flowise - No/low-code AI agent builder that pairs very well with n8n.

✅ Qdrant - Open source, high performance vector store with an comprehensive API.

✅ PostgreSQL - Workhorse of the Data Engineering world, backend for Langfuse.

✅ MCP Gateway - Reverse proxy and management layer for MCP servers.

✅ Neo4j - Knowledge graph engine that powers tools like GraphRAG, LightRAG, and Graphiti.

✅ Redis (Valkey) - High-performance key/value datastore, supports caching and message queues workloads.

✅ SearXNG - Open source internet metasearch engine, aggregates results from up to 229 search services.

✅ Langfuse - Open source LLM engineering platform for agent observability.

✅ MinIO - High-performance, S3-compatible object storage solution.

✅ ClickHouse - Open source, database management system that can generate analytical data reports in real-time.

✅ Caddy - Managed HTTPS/TLS for custom domains.

✅ Nginx - HTTPS/TLS server, reverse proxy, TCP/UDP proxy server

✅ Authelia - Authentication and authorization server, identity and access management (IAM).

Prerequisites

System specifications:

• 32GB RAM recommended (8GB minimum)
• 40GB free disk space

Before you begin, make sure you have the following software installed:

• Git - For easy repository management.
• Python 3.10+ - To run the setup script.
• Node 22.16+ - For auto-configuration and OpenClaw runtime.
• Docker 20.10+ - Required to

setup and run all AI-Suite services.

Docker Compose commands

By default, AI-Suite automatic configuration will validate and, if needed, install Docker. However, you can also manually install Docker in advance.

If you are using a machine without the docker compose application available by default, run these commands to install Docker compose:

``bash DOCKER_COMPOSE_VERSION=$(curl -s https://api.github.com/repos/docker/compose/ releases/latest | grep 'tag_name' | cut -d\\" -f4) sudo curl -L "https://github.com/docker/compose/releases/download/${DOCKER_COMPOSE_VERSION}/docker-compose-linux-x86_64" -o /usr/local/bin docker-compose sudo chmod +x /usr/local/bin/docker-compose sudo mkdir -p /usr/local/lib/docker/cli-plugins sudo ln -s /usr/local/bin/docker-compose /usr/local/lib/docker/cli-plugins/docker-compose ``

Developers may also consider the following optional software:

• VSCode - Python and Bash shell development.
• GitKraken - Superior Git SCM platform

Installation

Step 1: Clone the repository and set environment variables

1. Clone the repository and navigate to the project directory:

``powershell git clone https://github.com/trevorsandy/ai-suite.git cd ai-suite ``

1. AI-Suite will automatically configure the settings and environment variables

including generation of secret passwords, tokens and keys needed to successfully perform installation and startup operations.

However, it is good practice to review your .env environment variables before running install or update taking into account your installation platform components, specifications and requirements. Particularly pay attention to the Ollama or LLaMA.cpp (depending on which LLM you are using) configuration settings and Windows WSL (posix) versus native paths.

Environment variables

Optionally, you can make a copy of .env.example renamed to .env in the project directory.

``powershell cp .env.example .env ``

Credentials

If you install Supabase, all credentials will be auto-generated. If you prefer to manually setup the Supabase credentials, you may use the their self-hosting guide.

.env.example file

```ini # Change this file name to .env after updating it if not using auto-configuration!

############ # Auto-Configuration: # AI-Suite uses this file as the .env template. You should update default settings # you wish to set before running install or update using suiteservices.py. # # If an existing .env is encountered during auto-configuration, defaults from this # file are overlayed with the existing .env values. This means secrets for variables # in the existing .env will not be generated by AI-Suite during install or update. # # Variables that hold generated secrets will have a specific default value # format: =generate using [:] # Examples: N8NRUNNERSAUTHTOKEN=generate using genhex:32 # SERVICEROLEKEY=generate using gentoken:servicerolesym # PROXYAUTHPASSWORD=generate using genbcrypt # # Generating Credentials: # All secrets are generated when using auto-configure except N8NENCRYPTION_KEY # which can also be set by exporting the environment variable or by placing the # key=value pair in n8n/.n8n.encryption.key.

# When using your existing n8n encryption key placed in n8n/.n8n.encryption.key, # be sure to properly terminate the line entry with a new line (hit enter key to # move your cursor to the next line). Also ensure the file format is LF (Unix) # and not CRLF (Windows). # # OpenSSL: Available by default on Linux/Mac via command openssl rand -hex 32 # For Windows, use 'WSL2', 'Git Bash' terminal installed with git or from cmd # run the command: python -c "import secrets; print(secrets.tokenhex(32))" # # Password: Use Python command to generate 16-character strong password: # python3 -c "import secrets;import string; alphabet = string.asciiletters + string.digits;\ # password = ''.join(secrets.choice(alphabet) for i in range(16));\ # print(password)" # # JWT Tokens: Use https://jwtsecrets.com/#generator to generate keys and tokens # ranging from 8 to 128 characters long. ############

############ # [required for Auto-Configuration] - automatically set when enabled (AC=True) # Access Control - Proxy, Identity and Access Management configuration ############

# Enable proxy, identity and access auto-configure mode -credentials are auto-generated AC=True # Your public/private domain name. An arbitrary name is allowed for private domain ACDOMAIN=local.pc # Configure AI-Suite as a local (private) vs. global (public) installation ACLOCAL=True # The reverse proxy to use (Caddy or Nginx) ACPROXY=caddy # User name for PROXY configuration (alphanumeric characters only) ACUSERNAME=AISuiteProxyUser # User password for PROXY configuration # Keep default '*****' to trigger password prompt during setup ACPASSWORD='*****' # Send confirmation email on user registration - SMTP server required ACCONFIRM=False # Enable Authelia 2FA (two factor authentication) support ACWITHAUTHELIA=True # User email address for Authelia - required if ACWITHAUTHELIA=True ACEMAIL=ai-suite-internal@local.pc # User display name for Authelia - required if ACWITHAUTHELIA=True (alphanumeric chars and spaces only) ACDISPLAYNAME='AI Suite Authelia User' # Use Redis with Authelia - recommended if ACWITHAUTHELIA=True and public ACWITHREDIS=False # Auto-configuration runtime log relative path without filename ACLOG_PATH=./access

############ # [required] - automatically set when auto-configure (AC=True) is enabled # n8n credentials - use OpenSSL openssl rand -hex 32 for all ############

# Master key used to encrypt sensitive credentials that n8n stores N8NENCRYPTIONKEY=generate using genn8ncrypt # Shared secret between n8n containers and runners sidecars N8NRUNNERSAUTHTOKEN=generate using genhex:32 # Specific JWT secret. By default, n8n generates one on start N8NUSERMANAGEMENTJWTSECRET=generate using genhex:32

############ # [required] - automatically set when auto-configure (AC=True) is enabled # PostgreSQL database user password - use OpenSSL openssl rand -hex 16 ############

POSTGRESPASSWORD=generate using genhex:16

# Following settings are required if you enable the respective module.

# # ####### ##### #

############ # [required for Supabase] - automatically set when auto-configure (AC=True) is enabled # Supabase Secrets

# Read these docs for any help: https://supabase.com/docs/guides/self-hosting/docker # For the JWT Secret and keys, see: https://supabase.com/docs/guides/self-hosting/docker#generate-api-keys # For the other secrets, see: https://supabase.com/docs/guides/self-hosting/docker#update-secrets

# Note that using special symbols (like '%') can complicate things a bit for your Postgres password. # If you use special symbols in your Postgres password, you must remember to percent-encode your password later if using the # Postgres connection string, for example, postgresql://postgres.projectref:p%3Dword@aws-0-us-east-1.pooler.supabase.com:6543/postgres # # To enable the new asymmetric key support, uncomment these lines in docker-compose.yml: # Auth : GOTRUEJWTKEYS: ${JWTKEYS:-[]} # Realtime: APIJWTJWKS: ${JWTJWKS:-{"keys":[]}} # Storage : JWTJWKS: ${JWTJWKS:-{"keys":[]}} ############

# Legacy symmetric HS256 key JWTSECRET=generate using genkey:secret # Legacy symmetric API key (HS256-signed JWT) for anon role. ANONKEY=generate using genkey:anonsym # Legacy symmetric API key (HS256-signed JWT) for service role. SERVICEROLEKEY=generate using genkey:servicerolesym # Pre-signed ES256 JWT "API key" for anon role. ANONKEYASYMMETRIC=generate using genkey:anonasym # Pre-signed ES256 JWT "API key" for service role. SERVICEROLEASYMMETRIC=generate using genkey:serviceroleasym # Opaque API key for client-side use (anon role). SUPABASEPUBLISHABLEKEY=generate using genkey:client # Opaque API key for server-side use (servicerole). Never expose in client code. SUPABASESECRETKEY=generate using genkey:server # JSON array of signing JWKs (EC private + legacy symmetric). # Used by Auth. JWTKEYS=generate using genkey:keys # JWKS for token verification (EC public + legacy symmetric). # Used by PostgREST, Realtime, Storage to verify tokens. JWTJWKS=generate using genkey:jwks # Used by Realtime and Supavisor SECRETKEYBASE=generate using gentoken:48 # Used by Supavisor VAULTENCKEY=generate using genhex:16 # Used by Studio to access Postgres via postgres-meta PGMETACRYPTOKEY=generate using gentoken:24 # Used by Kong dashboard user DASHBOARDPASSWORD=generate using genhex:16

############ # [required for Supabase] - automatically set when auto-configure (AC=True) is enabled # Logs - Configuration for Supabase Analytics # Please refer to https://supabase.com/docs/reference/self-hosting-analytics/introduction ############

# Change vector.toml sinks to reflect this change # These cannot be the same value # Must be at least 32 characters; generate with 'openssl rand -base64 24' LOGFLAREPUBLICACCESSTOKEN=generate using gentoken:24 LOGFLAREPRIVATEACCESSTOKEN=generate using gentoken:24

############ # [required for Supabase S3] - automatically set when auto-configure (AC=True) is enabled # S3 - Supabase alternative storage ############

S3PROTOCOLACCESSKEYID=generate using genhex:16 S3PROTOCOLACCESSKEYSECRET=generate using genhex:32

############ # [required for Supabase and Langfuse] - automatically set when auto-configure (AC=True) is enabled # MinIO - authentication configuration - use OpenSSL openssl rand -hex 16 ############

MINIOROOTPASSWORD=generate using gen_hex:16

############ # [required for Flowise] - automatically set when auto-configure (AC=True) is enabled # Flowise - authentication configuration - use OpenSSL openssl rand -hex 16 ############

FLOWISEPASSWORD=generate using genhex:16

############ # [required for Neo4j] - automatically set when auto-configure (AC=True) is enabled # Neo4j admin username and password # The admin username must remain "neo4j". # Replace "password" with your chosen password. # Keep the "/" as a separator between the two. ############

NEO4JPASSWORD=generate using genhex:16 NEO4JAUTH=neo4j/${NEO4JPASSWORD}

############ # [required for Langfuse] - automatically set when auto-configure (AC=True) is enabled # Langfuse credentials # Each of the secret keys you can set to whatever you want, just make it secure! # For salt, secret and encryption key, use OpenSSL command specified above ############

CLICKHOUSEPASSWORD=generate using genhex:16 LANGFUSESALT=generate using genhex:16 NEXTAUTHSECRET=generate using gentoken:32 ENCRYPTIONKEY=generate using genhex:32

# Following settings are required for production.

# # ####### ##### #

############ # [required for production if using Authelia] # Automatically set when auto-configure (AC=True) is enabled # Authelia Config ############

AUTHELIASESSIONSECRET=generate using genhex:32 AUTHELIASTORAGEENCRYPTIONKEY=generate using genhex:32 AUTHELIAIDENTITYVALIDATIONRESE

…

Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: trevorsandy
• Source: trevorsandy/ai-suite
• License: Apache-2.0

Install and usage instructions live in the source repository linked above.