Retool previously announced the adoption of hardened deployment images, starting with the backend service. A hardened code-executor image is now available, built in the same manner as the backend image.

These images are used by Retool for its cloud-hosted platform and are available for self-hosted organizations to adopt. Eventually, all images used by Retool will be hardened.

Hardened images are built on a minimal, tightly controlled base to improve supply-chain security and reduce the attack surface. They also benefit from a smaller, more tightly curated set of included software, which reduces the risk of security vulnerabilities.

Retool is continuing to work on new and existing hardened images. Over time, this means some existing features and bundled libraries will no longer be supported in their current form. If a feature or library will no longer be available, or if a change requires updates to your current configuration, Retool will share this information in a changelog post with specific information and any relevant migration guidance.

Each changelog post will provide as much advance notice as possible so that you have time to review and implement any changes that may be needed.

Retool is deprecating the dedicated Vertica resource type.

Retool will remove the resource type in Q1 2027, after two quarterly Stable releases. After removal, Vertica resources will stop working. Queries in apps and workflows that still point at those resources will fail. Retool will no longer ship the Vertica JDBC driver. Cloud organizations will not have a Vertica connection option after removal.

Self-hosted organizations can keep querying Vertica after removal by creating a JDBC resource and adding a Vertica JDBC driver that you provide. Retool will not migrate Vertica resources or their query references automatically.

1. Download the Vertica JDBC driver from Vertica.
2. Add the .jar file to your self-hosted instance. Follow the JDBC configuration steps for JDBC_DIRECTORY_PATH.
3. Create a JDBC resource with Driver name com.vertica.jdbc.Driver, connection string jdbc:vertica://HOSTNAME:5433/DATABASE?user=USERNAME&password=PASSWORD&DisableCopyLocal=true, and schema query select table_name, column_name, data_type, table_schema from columns. Include DisableCopyLocal=true on the connection string.
4. Open each app and workflow query that uses the Vertica resource. Change the query to use the new JDBC resource, then test it.

JDBC resources do not support Retool-managed SSH tunnels. If your Vertica resource uses an SSH tunnel, or you have a large number of Vertica queries and need help finding them, contact Retool Support.

Retool is phasing out support for MongoDB Server version 3.4 and earlier. Organizations with an unsupported version of MongoDB Server connected to Retool must upgrade to MongoDB Server 3.6 or later.

• For cloud organizations, support for MongoDB Server 3.4 and earlier has already been removed.
• For self-hosted organizations, support for MongoDB Server 3.4 and earlier will be deprecated in the Q2 2026 stable release. It will be removed in the Q3 2026 stable release.

MongoDB Server 3.4 has been end of life (EOL) since January 2020. We recommend upgrading to a currently supported MongoDB release.