Skip to main content

Changelog

Updates, changes, and improvements at Retool.

Refer to the stable and edge release notes for detailed information about self-hosted releases.

Tags

Retool now supports hardened images, which are available on the self-hosted edge release channel. These images are designed to improve supply-chain security, reduce the attack surface, and support modern infrastructure while remaining functionally compatible with existing deployments. Learn more about hardened images in the conceptual guide.

Plan your migration​

Use the following high-level steps to evaluate and roll out hardened images.

1. Review requirements and environment​

2. Test hardened images in non-production​

Retool strongly recommends testing hardened images on non-production instances first, for example:

  • A development or staging instance in a separate Virtual Private Cloud (VPC) or cluster.
  • A temporary test environment built using the Docker, Kubernetes, or ECS Fargate deployment guides.

When testing:

  • Update your manifests or Docker Compose files to use the appropriate *-edge-hardened-beta tags.
  • Verify your critical apps, workflows, and database connections behave as expected.
  • Check container health, logs, and telemetry using Container logs and Collect self-hosted telemetry data.

3. Roll out to production instances​

When you're ready to use hardened images in production:

  • Follow your usual deployment and rollout process. For example, use the near-zero downtime strategy in Scale your self-hosted deployment infrastructure.
  • Upgrade instances sequentially (development → staging → production) and validate each step.
  • Communicate with your users about maintenance windows and any expected changes.

If you encounter regressions, you can temporarily roll back to classic images by reverting your image tags while you work to diagnose and resolve issues.

Stable channel timeline​

After sufficient testing and feedback on edge, Retool plans to transition hardened images to the stable channel. When that happens:

  • Both Stable classic and Stable hardened images will be available in parallel for a period of time.
  • Over time, hardened images will become the recommended default for production deployments, and classic images will eventually be phased out.

To stay current on timelines and support windows, monitor the Stable releases and Self-hosted requirements documentation.

Tags

You can now create a README from the workflow IDE to help clarify important information about your workflow for collaborators. For example, if a workflow requires certain permissions on a resource, or if it's only scheduled to run once a week.

This feature is available for cloud instances and will be available in subsequent releases of self-hosted Retool. Reach out to your account manager to enable README for workflows.

This feature is also available for workflows protected with Source Control. To create a README, click the title of the workflow and add content to the Editor README field. READMEs are visible from the Edit workflow details dialog box, in workflows JSON exports, and in a markdown file from source control.

Tags

Tags

Tags

If you self-host Retool and are using a stable release, reach out to your account manager to enable Google Slides.

Retool now supports an integration to Google Slides, which utilizes the Google Slides API and the Google Drive API. Use this integration to retrieve, create, and update documents for apps, workflows, and agents.

This integration can also indirectly interact with the Google Sheets API. Charts from Google Sheets can be embedded into Google Slides.

Tags

Retool now supports Azure OpenAI for use with Assist. Admins on the Enterprise plan can configure Assist to use Azure OpenAI as the single model provider for Assist-powered interactions.

To enable the use of Azure OpenAI as a single model provider, reach out to your account manager.

Retool designed Assist to use two AI providers by default: OpenAI and Anthropic. Using both providers enables Assist to optimize for speed and quality. However, some customers may need to consolidate AI services with a single provider. To accommodate these customers, Enterprise organizations can configure Assist to work with a single provider.

Tags

Retool no longer supports Claude Sonnet 3.5. Claude Sonnet 4.5 will be used instead.

Tags

Retool no longer supports GPT 3.5 Turbo. GPT-4o-mini will be used instead.

Tags

Retool now supports Amazon Bedrock for use with Assist. Admins on the Enterprise plan can configure Assist to use Amazon Bedrock as the single model provider for Assist-powered interactions.

To enable the use of Amazon Bedrock as a single model provider, reach out to your account manager.

Retool designed Assist to use two AI providers by default: OpenAI and Anthropic. Using both providers enables Assist to optimize for speed and quality. However, some customers may need to consolidate AI services with a single provider. To accommodate these customers, Enterprise organizations can configure Assist to work with a single provider.