# Luminati Proxy Manager: a local proxy in front of a residential IP pool

> The open source manager for Bright Data's proxy network, running as a local HTTP and HTTPS proxy that rotates, balances and monitors traffic. It ships as an npm package, a Windows installer and a container image.

**luminati-io/luminati-proxy** — Luminati HTTP/HTTPS Proxy manager

- Repository: https://github.com/luminati-io/luminati-proxy
- Website: https://luminati.io/
- Stars: 824 · Forks: 206
- Language: JavaScript
- License: not declared
- Published: 2026-10-20 · Updated: 2026-10-20 · Language: en
- Canonical page: https://hysenlabs.com/projects/luminati-io-luminati-proxy

## One local proxy endpoint in front of a global proxy network

Proxy Manager is a forward HTTP and HTTPS proxy that runs on your side and forwards traffic to proxies around the world, with the README listing the jobs it does as accelerating, compressing, rotating, distributing, managing, monitoring, reporting, logging and debugging that traffic. Concretely, it lets you drive Bright Data residential IPs and Bright Data static IPs through a single local address, so the applications you point at it do not each need to know the credentials or the routing rules. The feature list spells out what that buys: a connection pool for faster response time, easy setup of multiple configurations through a simple web interface, statistics, automatic IP rotation every X requests, load balancing across multiple super proxies, SSL analysis using a self-signed certificate, and a SOCKSv5 proxy. The tool requires a Bright Data account, and the README directs bug reports to the account manager or the help centre.

## Four install routes and a strict Node version

Windows users download an installer from the releases page. On Linux and macOS the README offers a setup script that pipes the download straight into bash:

```sh
wget -qO- https://brightdata.com/static/lpm/luminati-proxy-latest-setup.sh | bash
```

A manual route is documented as well, and it is specific about versions. Node.js should be at least 24.13.0 and npm at least 6.14.6, and the package installs globally:

```sh
sudo npm install -g @luminati-io/luminati-proxy
```

If your npm is newer than 6 the README says to add the --legacy-peer-deps flag, and there is a third variant for installs from China where the default npm registry is unavailable, using the alternative registry at r.cnpmjs.org. Upgrades use the same npm command or a built-in CLI call:

```sh
proxy-manager --upgrade
```

Specific older versions can be installed from the releases page by putting the version number after the package name. The hardware expectations are modest, with 2GB RAM, one CPU and a 3GB disk as the minimum and 4GB RAM with two CPUs and an SSD recommended.

## Dropin mode is the migration path from plain super proxies

The feature that matters most for an existing setup is dropin mode. When a proxy runs in dropin mode it behaves exactly like the existing super proxies, and you do not sign in through the administrative interface to make requests. Instead, the proxy username and password are supplied with each request to the proxy server. The mode is enabled by default, and the README positions it as an easy replacement when migrating from the regular super proxy to Proxy Manager. It is turned off with a single flag:

```sh
proxy-manager --no-dropin
```

Full documentation for the dropin request API is in the account area of the Bright Data site rather than in the repository. First run starts the app with no arguments, and the browser is then pointed at the local admin interface on port 22999 to enter credentials and configure proxies:

```sh
proxy-manager
```

The app also runs in the background with proxy-manager --daemon.

## The flag surface exposes routing, targeting and TLS inspection

The complete option list is printed by proxy-manager --help, and it reads like a configuration file in disguise. The proxy port is set with -p, and the --multiply option repeats a port definition a given number of times, with --multiply_users and --users to generate them per user. Target selection uses --country, --state and --city, while --zone and --password name the Bright Data zone, defaulting to static. The upstream super proxy is set with --proxy, defaulting to brd.superproxy.io on port 44445, with --proxy_connection_type and --proxy_retry governing how the manager talks to it and how often it retries. TLS handling has three switches, --ssl to enable analysis, --tls_lib to pick the library with a default of open_ssl, and --insecure for insecure hosts. An --av_check flag enables an antivirus check, and --iface binds the listener to a particular interface.

## The container image bundles Chrome for the puppeteer path

The Dockerfile in the repository root builds on node:24.13.0-bookworm and sets PUPPETEER_SKIP_CHROMIUM_DOWNLOAD so that the bundled browser is used instead of a downloaded one. The image installs the usual Chromium runtime libraries, then fetches the Google Chrome stable package so the bundled version of Chromium that Puppeteer installs can run, with fonts for major charsets including Chinese, Japanese, Arabic, Hebrew and Thai. Proxy Manager itself is installed globally with npm and then reinstalled without dev dependencies, the environment variable DOCKER=1 marks the environment for CLI output, and the default command is the luminati binary showing its help. The repository is a JavaScript project with webpack configuration for development and production, a src/ tree, a www/ directory for the admin interface, and a Dockerfile at the root.

## Frequent releases, four binary names, and no stated licence

Release activity is high. The tagged versions include v1.670.998 on 2026-09-23, v1.676.810 on 2026-10-11 and v1.679.135 on 2026-10-19, and the last push was on 2026-10-19, so the project is being worked on continuously. The Windows build is produced with electron-builder as an NSIS installer, signed with a Bright Data certificate and timestamped against DigiCert servers, and the same binary is published to a static location that the README's own download links point at. The package publishes four command names, proxy-manager, pmgr, luminati-proxy and luminati, all mapping to the same bin/index.js entry point. What is missing from all of this is a licence: the repository listing records no licence and the root holds no LICENSE file, so the terms under which the source may be reused are not stated by the project, which is unusual for a tool published in full.

## Conclusion

The Proxy Manager suits an organisation already paying for Bright Data's IP network that wants one local endpoint to route through it, add rotation or SSL inspection, and watch the traffic from a browser interface. It does not suit anyone looking for a general purpose open proxy, since the tool only works with a paid account, and the README says so plainly. Before deploying it, read the terms of the Bright Data account you attach, and note that the repository declares no licence, so the code is visible but not obviously reusable.

## FAQ

### What does the Luminati Proxy Manager do?

It is a forward HTTP and HTTPS proxy that runs on your side and forwards traffic to proxies around the world, accelerating, compressing, rotating, distributing, managing, monitoring, reporting, logging and debugging that traffic. It requires a Bright Data account.

### How do I install the Luminati Proxy Manager on Linux or macOS?

Run the setup script with wget or curl piped to bash, or install the package manually with sudo npm install -g @luminati-io/luminati-proxy. The README asks for Node.js 24.13.0 or later and npm 6.14.6 or later, and to add --legacy-peer-deps on newer npm versions.

### What is dropin mode in the Luminati Proxy Manager?

In dropin mode the proxy behaves exactly like the existing super proxies, and the proxy username and password are provided with each request instead of signing in through the admin interface. It is enabled by default and can be disabled with proxy-manager --no-dropin.

### Where is the Luminati Proxy Manager admin interface?

After the first run, point a browser at http://127.0.0.1:22999 to set up credentials and configure the proxies.

### Can the Luminati Proxy Manager target a specific country?

Yes. The command line options include --country, --state and --city for target selection, along with --zone and --password to name the Bright Data zone.

## Sources

- [Issues](https://github.com/luminati-io/luminati-proxy/issues)
- [luminati-io/luminati-proxy on GitHub](https://github.com/luminati-io/luminati-proxy)
- [Project website](https://luminati.io/)
- [README](https://github.com/luminati-io/luminati-proxy/blob/master/README.md)
- [Releases](https://github.com/luminati-io/luminati-proxy/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/luminati-io-luminati-proxy