What’s New At Releem
June 2026

We're always collecting issues and feature requests on our GitHub. Here's where you can contribute:

• Issues – If you encounter any problems or bugs, report them here.
• Feature Requests – Have an idea to make Releem even better? Share your suggestions here.

Safe automation for index recommendations

Releem can now safely apply index recommendations. Every change goes through a guarded workflow designed to protect availability and preserve a recovery path:

1. Before a schema change is sent to the Agent, Releem validates whether the affected data can be recovered and whether the operation can run online in that environment.
2. The workflow accounts for the database distribution, version, storage engine, and table structure when selecting an eligible execution method. If the database cannot support an online backup, point-in-time recovery is unavailable, or the change would require a blocking operation, Releem stops before execution.
3. The Agent then checks available space in the backup and database filesystems and confirms that the required backup tools are installed. It creates a backup and runs a schema-change dry run before applying the index.

Any failed prerequisite, backup, or dry run aborts the change. This gives teams a controlled path from identifying a missing index to applying it safely.

Added multi-step Installation Wizard

The new Installation Wizard guides users through three setup decisions:

1. Which database they want to connect
2. Where the database is running
3. How Releem should be installed

The wizard supports MySQL, MariaDB, and PostgreSQL. For self-managed environments, users can choose Linux, Windows, WHM/cPanel, Docker, or Kubernetes. Managed cloud options include AWS, Google Cloud, and Azure.

For Linux and Windows installations, the database password is no longer entered in the web interface. The generated script requests it locally during installation, keeping the credential out of the browser-based setup flow for added security.

Expanded PostgreSQL configuration recommendations

Releem now provides recommendations for a broader range of PostgreSQL settings, giving users more control over autovacuum behavior, memory allocation, storage use, parallel query execution, and idle transactions.

The expanded recommendation set includes:

Show just the recommended configuration changes

Recommended Configuration now includes a Show just changes view, allowing users to focus on the settings that differ from their current database configuration instead of reviewing every available value.

Reports for invited users on shared servers

Invited users can now receive reports for servers shared with them. This keeps collaborators informed about the databases they work on without requiring the server owner to forward updates manually.

Removed an irrelevant security check for cloud-managed MySQL and MariaDB

Releem previously displayed a symlink security check for managed cloud MySQL and MariaDB instances, even though users cannot change the related setting or access the underlying host.
The check is now skipped for cloud-managed instances, removing a warning and advice that users could not act on.

Fixed deadlock analysis for names with special characters

Deadlock analysis can now parse quoted database and table names that contain special characters. We update the parser’s regular expressions after finding cases where these names prevented Releem from reading the deadlock output correctly.

Fixed an error when adding servers simultaneously

We fixed an error that could occur when two servers were added at the same time. Parallel server onboarding can now complete without one addition interfering with the other (Closes #515).