Continuing the ProxySQL.Cloud Conversation After Percona Live Amsterdam
Thank you to everyone who visited the ProxySQL booth at Percona Live 2026 Amsterdam and spent time exploring ProxySQL.Cloud with us.
Showing a new platform in person creates a different kind of conversation. Instead of describing an idea in the abstract, we could walk through real operational workflows and discuss how teams manage ProxySQL today across databases, clusters, clouds, and regions.
We are grateful for the time, questions, and practical perspective that visitors brought to those conversations.
One control plane for a growing database estate
ProxySQL.Cloud is being built for teams whose ProxySQL environments have grown beyond a handful of instances.
At that point, the challenge is not simply running another proxy. It is maintaining a dependable view of the whole estate: which clusters are healthy, where traffic is flowing, what configuration is active, who changed it, when a backup last completed, and whether capacity still matches demand.
The platform brings those concerns into one control plane for MySQL and PostgreSQL environments.
What we demonstrated in Amsterdam
At the booth, we walked through the main areas of the ProxySQL.Cloud experience:
Cluster health and activity
Each cluster brings together health, throughput, top queries, backend-pool status, connections, and other operational signals. The goal is to make the current state understandable without assembling it from several unrelated tools.
Configuration with validation and history
Query rules, servers, users, and variables can be managed as YAML. A dry-run validation step helps catch problems before changes are applied, while configuration history provides a path back to an earlier known state.
Backups, alerting, and scaling
Teams can create configuration backups on demand or on a schedule, define alerts around meaningful thresholds, and establish scaling policies based on operational signals such as client connections.
An activity trail for operational context
State transitions and changes are recorded in one activity stream. When something needs attention, the surrounding context should be available alongside the cluster rather than reconstructed after the fact.
The operational questions behind the product
ProxySQL.Cloud is designed around a set of practical questions:
- How can a team understand the health of many ProxySQL deployments at a glance?
- How can configuration changes be validated, attributed, and recovered safely?
- How can operators investigate query behavior without switching among several systems?
- How should backups, alerts, and scaling policies work across environments?
- How can organizations choose between managed, BYOC, and BYOK deployment models?
- Where can automation remove repetitive work without hiding important operational decisions?
These are not problems with one universal answer. Different organizations have different boundaries around infrastructure ownership, security, compliance, and change management. Our goal is to make those choices explicit while reducing the manual work around them.
The conversation continues
Percona Live Amsterdam was an important milestone for ProxySQL.Cloud, but it was not the end of the discussion. We will continue refining the platform as we move toward broader availability.
If you saw the demonstration in Amsterdam, thank you for spending time with us. If you could not attend, you can still preview ProxySQL.Cloud, read the original ProxySQL.Cloud announcement, or contact us to discuss your environment and requirements.
Whether you operate a few clusters or a database estate spread across multiple clouds and regions, we would like to understand what makes that work difficult today.
Thank you again for helping us continue the conversation.