Self-hosted Retool 4.34 and 4.0 stable updates
The following patches are now available on the Stable release channel:
Update your Retool instance to apply the latest bug fixes and security patches.
Updates, changes, and improvements at Retool.
Refer to the stable and edge release notes for detailed information about self-hosted releases.
The following patches are now available on the Stable release channel:
Update your Retool instance to apply the latest bug fixes and security patches.
You can now embed apps in other apps, in classic apps, and in apps or websites outside Retool using an iframe. To enable app embedding, an organization admin adds Content Security Policy directive rules that name the pages that are allowed to frame your app.
Refer to the Embed apps guide to learn how.
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.58 is now available on the Edge release channel for self-hosted organizations.
Retool now supports the following new AI models:
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.54 is now available on the Edge release channel for self-hosted organizations.
Version 3.0 of the Microsoft SQL integration accepts array values in query parameters. Retool converts an array to a comma-separated string before passing it to SQL Server, which matches the behavior of version 1.0.
Retool previously documented this as a breaking change and recommended converting array values with .join(',') before using them with STRING_SPLIT. The restriction was broader than documented: it applied to any query parameter set to an array value, whether or not the query used STRING_SPLIT. Version 3.0 removes the restriction entirely, so queries that pass array values no longer need to be rewritten. Queries that already use .join(',') produce the same value and continue to work without changes.
This was the only known breaking change between version 1.0 and version 3.0. You can now update an existing Microsoft SQL resource from version 1.0 or version 2.0 to version 3.0 without changing your queries. Versions 1.0 and 2.0 are deprecated and will be removed, so Retool recommends updating any resource still using them.
Query parameters set to an object are not supported and cause the query to fail. Convert an object to a string before using it in a query, for example with JSON.stringify.
Retool introduced several features to help Enterprise organizations manage AI usage.
Use the new centralized settings page, AI visibility, to view AI credit usage and BYOK AI token usage. Navigate to Settings, and select Retool managed keys or Bring your own key from the dropdown at the top of the page. You can filter AI usage by instance, model, user, and feature.
This page is available on Enterprise plans. Admins can access it, and other users can access it with delegated Manage billing and Manage usage analytics permissions. Available views depend on the user’s permissions.
Enterprise organizations can also use the new Get AI credit usage endpoint to measure the number of credits consumed for each AI resource that uses a Retool-managed key. You can view the number of credits consumed by resource, user, and surface area.
Learn more about credit and token monitoring.
The following patches are now available on the Stable release channel:
Update your Retool instance to apply the latest bug fixes and security patches.