RackMon
Security

Built so your data never leaves your hands.

RackMon is self-hosted by design. It runs entirely on your infrastructure, and its security model assumes you — not us — are in control.

Self-hosted, no phone-home

Secrets encrypted at rest

Device and SMTP credentials are encrypted with AES-256-GCM using a master key you provide (RACKMON_MASTER_KEY), which is kept out of the database. Session tokens are signed with a separate secret (RACKMON_JWT_SECRET).

Safe by default in production. With RACKMON_ENVIRONMENT=production, RackMon refuses to start while any security-sensitive value is still on its insecure development default — so a misconfigured instance fails closed instead of running exposed.

Authentication & access control

License keys are offline and tamper-evident

Pro/Enterprise licenses are Ed25519-signed tokens verified offline inside your instance against an embedded public key. There is no license server to call and nothing to leak. The private signing key lives only on our side and is never shipped in the product image.

Transport & deployment

Payments

We never see or store your card details. Checkout is handled by our Merchant of Record, Lemon Squeezy, which processes payments and is PCI-compliant.

Reporting a vulnerability

Found a security issue? Please email rackmon.software@gmail.com with details and steps to reproduce. Give us a reasonable window to fix it before public disclosure — we'll acknowledge your report and keep you posted. We're grateful for responsible disclosure.

← Back to RackMon