Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

Gaea review

Free#18 of 31 in Database Proxy Software

A self-hosted MySQL proxy for sharding, routing, pooling, and multi-cluster operations.

7.4/10Editor score
Gaea7.4 Visit Gaea

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Gaea is open-source database middleware and a MySQL protocol proxy developed by Xiaomi’s B2C development team. It is designed for teams operating self-hosted MySQL-compatible database infrastructure that need to place a routing and management layer between applications and backend databases. Its scope covers transparent SQL forwarding, database and table sharding, SQL routing, read/write splitting, replica load balancing, backend connection pooling, SQL interception and filtering, configuration hot loading, multi-tenant namespaces, and multi-cluster operation. Gaea is a focused fit for MySQL infrastructure teams rather than a general-purpose proxy across several database engines.

The feature set centers on traffic control and distribution. SQL routing can direct requests across database layouts, while sharding supports both databases and tables. Read/write splitting separates query paths, and replica load balancing distributes traffic across replicas. Backend connection pooling handles reusable database connections, while SQL interception and filtering provide an additional control point for statements passing through the proxy. The published scope also includes automatic failover, configuration hot loading, namespaces for multi-tenant environments, and multi-cluster management. Together, these capabilities make Gaea relevant when a MySQL deployment needs more than basic connection forwarding.

Deployment is self-hosted: Gaea is distributed as Go binaries that administrators compile and run themselves. Configuration can be managed through files or etcd, giving teams an integration point for centralized configuration workflows. The platform fit is therefore strongest for organizations already operating MySQL clusters, replicas, and supporting infrastructure. Choose Gaea when MySQL sharding, routing, pooling, and multi-cluster control are core requirements and your team can manage the middleware directly. Consider another option if you need a hosted service, broader database-engine coverage, or a vendor-managed operating model.

Gaea pros and cons

  • Where it wins
    • Supports database and table sharding with SQL routing
    • Combines read/write splitting, replica balancing, and pooling
    • Adds namespaces, hot loading, filtering, and multi-cluster management
  • Where it doesn't
    • Focused on self-hosted deployment rather than hosted database services
    • Verified database support is limited to MySQL
    • Requires administrators to compile and run Go binaries

Gaea fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update