Why host Fluxer rather than stay on Discord
Discord is a hosted platform: your members, message history and moderation roles reside on servers you do not control. Fluxer adopts the inverse model — AGPL-3.0, over 10,000 GitHub stars since January 2026, no third party holds the keys to your instance.
What you gain by self-hosting Fluxer
- Complete data sovereignty — messages, files and audit logs stay on your VPS, in your chosen jurisdiction.
- Unilateral moderation — bans, roles and permissions are defined by your administrators.
- Full history accessible — no message cap, unlike SaaS free plans that archive or truncate history.
- Private network webhook integration — your bots and CI/CD alerts call the Fluxer API within your VLAN.
- Predictable cost — the operating cost is the VPS, regardless of community size.
- Updates under your control — you choose when to upgrade, after validating in pre-production.
- AGPL-3.0 licence — the code openness prevents enshittification: if maintainers change course, the community can fork.
Requirements: what you need before starting
Fluxer is written in Go (backend) and React (interface). The recommended stack uses Docker and Docker Compose. Plan for 2 vCPU and 2 GB RAM for a light community (up to 100 simultaneous active members). For 500 active members with audio calls, aim for 4 vCPU and 4 GB RAM. Docker Engine 24+ and Docker Compose v2 are the only software requirements.
Docker Compose deployment
Retrieve the production Compose file and configure the .env with FLUXER_SECRET_KEY, FLUXER_DOMAIN and POSTGRES_PASSWORD. Launch with docker compose -f docker-compose.prod.yml up -d. Fluxer listens on port 3000 locally; the reverse proxy handles port 443 and TLS.
Reverse proxy and TLS certificates: nginx or Caddy
TLS encryption is handled by your reverse proxy, not by Fluxer itself. With Caddy, add one block and it negotiates Let's Encrypt automatically. With nginx, configure proxy_pass and let Certbot manage the certificate — renewable every 60 days via systemd timer with no manual intervention.
Updating Fluxer without breaking the instance
Docker isolation is the key technical argument against the manual update objection. Pin a version tag in your production Compose, update with docker compose pull && up -d, and roll back in one command by reverting the tag. Never use latest in production.
Who should manage the machine?
Self-hosting Fluxer transfers operational responsibility. This is real but manageable — Docker isolates the app, the reverse proxy handles TLS, and monitoring alerts install in minutes. ServOrbit's optional VPS administration service covers OS updates, security patches and proactive monitoring — available as an add-on, not included by default.
Which VPS plan to choose for Fluxer?
2 vCPU / 2 GB RAM — minimum for a light community (under 100 simultaneous active members). 4 vCPU / 4 GB RAM — recommended for 500 active members or a community with regularly occupied voice channels. Compare plans on the ServOrbit VPS Cloud page.
Fluxer, Mattermost or Matrix: which to choose?
Fluxer targets Discord-native communities. Mattermost suits structured professional teams — see hosting Mattermost on your own VPS. Matrix is the choice when federation and end-to-end encryption are top priorities — see hosting Matrix (Synapse) and Element. For Slack migrations: Migrating from Slack to Mattermost or Rocket.Chat.
Conclusion
Fluxer offers a credible exit from the Discord ecosystem. Docker isolation reduces operational complexity: updates are isolated, rollback is immediate, and the reverse proxy handles TLS with no manual intervention.
ServOrbit VPS administration option is available for teams that want to delegate the system layer without losing data sovereignty. Compare plans at ServOrbit VPS Cloud.
VPS Cloud ServOrbit
Compare plans at ServOrbit VPS Cloud.
