Deployment

TrenchTools is designed to run locally on your machine. The UI builds to static files that open in your browser — no cloud server required.

Quick Start (Local)

git clone https://github.com/natebag/Trenchtools.git
cd Trenchtools
pnpm install
pnpm dev

This starts the dashboard at http://localhost:3000. Your wallets and trade history are stored in your browser's localStorage — nothing leaves your machine.

Building for Production

npx turbo run build --filter=@trenchtools/ui --force
# Output: packages/ui/dist/

The dist/ folder contains a fully static site (HTML + JS + CSS). You can serve it with any static file server:

npx serve packages/ui/dist

Self-Hosting on a VPS

If you want to access TrenchTools from multiple devices or keep it running 24/7 (for volume boosting, bot groups, etc.), deploy to a VPS.

Any VPS (DigitalOcean, Hetzner, etc.)

1. Clone the repo on your server
2. Install Node.js 20+ and pnpm
3. Build and serve:

pnpm install
npx turbo run build --filter=@trenchtools/ui --force
npx serve packages/ui/dist -l 3000

4. (Optional) Put behind nginx or Caddy for HTTPS

Docker

FROM node:20-alpine AS build
RUN npm install -g pnpm
WORKDIR /app
COPY . .
RUN pnpm install
RUN npx turbo run build --filter=@trenchtools/ui --force

FROM nginx:alpine
COPY --from=build /app/packages/ui/dist /usr/share/nginx/html
EXPOSE 80

docker build -t trenchtools .
docker run -p 3000:80 trenchtools

Railway / Render / Fly.io

Any PaaS that supports static sites or Docker works:

1. Connect your GitHub fork
2. Set build command: pnpm install && npx turbo run build --filter=@trenchtools/ui --force
3. Set output directory: packages/ui/dist
4. Deploy

Environment Variables

The self-hosted dashboard runs entirely in the browser. API keys are entered in the Settings panel and stored in your browser's localStorage.

Optional build-time variables:

# Override the default Solana RPC (users can also set this in Settings)
VITE_DEFAULT_RPC_URL=https://api.mainnet-beta.solana.com

# EVM RPCs (free defaults are built-in)
# BSC_RPC_URL=https://bsc-dataseed.binance.org
# BASE_RPC_URL=https://mainnet.base.org

No server-side secrets needed

Unlike hosted platforms, self-hosted TrenchTools keeps your API keys in your browser. There's no backend server that needs API keys configured.

MCP Server

The MCP server (packages/mcp) runs as a local process alongside Claude Desktop or any MCP-compatible AI agent. See MCP Server Setup for installation.