The new @retool's real unlock isn't "describe an app, get React." It's shipping with governance attached. The blocker was never the code. It was procurement, security, and DevOps. Retool sits behind all three, so governance comes with the build. 🦾 eu1.hubs.ly/H0whkZC0

Proud to be a launch partner for their new AI app-building experience. Build with any AI tool. Deploy with enterprise governance enforced automatically. For enterprise teams: AI-assisted development that doesn't compromise on compliance. Learn more → eu1.hubs.ly/H0w9zfz0

Six to eight weeks: the typical delivery window for enterprise Retool builds across 200+ EMEA engagements. 📊 We break down the exact week-by-week model for each project type in the article: eu1.hubs.ly/H0vkHwt0

Signed S3 URL loads fine in the browser. Open it in a Retool PDF component and a blank screen appears, no error. The fix: one CORS config change on your S3 bucket. Our engineer Arsany documented the full breakdown 👇 Link here: eu1.hubs.ly/H0tZHTD0

Why do well-built internal tools still get abandoned? Most teams assume it's a UX problem. Or a training problem. Or that people just resist change. It's usually simpler than that: the old process stays because the new one hasn't earned enough trust yet. There is no clear owner, no documentation and no place to raise issues. The build is done, but the adoption work hasn't started. 🛠️ Full article on Internal tool adoption here: eu1.hubs.ly/H0tzTHq0 #InternalTools #OperationalExcellence #EnterpriseOps

@retool invited Stackdrop's founder, John, to build live on April 21. Here's what he's building: an LLM-powered WYSIWYG editor inside Retool, using Editor.js as the foundation: a custom component that doesn't exist out of the box, built from scratch in one hour. 🏗️ If your team runs Retool in production and has ever needed a richer text input layer inside your tools, this session is worth watching. The full build happens live and the recorded session will be available afterward. 🗓 April 21 · 7:00–8:00 PM CEST 🔗 Register: eu1.hubs.ly/H0twQQ10 #Retool #InternalTools #LowCode #CustomComponents

Retool's default slider lets you filter data. It doesn't show you what you're filtering into. Vaggelis Kapetanakis, an engineer at Stackdrop, built a custom range slider with a histogram above it so you can see how your data is distributed before you set a range. Not after. The difference matters when you're reviewing transactions, managing inventory, or tracking any metric where context changes the decision: You stop filtering blind. This component is now part of @retool's official custom component library. 📚 On April 21, we're building a WYSIWYG editor live at Retool's Build Together event. Register here: eu1.hubs.ly/H0thS9v0 #Retool #InternalTools #CustomComponents

At a certain scale, enterprise creative teams run into the same wall. Output is high, tools are in place, and the work keeps moving, but campaigns slip, brand inconsistencies creep in, and nobody can quite explain where the delays are coming from. You'd think the problem is in the creative work itself, but it actually lives in the coordination around it: requests moving through chat threads, approvals scattered across email, assets distributed across tools that weren't built to connect. We wrote about what that looks like structurally, why tool consolidation alone doesn't solve it, and what a governed platform layer actually requires: eu1.hubs.ly/H0tddpQ0 #InternalTools #MarketingOperations #EnterpriseOperations #Stackdrop

@saxobank 's creative team was producing thousands of formats each year across 13 markets. The work itself wasn't the problem, it was the coordination layer underneath it. Requests, approvals, assets, and brand reviews spread across disconnected tools, with governance enforced manually outside the workflow. We built Launchpad on @retool to bring all of that into one place. Intake to delivery, brand controls embedded directly into the process. Full case study here: eu1.hubs.ly/H0t92mb0 #InternalTools #CreativeOps #MarketingOperations #Retool #WorkflowAutomation

Internal tools tend to slow down gradually: A page that loaded in a second starts taking five, then nine. People refresh constantly until they stop trusting the data, so they build workarounds. ⚙️ By the time it feels broken, the structural issues have usually been there for a while, just not visible enough to prioritize. We wrote about what causes this and how to fix it without rebuilding from scratch. Pillar 3 of our internal tool literacy series is live: eu1.hubs.ly/H0t4q0r0 #InternalTools #RetoolDevelopment #EngineeringLeadership