ProxySQL Introduces Multi-Tier Release Strategy With Stable, Innovative, and AI Tracks

ProxySQL, the popular open source database proxy, has unveiled a new multi-tier release strategy alongside version 3.0.6, marking a significant evolution in how the project serves its diverse user base. The strategy introduces three distinct tracks: Stable, Innovative, and AI/MCP, each targeting different user needs and risk tolerances.

What's New in ProxySQL 3.0.6

The Stable Tier release focuses on reliability and production readiness. Version 3.0.6 brings substantial improvements to PostgreSQL support, including advanced query logging and enhanced compatibility. The release also strengthens authentication reliability, improves monitoring with clearer Prometheus metrics, and expands platform support to include macOS. A notable addition is native support for tracking replication lag on PostgreSQL backends, enabling ProxySQL to make more intelligent routing decisions based on real-time data freshness.

The Three-Tier Release Strategy

René Cannaò, founder and CEO at ProxySQL, explains that as the project has grown to power some of the world's most demanding database infrastructures, community needs have diversified. The new strategy addresses this by offering:

Stable Tier (3.0.x): Focuses on absolute reliability for mission-critical production environments. This track is recommended for most production deployments where stability trumps new features.

Innovative Tier (3.1.x): Targets early adopters and introduces new observability features such as an embedded time series database and a traffic observer for deeper insight into database traffic.

AI/MCP Tier (4.0.x): Explores experimental capabilities including native AI integrations and an MCP (Model Context Protocol) stack to enable more autonomous database management.

AI Integration at the Proxy Layer

The AI/MCP track represents ProxySQL's ambitious vision for the future of database management. In a separate article titled "Bringing GenAI to Every MySQL Instance: ProxySQL v4," Ronald Bradford, CTO at ProxySQL, outlines how traditional AI capabilities typically require schema migrations, new vector database infrastructure, dual-write synchronization headaches, and AI logic sprawled across every application layer.

ProxySQL v4.0 takes a different approach by putting intelligence at the proxy layer rather than in the database or application. This architectural decision means teams can leverage RAG (Retrieval Augmented Generation) pipelines and natural language querying without the typical infrastructure overhead and complexity.

Context in the Database Proxy Landscape

ProxySQL has historically been popular in the MySQL and MariaDB communities, but since 2024 has added PostgreSQL support, a move that has received positive reactions from the community. While ProxySQL is the most popular MySQL-aware proxy, with MySQL Router and MariaDB MaxScale as other common choices, PgBouncer dominates the PostgreSQL space, with PgCat and Pgpool-II as other popular options.

This multi-tier strategy positions ProxySQL to compete more effectively across both ecosystems while catering to different user segments. Organizations running mission-critical workloads can stick with the Stable track, while those exploring AI-driven database management can experiment with the AI/MCP track.

What This Means for Users

The multi-tier approach represents a mature understanding of how different organizations adopt technology. Production environments need stability and predictability, while innovation labs and forward-looking teams want early access to cutting-edge features. By separating these concerns into distinct tracks, ProxySQL can serve both audiences without forcing compromises.

For existing users, the recommendation is clear: most production deployments should continue with the Stable Tier (3.0.x), while teams interested in observability improvements can explore the Innovative Tier (3.1.x), and those experimenting with AI capabilities can look to the AI/MCP Tier (4.0.x).

ProxySQL remains open source under the GNU GPL v3 license, with additional enterprise features available under a commercial license from the project's company. This release strategy demonstrates how open source projects can evolve to meet diverse community needs while maintaining their core values of accessibility and transparency.

The new release strategy is available now, with ProxySQL 3.0.6 recommended for most production deployments. The project continues its journey to become a first-class citizen in the PostgreSQL ecosystem while maintaining its strong position in the MySQL world.