Self-Hosting the RMM Stack

Every product runs on your own hardware. No vendor lock-in, no telemetry home calls, no license server. The standard deployment target is a single VPS (4 vCPU / 8 GB RAM) running Docker + nginx.

Reference topology

                 ┌─────────────────────────────────────────┐
   HTTPS 443 ──▶ │ nginx (TLS termination, rate limiting)  │
                 └──────┬──────────────┬──────────────┬────┘
                        │              │              │
                 ┌──────▼─────┐ ┌──────▼──────┐ ┌─────▼──────┐
                 │ rmi-backend│ │ degenfeed   │ │ pryscraper │  (Docker)
                 │ :8000      │ │ :3000       │ │ :8080      │
                 └──────┬─────┘ └──────┬──────┘ └─────┬──────┘
                        │              │              │
                 ┌──────▼──────────────▼──────────────▼──────┐
                 │ Postgres · Redis · Qdrant (vectors)       │
                 └───────────────────────────────────────────┘

Per-product guides

Product	Guide
RMI backend	RMI deployment
DegenFeed	DegenFeed deployment
Pry	Pry deployment
WalletPress	WalletPress deployment
rugmunchbot	rugmunchbot deployment
RugBrain	RugBrain installation
rmi-mcp-x402	rmi-mcp-x402 installation
x402-coffer	x402-coffer installation

Baseline requirements

• Docker Engine 24+ and Docker Compose v2
• Postgres 15+, Redis 7+, Qdrant 1.9+ (only where a product needs them)
• TLS via Let's Encrypt (acme.sh or certbot) — never self-signed in production
• Secrets in a secret manager or environment injection — never in .env files committed to git

warning

Public-facing deployments: enable rate limiting, CORS allow-lists, and follow the security operations guide. Sample configs in each repo's docker-compose.yml are development defaults, not production-ready.