Open-Source Observability · roxy-wi

roxy-wi

Roxy-WI is a Python-based web GUI for managing HAProxy, Nginx, Apache, and Keepalived load balancers and reverse proxies from a single dashboard. It provides configuration management, monitoring, alerting, and multi-server orchestration with role-based access control and backup capabilities.

Talk to DEV.co Discuss Implementation

Source: GitHub — github.com/roxy-wi/roxy-wi

1.8k

GitHub stars

279

Forks

Python

Primary language

Apache-2.0

License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

Field	Value
Repository	roxy-wi/roxy-wi
Owner	roxy-wi
Primary language	Python
License	Apache-2.0 — OSI-approved
Stars	1.8k
Forks	279
Open issues	7
Latest release	v8.2.6.5 (2026-05-15)
Last updated	2026-05-15
Source	https://github.com/roxy-wi/roxy-wi

What roxy-wi is

Web-based management interface written in Python that centralizes control of HAProxy, Nginx, Apache, and Keepalived instances via SSH/API. Supports SQLite or MySQL backends, role-based access, config versioning, multi-server sync, and integrates with external alerting (Telegram, Slack, Email, PagerDuty, Mattermost) and monitoring tools.

Quickstart

Get the roxy-wi source

Clone the repository and explore it locally.

terminalbash

1git clone https://github.com/roxy-wi/roxy-wi.git2cd roxy-wi3# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Multi-server load balancer fleet management

Manage configurations and state across dozens of HAProxy/Nginx/Apache instances from one interface, with config sync, change tracking, and rollback capabilities.

High-availability and failover orchestration

Roxy-WI supports Keepalived integration and HA topologies (master-slave), making it suitable for environments requiring automatic failover and redundancy.

Operational teams lacking CLI expertise

GUI-driven interface with mobile support, multi-user roles, and drag-and-drop HAProxy workflow visualization lowers the barrier for non-CLI-native operations teams.

Implementation considerations

Deploy Roxy-WI on a dedicated, stable server (EL7+, Ubuntu x86_64). Plan for database persistence (SQLite suitable for small teams; MySQL for scale).
Pre-generate SSH keys or implement centralized key management for passwordless authentication to managed load-balancer nodes.
Configure role-based access early (admin, operator, viewer roles) to match your team structure and compliance requirements.
Test config changes in a staging cluster first; while rollback is available, invalid HAProxy/Nginx syntax can bring down production frontends.
Plan backup and disaster recovery for the Roxy-WI database; loss of config history and audit logs is operationally costly.

When to avoid it — and what to weigh

Kubernetes-native environments — Roxy-WI targets traditional VMs and bare metal. If your load balancing is Kubernetes-based, consider Ingress controllers or service mesh solutions instead.
Zero-trust or air-gapped deployments — Roxy-WI requires outbound connectivity for external alerting (Slack, PagerDuty, Telegram) and relies on SSH/HTTP for management. Highly restricted networks may face integration friction.
Minimal operational overhead required — Deploying and maintaining Roxy-WI itself (SQLite/MySQL database, web service, SSH key management) introduces operational complexity. Simple load-balancer-only setups may not justify this.
Scripted, infrastructure-as-code-first approach — Roxy-WI is GUI-centric and relies on state stored in a database. Teams invested in Terraform, Ansible, or declarative configs may find the stateful model misaligned with their philosophy.

License & commercial use

Licensed under Apache License 2.0 (Apache-2.0), an OSI-approved permissive license permitting commercial use, modification, and distribution with minimal restrictions (must retain license/notice, changes must be documented).

Apache 2.0 explicitly permits commercial use without royalties or license fees. No dual licensing or proprietary restrictions mentioned in the provided data. Confirm with upstream that no additional commercial license agreement is required for your deployment model; see official docs at roxy-wi.org for clarity.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

Signal	Assessment
Maintenance	Active
Documentation	Adequate
License clarity	Clear
Deployment complexity	Moderate
DEV.co fit	Good
Assessment confidence	High

Security considerations

Roxy-WI centralizes load-balancer management and SSH keys; the web interface and database become high-value targets. Default credentials (admin/admin on demo) must be changed immediately. HTTPS and Let's Encrypt support mentioned; verify in-transit encryption for config pushes and alerts. SSH key storage on the Roxy-WI host requires hardened OS-level access controls. No mention of audit logging, secrets rotation, or vulnerability disclosure policy in provided data. Code review recommended before production in security-critical environments.

Alternatives to consider

Terraform + HAProxy/Nginx Ansible playbooks

Infrastructure-as-code approach; version-controlled, auditable, and integrates with CI/CD. No central web UI, but suits teams favoring declarative config and scripted deployments.

NGINX Controller (commercial) or Kubernetes Ingress

Enterprise load-balancing with native multi-cluster support, API-first design, and SaaS options. Better fit for cloud-native and Kubernetes environments.

Lightweight, direct control without additional web UI overhead. Suitable for small, stable deployments where change frequency is low and team has strong CLI skills.

Software development agency

Build on roxy-wi with DEV.co software developers

Deploy Roxy-WI to unify control over your HAProxy, Nginx, and Apache fleet. Start with a free demo at demo.roxy-wi.org (login: admin/admin) or install on EL7+/Ubuntu. Check roxy-wi.org for detailed setup guides and join the Telegram community.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

huginn swetrix goaccess

Related on DEV.co

Explore the category and the services that help you build with it.

Open-Source Observability DevOps & Infrastructure Cloud Deployment & Management Talk to DEV.co

roxy-wi FAQ

Can I manage load balancers across multiple data centers or cloud regions?

Yes. Roxy-WI supports multiple servers and groups. SSH connectivity between the Roxy-WI host and managed nodes is required; ensure low-latency, reliable network paths to avoid management delays or timeouts.

What happens if the Roxy-WI server goes down?

The managed load balancers (HAProxy, Nginx, etc.) continue running with their current config. You lose the GUI, monitoring, and alerting until Roxy-WI is restored. Config changes cannot be pushed until recovery. Regular backups of the Roxy-WI database are critical.

Does Roxy-WI support SSL/TLS termination configuration?

Yes. It supports SSL configuration (including Let's Encrypt integration) and manages HAProxy/Nginx SSL settings via the GUI, but you must supply certificates or use the Let's Encrypt integration.

Is there a programmatic API, or is it GUI-only?

Not mentioned in the provided data. Appears to be primarily GUI-driven. Confirm with official documentation if REST API or CLI tools exist for automation.

Software developers & web developers for hire

Adopting roxy-wi is usually one piece of a larger software development effort. As a software development agency, DEV.co provides software development services and web development expertise — pairing senior software developers and web developers with your team to design, build, and operate open-source observability software in production.

Ready to simplify load balancer management?

Talk to DEV.co Schedule a Consultation