Standalone Deployment

Standalone deployment means running ClawNex from the repository installer on one host, without a separate packaging and transfer workflow. Use this path for local macOS installs, macOS server installs, and simple source-based Linux installs.

For production Linux VPS deployments, use VPS Quickstart.

Local macOS Install

git clone https://github.com/ClawNexAi/clawnex.git ~/clawnex
cd ~/clawnex

bash install.sh

[1] Local  -- dashboard on localhost, launchd keep-alive
[2] Server -- public domain, Caddy, TLS on this Mac

open http://127.0.0.1:5001

macOS Server Install

Use this when a Mac is acting as the public ClawNex host.

bash install.sh --mode mac-server --domain qa.example.com

macOS server mode uses launchd for ClawNex services and Caddy for public HTTPS. The domain must already point to the Mac.

Service Management

The installer creates ClawNex service wrappers and the clawnex CLI when possible:

clawnex status
clawnex restart
clawnex logs

On macOS, the backing services are launchd agents:

launchctl list | grep clawnex

On Linux VPS, the backing services are systemd units:

sudo systemctl status clawnex-dashboard clawnex-litellm

Verify

curl -fsS http://127.0.0.1:5001/api/health && echo
curl -fsS http://127.0.0.1:4001/health/liveliness && echo

Development Mode

Use development mode only when changing ClawNex source code:

npm install
npm run dev

Development mode does not replace the installer. It does not provision Caddy, systemd, launchd, RBAC secrets, LiteLLM service management, or production build artifacts.