Updates, changes, and improvements at Retool.
Refer to the stable and edge release notes for detailed information about self-hosted releases.
Organizations on the Team plan can now use Retool-provided AI models for app building, in addition to the full catalog of supported models. These models, prefixed with Retool, have been tuned by Retool for enhanced performance and speed for app building.
The following Retool-provided models are supported:
Claude Opus 5.5 is now available in Retool through Anthropic for all paid plans and through Amazon Bedrock for Enterprise plans. It can be used in the following ways:
The following patches are now available on the Stable release channel:
Update your Retool instance to apply the latest bug fixes and security patches.
Retool 4.66 is now available on the Edge release channel for self-hosted organizations.
Retool has concluded the public beta period for Assist, and Assist is no longer available in the classic app builder for most cloud or self-hosted instances. Certain customers retained access until December 31, 2026, in order to migrate off the tool. If your organization retained access, see Assist for supported models and setup instructions.
The drag-and-drop experience for building and maintaining classic apps is still available. For an AI-powered building experience, Retool recommends using the new app builder. Converting your classic apps to the new app builder is free for Team, Business, and Enterprise organizations.
If you have any questions, reach out to the Community Forum or your account manager.
Starting January 1, 2027, Retool is deprecating Retool Email for organizations on the Free plan. After this date, Free plan organizations can no longer use Retool Email to send emails from apps, workflows, or other automations.
Retool Email remains available to organizations on the Team, Business, and Enterprise plans.
This change affects cloud-hosted organizations on the Free plan that use Retool Email. Organizations on paid plans are not affected.
As part of our continued efforts to keep Retool secure and reduce vulnerabilities, Retool is deprecating several preinstalled third-party libraries, such as jsonwebtoken, crypto-js, moment, and uuid, currently available in custom authentication JavaScript steps. Retool plans to remove these libraries from cloud and self-hosted instances in Q2 2027.
If your custom authentication steps use any of these libraries, you can migrate to Node.js built-in equivalents, such as crypto and Buffer, well ahead of the removal date. Migrating before then avoids any disruption to your authentication flows.
Only REST API, GraphQL, OpenAPI, and gRPC resources that use Custom Auth with a JavaScript step that loads a preinstalled library are affected. JavaScript steps that use Node.js built-in modules, such as crypto, continue to work without changes.
Any customers who have resources that use Custom Auth as its authentication method and one of its JavaScript steps loads a preinstalled library. Custom authentication steps that only use Form (modal), API Request, or Define a variable steps aren't affected, and neither are JavaScript steps that don't call require().
As part of our continued efforts to keep Retool secure and reduce vulnerabilities, hardened images become the default for self-hosted images starting in Q2 2027. As a result, Retool is deprecating Windows Authentication for Microsoft SQL Server resources. This deprecation also applies to Kerberos authentication for Microsoft SQL Server, which relies on Windows Authentication.
Hardened images are intentionally minimal and don't include the additional third-party libraries and utilities that Windows Authentication relies on. Microsoft SQL Server resources with Connect using Windows Auth enabled will eventually stop working, so plan to migrate before your resources are affected.
This change only affects self-hosted organizations with Microsoft SQL Server resources that have Connect using Windows Auth enabled.
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. The hardened code-executor image is still in testing and its default packages are subject to change.
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.
Organizations on the Free plan now use Retool-provided AI models for app building. These models, prefixed with Retool, have been tuned by Retool for enhanced performance and speed for app building. Access to models from other providers is now only available on paid plans.
Builders using these models will notice comparable quality and faster speeds when compared with other models previously available on the Free plan.
The following Retool-provided models are supported: