sysown/proxysql
sysown/proxysql sits at 7.0k stars on GitHub, written primarily in C++. High-performance proxy for MySQL and PostgreSQL
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
Snapshot
Top contributors
Show top contributors

Table of Contents
- Introduction
- Useful links
- Getting started
- Installation
- Ubuntu / Debian
- Red Hat / CentOS
- Amazon Linux
- Almalinux
- OpenSUSE
- FreeBSD
- Service management
- Starting ProxySQL
- Stopping ProxySQL
- Restarting ProxySQL
- Reinitializing ProxySQL
- Upgrades
- How to check the ProxySQL version
- Configuring ProxySQL via the admin interface
- Configuring ProxySQL through the admin interface
- Configuring ProxySQL through the config file
- Installation
Introduction
ProxySQL is a high-performance, high-availability, protocol-aware proxy for MySQL and its forks (such as Percona Server and MariaDB), as well as PostgreSQL. All the while getting the unlimited freedom that comes with a GPL license.
Its development is driven by the lack of open source proxies that provide high performance.
Useful links
- Official website
- Subscriptions and Support
- Documentation
- DockerHub Repository
- Benchmarks and blog posts
- Forum
Getting started
Installation
Released packages can be found here: https://github.com/sysown/proxysql/releases
Just download a package and use your systems package manager to install it:
wget https://github.com/sysown/proxysql/releases/download/v3.0.4/proxysql_3.0.4-ubuntu24_amd64.deb
dpkg -i proxysql_3.0.4-ubuntu24_amd64.deb
Generic Linux binaries (tarball)
Distribution-agnostic .tar.gz builds are also published on the
releases page — handy for hosts
where a .deb/.rpm is inconvenient (any glibc 2.34+ Linux, amd64 or
arm64). ProxySQL embeds the pinned OpenSSL 3.5.9 libraries and does not need
host OpenSSL shared libraries; GnuTLS remains a dynamic runtime dependency.
This vendoring is not a FIPS compliance claim—future FIPS module support is
tracked separately in issue #6116.
Grab the proxysql-<version>-linux-<arch>.tar.gz asset,
verify its checksum, and extract:
sha256sum -c proxysql-<version>-linux-amd64.tar.gz.sha256
tar xzf proxysql-<version>-linux-amd64.tar.gz
The archive contains bin/proxysql, a sample etc/proxysql.cnf, the systemd/
units, and helper tools. The v4.0 build additionally includes runtime plugins
for MySQL X, GenAI, and the real
MySQL Router compatibility foundation. The
Router plugin is distinct from the MySQL X protocol plugin and is not yet
included in release packages; source builds install
proxysql_mysql_router.so under /usr/lib/proxysql/plugins/.
See AWS locality-aware backend selection for
the optional external-provider contract and MySQL configuration controls.
Building ProxySQL from source needs nothing beyond a normal git clone:
the pinned OpenSSL source archive is vendored directly in git. Verify it
before building dependencies:
deps/libssl/verify-source.bash
See the vendored OpenSSL maintenance guide for source verification, recovery, and the supported patch-update procedure from issue #6115.
Alternatively you can also use the available repositories:
Ubuntu / Debian:
Adding repository:
apt-get update && apt-get install -y --no-install-recommends lsb-release wget apt-transport-https ca-certificates
wget -nv -O /etc/apt/trusted.gpg.d/proxysql-3.0.x-keyring.gpg 'https://repo.proxysql.com/ProxySQL/proxysql-3.0.x/repo_pub_key.gpg'
echo "deb https://repo.proxysql.com/ProxySQL/proxysql-3.0.x/$(lsb_release -sc)/ ./" | tee /etc/apt/sources.list.d/proxysql.list
Installing:
apt-get update
apt-get install proxysql OR apt-get install proxysql=version
Red Hat / CentOS:
Adding repository:
cat > /etc/yum.repos.d/proxysql.repo << EOF
[proxysql]
name=ProxySQL YUM repository
baseurl=https://repo.proxysql.com/ProxySQL/proxysql-3.0.x/centos/\$releasever
gpgcheck=1
gpgkey=https://repo.proxysql.com/ProxySQL/proxysql-3.0.x/repo_pub_key
EOF
Installing:
yum install proxysql OR yum install proxysql-version
Amazon Linux:
Adding repository:
cat > /etc/yum.repos.d/proxysql.repo << EOF
[proxysql]
name=ProxySQL YUM repository
baseurl=https://repo.proxysql.com/ProxySQL/proxysql-3.0.x/centos/8
gpgcheck=1
gpgkey=https://repo.proxysql.com/ProxySQL/proxysql-3.0.x/repo_pub_key
EOF
Installing:
yum install proxysql OR yum install proxysql-version
Almalinux:
Adding repository:
cat > /etc/yum.repos.d/proxysql.repo << EOF
[proxysql]
name=ProxySQL YUM repository
baseurl=https://repo.proxysql.com/ProxySQL/proxysql-3.0.x/almalinux/\$releasever
gpgcheck=1
gpgkey=https://repo.proxysql.com/ProxySQL/proxysql-3.0.x/repo_pub_key
EOF
Installing:
yum install proxysql OR yum install proxysql-version
OpenSUSE:
Adding repository:
cat > /etc/zypp/repos.d/proxysql.repo << EOF
[proxysql]
name=ProxySQL Zypper repository
enabled=1
autorefresh=0
baseurl=https://repo.proxysql.com/ProxySQL/proxysql-3.0.x/opensuse/\$releasever_major
gpgcheck=1
EOF
or
zypper addrepo -g -n 'ProxySQL Zypper repository' 'https://repo.proxysql.com/ProxySQL/proxysql-3.0.x/opensuse/$releasever_major' proxysql
Installing:
yum install proxysql OR yum install proxysql-version
FreeBSD:
Installing (via pkg):
pkg install proxysql
Installing (via ports):
cd /usr/ports/databases/proxysql/ && make install clean
Service management
Once the software is installed, you can use the service command to control the process:
Starting ProxySQL:
service proxysql start
Stopping ProxySQL:
service proxysql stop
Or alternatively via the Admin interface (MySQL admin example):
$ mysql -u admin -padmin -h 127.0.0.1 -P6032 --prompt='Admin> '
Warning: Using a password on the command line interface can be insecure.
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 4
Server version: 5.5.30 (ProxySQL Admin Module)
Copyright (c) 2000, 2016, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
Admin> proxysql stop
For PostgreSQL admin interface the same Admin commands apply and the admin port defaults to 6132. You can connect using the psql client as follows:
$ export PGPASSWORD=admin
$ psql -U admin -h 127.0.0.1 -p6132
psql (17.4 (Ubuntu 17.4-1.pgdg22.04+2), server 16.1)
SSL connection (protocol: TLSv1.3, cipher: TLS_AES_256_GCM_SHA384, compression: off, ALPN: none)
Type "help" for help.
admin=# proxysql stop
(The examples above show the Admin interface workflow - the Admin SQL commands are the same for both MySQL and PostgreSQL modes.)
Restarting ProxySQL:
service proxysql restart
Or alternatively via the Admin interface (MySQL example):
$ mysql -u admin -padmin -h 127.0.0.1 -P6032 --prompt='Admin> '
Warning: Using a password on the command line interface can be insecure.
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 4
Server version: 5.5.30 (ProxySQL Admin Module)
Copyright (c) 2000, 2016, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
Admin> proxysql restart
Or via the PostgreSQL admin port:
$ export PGPASSWORD=admin
$ psql -U admin -h 127.0.0.1 -p6132
psql (17.4 (Ubuntu 17.4-1.pgdg22.04+2), server 16.1)
SSL connection (protocol: TLSv1.3, cipher: TLS_AES_256_GCM_SHA384, compression: off, ALPN: none)
Type "help" for help.
admin=# proxysql restart
Reinitializing ProxySQL from the config file (after first startup the DB file is used instead of the config file):
# If you are using the init script run:
/etc/init.d/proxysql initial
# or
service proxysql initial
# If you are using the systemd unit file run:
systemctl start proxysql-initial
# or
service proxysql-initial start
Upgrades
Just install the new package and restart ProxySQL:
wget https://github.com/sysown/proxysql/releases/download/v3.0.4/proxysql_3.0.4-ubuntu24_amd64.deb
dpkg -i proxysql_3.0.4-ubuntu24_amd64.deb
service proxysql restart
How to check the ProxySQL version
$ proxysql --version
ProxySQL version 3.0.4-162-gfaa64a5, codename Truls
A debug version has _DEBUG in its version string.
It is slower than non-debug version, but easier to debug in case of failures.
$ proxysql --version
ProxySQL version 3.0.4-162-gfaa64a5_DEBUG, codename Truls
Configuring ProxySQL via the admin interface
First of all, bear in mind that the best way to configure ProxySQL is through its admin interface. This lends itself to online configuration (without having to restart the proxy) via SQL queries to its admin database. It's an effective way to configure it both manually and in an automated fashion.
As a secondary way to configure it, we have the configuration file.
Configuring ProxySQL through the admin interface
To log into the admin interface for MySQL (with the default credentials) use a mysql client and connect using the following admin credentials locally on port (6032):
$ mysql -u admin -padmin -h 127.0.0.1 -P6032 --prompt='Admin> '
Warning: Using a password on the command line interface can be insecure.
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 4
Server version: 5.5.30 (ProxySQL Admin Module)
Copyright (c) 2000, 2016, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
Admin>
note: If your MySQL client version is version 8.04 or higher add --default-auth=mysql_native_password to the above command to connect to the admin interface.
To log into the admin interface for PostgreSQL use the psql client and connect using admin on port 6132 (the Admin SQL commands are the same):
$ export PGPASSWORD=admin
$ psql -U admin -h 127.0.0.1 -p6132
psql (17.4 (Ubuntu 17.4-1.pgdg22.04+2), server 16.1)
SSL connection (protocol: TLSv1.3, cipher: TLS_AES_256_GCM_SHA384, compression: off, ALPN: none)
Type "help" for help.
admin=#
Once connected to the admin interface, you will have a list of databases and tables at your disposal that can be queried using the SQL language:
Admin> SHOW DATABASES;
+-----+---------+-------------------------------+
| seq | name | file |
+-----+---------+-------------------------------+
| 0 | main | |
| 2 | disk | /var/lib/proxysql/proxysql.db |
| 3 | stats | |
| 4 | monitor | |
+-----+---------+-------------------------------+
4 rows in set (0.00 sec)
This will allow you to control the list of the backend servers, how traffic is routed to them, and other important settings (such as caching, access control, etc). Once you've made modifications to the in-memory data structure, you must load the new configuration to the runtime, or persist the new settings to disk (so that they are still there after a restart of the proxy). A detailed tutorial on how to configure ProxySQL through the Admin interface is available here.
Configuring ProxySQL through the config file
Even though the config file should only be regarded as a secondary way to configure the proxy, we must not discard its value as a valid way to bootstrap a fresh ProxySQL install.
Let's quickly go over the main sections of the configuration file (this overview serves as a very high level overview of ProxySQL configuration).
Top-level sections:
-
admin_variables: contains global variables that control the functionality of the admin interface. -
mysql_variables: contains global variables that control the functionality for handling the incoming MySQL traffic. -
mysql_servers: contains rows for themysql_serverstable from the admin interface. Basically, these define the backend servers towards which the incoming MySQL traffic is routed. Rows are encoded as per the.cfgfile format, here is an example:mysql_servers = ( { address="127.0.0.1" port=3306 hostgroup=0 max_connections=200 } ) -
mysql_users: contains rows for themysql_userstable from the admin interface. Basically, these define the users which can connect to the proxy, and the users with which the proxy can connect to the backend servers. Rows are encoded as per the.cfgfile format, here is an example:mysql_users: ( { username="root" password="root" default_hostgroup=0 max_connections=1000 default_schema="information_schema" active=1 } ) -
mysql_query_rules: contains rows for themysql_query_rulestable from the admin interface. Basically, these define the rules used to classify and route the incoming MySQL traffic, according to various criteria (patterns matched, user used to run the query, etc.). Rows are encoded as per the.cfgfile format, here is an example (Note: the example is a very generic query routing rule and it is recommended to create specific rules for queries rather than using a generic rule such as this):mysql_query_rules: ( { rule_id=1 active=1 match_pattern="^SELECT .* FOR UPDATE$" destination_hostgroup=0 apply=1 }, { rule_id=2 active=1 match_pattern="^SELECT" destination_hostgroup=1 apply=1 } ) -
pgsql_variables: contains global variables that control the functionality for handling the incoming PostgreSQL traffic. -
pgsql_servers: contains rows for thepgsql_serverstable from the admin interface. Basically, these define the backend servers towards which the incoming PostgreSQL traffic is routed. Rows are encoded as per the.cfgfile format, here is an example:pgsql_servers = ( { address="127.0.0.1" port=5432 hostgroup=0 max_connections=200 } ) -
pgsql_users: contains rows for thepgsql_userstable from the admin interface. Basically, these define the users which can connect to the proxy, and the users with which the proxy can connect to the backend servers. Rows are encoded as per the.cfgfile format, here is an example:pgsql_users: ( { username="postgres" password="postgres" default_hostgroup=0 max_connections=1000 active=1 } ) -
pgsql_query_rules: contains rows for thepgsql_query_rulestable from the admin interface. Basically, these define the rules used to classify and route the incoming PostgreSQL traffic, according to various criteria (patterns matched, user used to run the query, etc.). Rows are encoded as per the.cfgfile format, here is an example (Note: the example is a very generic query routing rule and it is recommended to create specific rules for queries rather than using a generic rule such as this):pgsql_query_rules: ( { rule_id=1 active=1 match_pattern="^SELECT .* FOR UPDATE$" destination_hostgroup=0 apply=1 }, { rule_id=2 active=1 match_pattern="^SELECT" destination_hostgroup=1 apply=1 } ) -
top-level configuration item:
datadir, as a string, to point to the data dir.
Related repositories
Master programming by recreating your favorite technologies from scratch.
A curated meta-list of curated lists organized by technology domain. The repository acts as a directory pointing to hundreds of specialized awesome lists covering programming languages, platforms, frameworks, and tooling. All content is community-contributed under the CC0 public domain dedication.
Public APIs is a community-curated GitHub repository listing free, publicly accessible APIs across a wide range of categories, with auth type, HTTPS, and CORS noted for each entry. It's a browsable reference, not a library to install.
REA is an MCP server and CLI that gives AI coding agents the ability to reverse engineer binaries, JavaScript apps, .NET assemblies, and websites. It hooks into Hopper, Ghidra, or IDA Pro for native binary work, or runs static JavaScript analysis with just Node.js. Every investigation returns an Evidence bundle that includes what was found, what was not, and the reasoning path. Setup registers REA with supported agents and walks you through connecting an analysis engine. The CLI also works standalone for terminal-first workflows.
Quick answers
How many stars does sysown/proxysql have?
sysown/proxysql has 7.0k GitHub stars — refresh the page for the live number, or check github.com/sysown/proxysql. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
Is sysown/proxysql open source?
Yes — sysown/proxysql ships under the GPL-3.0 license, which makes its source code freely readable (and, depending on license terms, forkable and reusable). Source: github.com/sysown/proxysql.
What is sysown/proxysql?
sysown/proxysql (sysown/proxysql) is a C++ project on GitHub. From the project's own README: High-performance proxy for MySQL and PostgreSQL
Where can I see sysown/proxysql in action?
The project maintains a homepage at http://www.proxysql.com. The README tab on this page also usually contains screenshots and a quickstart.
Where do I read more about sysown/proxysql?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/sysown/proxysql is the definitive source.
Read full README in the tab above.
Curious whether proxysql is right for you?
Let ChatGPT, Claude, or Perplexity look into it — click below and see what AI actually says about proxysql.