🔍 What happens when you approve an index recommendation in Releem?
The Releem Agent checks whether the schema change can proceed before applying it to MySQL or MariaDB.
Here’s how it works 👇
We’ve finally shipped SQL query and schema optimization for PostgreSQL 🔥
Both are now generally available in Releem.
Teams running PostgreSQL, MySQL, or MariaDB can review recommendations across performance, availability, security, and resource usage in one interface. After user review and approval, Releem can safely automate supported configuration and schema changes.
Before tuning a database server configuration, we tune the ML models behind Releem 🙂
For every server connected, Releem prepares an individual ML model for configuration tuning based on its workload and configuration history.
Try Releem to find and optimize inefficient SQL queries, improve your database configuration, detect performance and security issues, and more:
https://t.co/SAMh6fwo2x
When we launched Releem, it supported MySQL on Linux and installing the agent took one command.
Since then, we have added MariaDB and PostgreSQL.
We have also expanded beyond Linux to Docker, Kubernetes, Windows, AWS RDS, Google Cloud SQL, and Azure.
As the number of supported setups grew, onboarding became harder 🤯
So we rebuilt the Add Server wizard. Tell Releem which database you use and where it runs, and it shows the correct installation steps.
Here is the new flow 👇
At Releem, we’re building a Database Advisor that analyzes databases and prepares evidence for review.
The Database Administrator decides what to change and when.
Same initials, DBA, different responsibilities.
One DBA helps another DBA 🙂
I underestimated by how much DeepSeek are raising API prices in a few days.
It's SIGNIFICANT.
It's not percentage, it's TIMES multiplier.
I ran calculations on a few typical prompts:
- 1.5-2x price off-peak
- 3-4x price during peak hours
Details: https://t.co/HCAwXi4rDU
Releem optimized 7.79 million SQL queries in the first six months of 2026. Sharing a few insights.
It’s great to see PostgreSQL in the report already. We released PostgreSQL support this year, and Releem is already helping optimize PostgreSQL queries.
Another milestone is that in just six months, Releem optimized more SQL queries than during 2025.
MariaDB continues to dominate production environments. MariaDB 10.11 LTS and 10.6 LTS are among the most common versions we see, alongside MySQL 8.0.
Looking forward to seeing how these numbers change by the end of the year. 🚀
Query optimization should not stop at "here is a missing index."
In the latest Releem update, we introduced a guarded Apply flow for index recommendations.
🧵👇
We’re partnering with Layershift to bring Releem to Enscale.
Releem helps teams run databases with confidence, even without a dedicated DBA, by monitoring availability and performance, identifying security risks, and recommending what to improve.
The link 👇
We finally closed the SQL query optimization loop for index recommendations in Releem 🎉
Releem already identifies inefficient queries and recommends missing indexes. But a recommendation is not a production change. Someone still has to decide whether and how to apply it safely.
Now, after you review and approve an index recommendation, Releem can apply it through a guarded workflow.
It checks whether the affected data can be recovered, whether the operation can run online, and which method fits the database engine, version, server, and table.
🛡️ If any check fails, the change does not proceed.
After the index is applied, Releem keeps monitoring the query and measures its impact.
This is the model we are building in Releem:
- AI identifies the opportunity.
- A human approves the decision.
- Deterministic software executes the change.
See how it works in the screencast below
Now you can analyze your own SQL queries in Releem, not only the ones detected automatically.
Add a custom query, and Releem will request the execution plan from your database server and suggest optimizations.
Useful for reviewing queries before they reach production.
May update is live 🎉
Releem now supports PostgreSQL and Azure Database for MySQL.
Also shipped:
- Windows install automation
- Query recommendations in Query Analytics
- Demo server
- Invited-user notifications
- Agent security fixes.
Read the full May update 👇
PostgreSQL support in Releem is now available 🎉
Teams can now use the same Releem workflow across MySQL, MariaDB, and PostgreSQL.
PostgreSQL support helps teams understand database health, monitor activity, identify and address security issues, and tune configuration to improve performance.
Schema analysis and query optimization are coming soon.
We first opened it to users on our waitlist, collected feedback, and used that feedback to improve the product before the public release.
Big thank you to everyone on the waitlist who helped us shape the product 🙌
Gabriel Ciciliani will be speaking at Percona Live 2026 about #MySQL internal temporary tables and the hidden behavior that shapes query performance.
If you’re coming to Percona Live, join the session and come say hi 👋 to Gabriel and the Releem team.
See you at #PerconaLive 🙂
We finally moved Releem platform from Azure back to Google Cloud.
Not because migration is fun. It is not)
Google now covers our cloud costs through its startup program, so moving back made sense.
Our infrastructure history is a small startup story by itself:
- We started on AWS.
- Two years later, we moved to GCP.
- We did not get into Google’s startup program then, so we moved to Azure.
- Now we are back on GCP.
Each time, we moved without service interruption. And each time, Releem became a little less tied to one cloud.
The hardest part is always the databases. Moving terabytes is not a “copy files and restart” service. You have to think about replication, consistency, failover, and all the boring details that decide whether users notice anything.
This migration also pushed us to do something we should have done earlier:
1. More Terraform and installation scripts.
2. Less hidden, cloud-specific knowledge.
Most importantly, we removed the last AWS Lambda dependency ( yeah, old services still used it )
The result is that Releem can now run the same way across clouds, or on dedicated servers.
Now back to building)
We simplified how recommendations are shown in Releem SQL Query Analytics.
You can now see analysis and recommendations for top and slowest queries without extra clicks.
If a query is fine, you’ll still see that it was checked and when it was last analyzed.
🚀 What’s new at Releem in March?
🔍 Recommendations for all queries are now visible directly in Query Analytics
🧠 Custom SQL query optimization
🖥️ WHM/cPanel + WHMCS integration
☁️ AWS Aurora Serverless support
📊 Deadlocks can now be exported to CSV
Blog post👇