Skip to main content

System Requirements

NeoMind runs on desktop (macOS / Windows / Linux) or servers. Below are the requirements for each deployment mode.

Package Sizes & Resource Footprint

Download Sizes (GitHub Releases)

ArtifactSizeNotes
Server binary (tar.gz)~27–30 MBneomind + neomind-extension-runner bundled; per-platform
Web frontend (tar.gz)~5.3 MBStatic assets (HTML/JS/CSS), served by the backend
macOS Desktop (.dmg)~45 MBTauri app — bundles backend + frontend + system WebView
Windows Desktop (.msi)~44 MB
Linux Desktop (.deb)~48 MB
Linux AppImage~117 MBFully self-contained — includes all system libraries

Total server footprint: ~35 MB on disk (binary + web assets). No Docker layers, no pip/npm runtime — a single statically compiled binary plus static files.

Runtime Resource Usage

The main process embeds the API server, MQTT broker, redb storage, and rule engine in one binary. Extensions run in separate processes.

ComponentRAM (typical)Notes
Main process50–150 MBAxum + MQTT broker + redb. Scales with device count and telemetry volume.
Extension runner10–50 MB per extensionML models are lazy-loaded (first command → load → stay resident). A YOLOv8n model adds ~50 MB when active.
Telemetry storagegrows with dataredb file at data/telemetry.redb. ~1 KB per data point. Retention is configurable.
No external dependencies

NeoMind does not require PostgreSQL, Mosquitto, Redis, or any other external service. The only optional external dependency is an LLM — either Ollama running locally, or a cloud API key.

Download the installer from GitHub Releases.

OSArchitectureFormat
macOSApple Silicon (arm64).dmg
Windowsx86_64.msi / .exe
Linuxx86_64 / arm64.AppImage / .deb

Official pre-built packages cover only the architectures above. For other platforms (e.g. macOS Intel / Windows ARM), build from source.

Minimum hardware:

  • CPU: 2 cores (4 recommended)
  • RAM: 4 GB baseline; 8 GB+ recommended when running a local LLM
  • Disk: 1 GB install + data storage (see below)

Server Deployment

Supported Operating Systems

  • Linux: Ubuntu 20.04+ / Debian 11+ / CentOS 8+ / other mainstream distros (x86_64 / arm64)
  • Edge devices (arm64): NVIDIA Jetson (Orin series, with the CUDA runtime auto-bootstrapped), RK3576, and other aarch64 SBCs — arm64 builds are available for both the server and extensions
  • macOS: 12 Monterey+ (development or small-scale deployment)
  • Windows: Windows 10 / Server 2019+ (via WSL2 or native)

Hardware Recommendations

ScenarioCPURAMDiskNotes
Light (rules only / cloud LLM)2 cores2 GB10 GBNo local model
Recommended (local LLM)4 cores8 GB20 GB+ SSDRuns 4B models like Qwen3.5-4B; the recommended MiniCPM5-2B (1.5GB) runs from 3 GB
Multi-device / vision pipeline8 cores16 GB50 GB+ SSDMulti-stream video + YOLO/OCR extensions

GPU: Not required. Local LLM and vision inference run via Ollama (CPU mode); when a GPU is present, Ollama auto-accelerates.

Network Ports

PortProtocolPurposeConfigurable
9375HTTPBackend API + Web UI (default neomind-cli serve port)--port / PORT env var
1883MQTTEmbedded MQTT broker (device onboarding)Config file
80 / 443HTTP(S)Reverse proxy (optional, nginx)nginx config

For production, use an nginx reverse proxy and expose only 80/443 externally; keep 9375 / 1883 on the internal network.

Docker Deployment Requirements

ItemRequirement
Imagecamthink/neomind:latest (multi-arch amd64 + arm64, built per release)
Ports9375 (HTTP API + Web UI), 1883 (MQTT)
Data persistencevolume neomind-data (mounted at /app/data)
Local LLMthe image bundles the llama.cpp runtime and a default curated model (LFM2.5-2.6B, swappable/skippable via build arg); other models can be downloaded on demand in the wizard (reserve 4-8 GB disk + RAM)

See Install & Setup — Docker.

Edge Devices

  • NVIDIA Jetson (Orin series): CUDA runtime auto-bootstrapped; budget 8 GB+ VRAM for vision pipelines (YOLO / DeepStream)
  • RK3576 and other aarch64 SBCs: prefer small-tier models for CPU-only inference
  • Memory-constrained boxes: use a 2-3B local model and run vision inference on a separate machine

Runtime Dependencies

Server deployment requires no manual dependency installation — the install script downloads statically compiled binaries. Optional components:

  • None (default): The Docker deployment image ships with the llama.cpp runtime and curated official models — a one-click download in the wizard gives you a local LLM with nothing extra to install
  • Ollama (optional, if you already have it): for local LLM inference. Install at ollama.com. Pull a model the first time you configure an LLM backend, e.g. ollama pull qwen3.5:4b
  • Docker (optional): one-line deploy via docker compose up -d
  • nginx (optional): production reverse proxy + static frontend hosting

Data Storage

NeoMind uses embedded storage — no external database is needed. The data directory defaults to data/ and contains:

File / DirPurpose
telemetry.redbTime-series telemetry (all device metrics)
sessions.redbUser sessions
devices.redb / dashboards.redb / rules.redb / agents.redbPer-domain primary data
messages.redbNotification delivery records
memory/Agent memory files (Markdown)
skills/Skill definitions (YAML + Markdown)
extensions/Extension binaries and config
logs/Runtime logs

The data directory can be customized via env vars or install script params (see Install & Setup).

Development Environment

Building from source requires:

ToolVersionPurpose
Rust1.85+ (toolchain pinned to 1.92.0)Backend
Node.js20+Frontend
OllamaanyLocal LLM (or connect a cloud model)
# Backend
cargo build && cargo test && cargo run -p neomind-cli -- serve

# Desktop / frontend
cd web && npm install && npm run tauri:dev

See Developer Guide for details.

LLM Backend Requirements

NeoMind supports multiple LLM backends in two deployment modes:

  • Local: Ollama (recommended, qwen3.5:4b model). The host needs enough RAM to load the model.
  • Cloud: OpenAI / Anthropic / Google / xAI / Qwen / DeepSeek / GLM / MiniMax and other OpenAI-compatible endpoints. Requires an API key and outbound network access.

See Configure LLM Backend for setup.


Last updated: 2026-09-08