Docs • Self-hosted

Self-hosted deployment and operations overview

Self-hosting Mint Help gives your team control over infrastructure and data, but it also means taking ownership of updates, backups, security posture, and operational visibility.

  • 8 min read
  • Self-hosted
  • Mint Help guide

Typical production requirements

  • A Linux server or container environment sized for your conversation volume.
  • PostgreSQL and Redis for application data and job processing.
  • HTTPS with a valid certificate for all public endpoints.
  • SMTP or another email delivery method for notifications and email workflows.

Deployment options to evaluate

  • Linux VM deployments for simple operational control.
  • Docker-based deployments for portability and repeatable rollouts.
  • Kubernetes or managed platforms for larger or more complex environments.

Operational habits that matter

  • Keep backups tested, not just scheduled.
  • Apply upgrades deliberately and review release notes before major version changes.
  • Restrict exposed ports and keep reverse-proxy, database, and cache access private.
  • Monitor job queues, application errors, disk space, and email delivery health.

Security checklist

  • Use strong secrets and rotate them when needed.
  • Limit admin access and protect SSH or control-plane entry points.
  • Use HTTPS everywhere and secure upstream services behind the proxy.
  • Document restore steps so incidents are survivable, not theatrical.