Linux Server Deployment

Nowledge Mem can run as a headless server on Linux machines without a GUI. Install the same .deb or .AppImage package, then manage everything from the command line.

System Requirements

Installation

curl -fsSL https://nowledge-co.github.io/community/apt/install.sh | sudo bash
sudo apt-get install nowledge-mem

# Install the package
sudo dpkg -i nowledge-mem_*.deb

# Fix any missing dependencies
sudo apt-get install -f

# Make executable
chmod +x Nowledge_Mem_*.AppImage

# Run once to extract the Python runtime
./Nowledge_Mem_*.AppImage --appimage-extract

# The nmem CLI is available after first run
# Location: ~/.local/bin/nmem

The .deb post-install script automatically:

• Extracts the bundled Python runtime
• Creates the nmem CLI at /usr/local/bin/nmem
• Configures the APT repository for automatic updates (if installed via APT)
• Sets up the desktop entry (ignored on headless servers)

Verify the CLI is available:

nmem --version

Quick Start

nmem serve

nmem serve --host 127.0.0.1 --port 8080

nmem license activate <license-key>        # Email is usually inferred from the key
nmem license status    # Verify activation
nmem license renew     # Refresh this device later if authorization expires

nmem models download
nmem models status     # Verify installation

nmem config provider set anthropic \
  --api-key sk-ant-xxx \
  --model claude-sonnet-4-20250514

nmem config provider test    # Verify connection

nmem config settings set backgroundIntelligence true
nmem config settings set autoDailyBriefing true

nmem status

Running as a systemd Service

For production deployments, use nmem service install to set up a background systemd service that automatically starts on boot:

# Install, enable, and start
sudo nmem service install

# If you are running from a root shell or automation, set the real Linux user explicitly
sudo nmem service install --service-user <linux-user>

# Custom host/port
sudo nmem service install --host 0.0.0.0 --port 8080

# No root required
nmem service install --user

sudo chown -R <linux-user>:<linux-user> ~/.config/co.nowledge.mem.desktop
sudo chown -R <linux-user>:<linux-user> ~/.local/share/NowledgeGraph

Managing the Service

nmem service status           # Show service status
nmem service logs -f          # Follow service logs
nmem service stop             # Stop the service
nmem service start            # Start the service
nmem service uninstall        # Stop, disable, and remove

serve vs service

Data Location

All data (graph database, search index, version metadata) is stored in a single directory:

~/.local/share/NowledgeGraph/
├── nowledge_graph_v2.db/   # KuzuDB graph database
├── search_index/           # LanceDB vector + BM25 index
└── db_version.json         # Schema version tracking

The server resolves this path automatically using XDG_DATA_HOME (defaults to ~/.local/share). To use a custom location, set the NOWLEDGE_DB_PATH environment variable before starting the server:

export NOWLEDGE_DB_PATH=/mnt/data/NowledgeGraph/nowledge_graph_v2.db
nmem serve

Remote Access

By default, nmem serve listens on all interfaces and requires an API key for connections from other machines. The key is auto-generated on first start and printed to the console.

Once the server is reachable, connect clients through the highest-level surface they support: native integrations first, then plugin settings or nmem config, and only then direct MCP when no better dedicated path exists.

# On the server
nmem serve
# Prints: API Key: nmem_...

Install the standalone CLI on remote machines:

pip install nmem-cli
# or
uv pip install nmem-cli

Then configure the connection. You can use a config file (persistent) or environment variables (per-session):

{
  "apiUrl": "http://your-server:14242",
  "apiKey": "nmem_..."
}

export NMEM_API_URL=http://your-server:14242
export NMEM_API_KEY="nmem_..."

nmem status
nmem m search "query"

Priority: CLI flags > env vars > config file > defaults.

To disable authentication (not recommended for production):

nmem serve --no-auth

Interactive TUI

For an interactive terminal experience, use the TUI:

nmem tui

The TUI provides a full settings management interface including license activation, LLM configuration, and knowledge processing toggles.

It also includes Access Anywhere controls in Settings, so you can configure Quick link / stable Cloudflare account mode directly from terminal workflows.
Full guide: Access Mem Anywhere.

If your server network blocks UDP/QUIC and Access Anywhere fails to come online, force Cloudflare transport to HTTP/2 before restarting Mem:

export TUNNEL_TRANSPORT_PROTOCOL=http2

Configuration Reference

Environment Variables

CLI Commands Summary

Troubleshooting

Missing data after upgrade

Older versions (before 0.7) stored the database in ./data/ relative to the directory you ran nmem serve from. The current version stores data in the standard location (~/.local/share/NowledgeGraph/). If your memories disappeared after upgrading, your data is likely still on disk, just in the old location.

find / -name "nowledge_graph*.db" -type d 2>/dev/null

# Stop the server first
nmem service stop        # if using systemd
# or Ctrl+C              # if running in foreground

# Create the standard directory if needed
mkdir -p ~/.local/share/NowledgeGraph

# Move your database and related files
mv /old/path/data/nowledge_graph*.db* ~/.local/share/NowledgeGraph/
mv /old/path/data/search_index ~/.local/share/NowledgeGraph/  2>/dev/null
mv /old/path/data/db_version.json ~/.local/share/NowledgeGraph/  2>/dev/null

# Restart the server
nmem serve               # or: nmem service start

nmem m search "test"     # Search for your memories
nmem status              # Check server health

Next Steps

• CLI Reference - Complete CLI documentation
• API Reference - REST API endpoints
• Integrations - Connect with AI tools