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

Cetus review

Free#19 of 31 in Database Proxy Software

A Linux self-hosted proxy for MySQL routing, pooling, splitting, and sharding.

7.3/10Editor score
Cetus7.3 Visit Cetus

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Cetus is open-source middleware written in C that sits between applications and MySQL backends as a transparent proxy. It is aimed at teams managing MySQL-compatible connections that need database-layer routing, connection pooling, read-write splitting, or sharding. Applications can connect through MySQL-compatible interfaces, while Cetus handles capabilities such as SQL routing, prepared statements, result-set compression, status monitoring, administration, and distributed transaction processing. Its open-source model and Linux support make it a fit for teams comfortable operating database infrastructure themselves.

The feature set is focused on scaling and controlling traffic at the database layer. Backend connection pooling can manage connections between the proxy and databases, while SQL read-write splitting and routing provide separate ways to direct queries. Database sharding extends that control across multiple database partitions. The combination is useful for MySQL environments where traffic distribution and data placement matter more than a simple connection-forwarding proxy. Docker deployment is also documented, giving infrastructure teams an additional deployment path alongside Linux-based operation.

Cetus is most suitable for engineering teams that want an open-source, self-hosted MySQL proxy with sharding and routing capabilities. It is less suitable for organizations seeking a managed service, broad multi-database support, or a non-Linux deployment. The published positioning includes high-availability use cases, but load balancing and automatic failover are not established here, so teams choosing Cetus for those requirements should evaluate those capabilities separately. Choose it when transparent proxying, pooling, read-write splitting, SQL routing, and sharding are central requirements; consider an alternative when operational simplicity or wider platform coverage matters more.

Cetus pros and cons

  • Where it wins
    • Supports transparent proxying, pooling, routing, and read-write splitting
    • Adds database sharding, prepared statements, and distributed transactions
    • Offers status monitoring, administration, compression, and Docker deployment
  • Where it doesn't
    • Runs on Linux only
    • Requires a self-hosted deployment model
    • Supports MySQL rather than a broader range of databases

Cetus 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