Services AI Integrations Case Studies Proof-of-Concept Sprint About Portfolio Pricing Tools Careers FAQs Contact Support request Get started Schedule a call Emergency session ($199)
Pooled · routed · failover-aware

ProxySQL that keeps MySQL reachable under load and through failover

We put ProxySQL between your application and MySQL or MariaDB so connection storms, replica lag and a primary failover stop being application problems. Pooling, read/write splitting and routing rules, set up and tested against your real traffic.

<48h
Typical Drop-In turnaround
R/Wsplit
Reads to replicas, writes to the primary
Zerocode
App changes needed for routing
proxysql — admin
admin@proxysql> SELECT hostgroup, srv_host, status FROM runtime_mysql_servers;
[writer] hg 10 · db1 · ONLINE   ok
[reader] hg 20 · db2, db3 · ONLINE   ok
# rule 1: ^SELECT.*FOR UPDATE → hg 10 · rule 2: ^SELECT → hg 20
[pool] 1,840 client conns → 48 backend   ok
failover drill writer moved to db2 · no errors_
What we deliver

Everything between your app and your database

Pooled, routed and failover-aware, with the rules written down.

Connection pooling

Thousands of application connections multiplexed onto a small, steady set of backend connections, so MySQL spends its time on queries.

Read/write splitting

Query rules send writes to the primary and safe reads to replicas, with no changes to application code.

Failover handling

Hostgroups that follow replication, Galera or Group Replication topology, so a promoted primary takes traffic without a config push.

Lag-aware routing

Replicas that fall behind are taken out of rotation automatically, so users do not read stale data.

Query caching & rewriting

Cache hot read queries at the proxy, and rewrite or block a bad query pattern without waiting on a deploy.

Query visibility

ProxySQL's own stats show which query digests cost the most, feeding monitoring and the next round of tuning.

Built for bad days

The database can fail over; the app should not notice

We run ProxySQL in front of our own MariaDB cluster. The configuration we hand over is the kind we have had to rely on ourselves.

  • Tested failover — we promote a replica on purpose and watch traffic follow.
  • Rules you can read — every query rule documented, with what it routes and why.
  • No single point — the proxy layer itself deployed redundantly, not as a new weak link.
Scope your proxy layer
Simple pricing

ProxySQL support that scales with you

Start with a monthly plan or grab a one-off Drop-In — no lock-in, cancel anytime.

See full pricing & compare

Or book a free 15-min call — or prove the approach first with a one-week Proof-of-Concept Sprint.

FAQ

Common questions

Do we have to change our application to use ProxySQL?

Usually only the database host and port. ProxySQL speaks the MySQL protocol, so the app connects to it as if it were the database, and routing is decided by rules on the proxy.

Is read/write splitting safe for our app?

It depends on how your app reads its own writes. We start with everything on the primary, then move specific read queries to replicas by rule, checking each for stale-read risk rather than splitting everything at once.

What happens when the primary fails?

ProxySQL watches the backends and moves the writer role to the promoted server. Promotion itself is done by your replication manager or cluster; we wire the two together and rehearse the failover so the behaviour is known.

Does ProxySQL become a single point of failure?

Only if it is deployed as one. We run it either alongside each application instance or as a redundant pair, so losing a proxy does not take the database path with it.

Get started

Let's put a proper proxy in front of your database

Tell us what you're running — we'll tell you where the wins are before you commit.

Architecture → implementation → proof → runbook  ·  senior US engineers  ·  $1M insured

Too many connections or failover gone wrong?

Emergency support is our entry tier — existing client or not, start an urgent request and a senior engineer will jump on it.

Start support request