Retool

As James MacDonald takes on the Monuments Time Challenge, a team of Retool engineers built a custom dashboard to help his crew monitor everything from power output and heart rate to core body temperature, pacing, and navigation in real time. A very cool use of Retool, and an even cooler challenge to be part of. Good luck, James. We’ll be watching the dashboard and you!

See how flaschenpost SE is using Retool to replace a sprawling toolchain with a governed platform built to move from problem to working solution, fast → https://lnkd.in/gKeKtJ-f

Retail’s next decade is being built now, and we’re excited to help shape what comes next. At RetailClub AI Festival, we’ll be joining leaders from across the industry to talk about all things secure vibe coding and how it’s reshaping how retailers and global brands use software to run their business. If you’ll be in Huntington Beach September 22–24, add these Retool sessions at the Amazon Web Services (AWS) Theatre to your schedule: • Architecting Trust: Lessons from the Front Lines of Responsible AI with Retool, Anthropic and AWS hosted by Mike Blank and Kevin McCurdy • A Beautiful Constraint: How Global Brands Are Securing Vibe-Coded Apps with Retool and AWS hosted by Michael Blank and Kevin McCurdy • Retail AI in Production Can Your AI Agents and Apps Pass Security Review? hosted by Claire Bushnell and Phil Pinson And come find the Retool team at the AWS Grounds for a live demo. Retail and brand leaders can attend for free and receive up to $1,250 in travel and hotel reimbursement through the Breakthru Hosted Program: https://lnkd.in/gcErMFfw See you at the beach!

It's been about a month since Retool new app builder launched. Sure, AI can help you build *anything* but if you want something that works on your real data, and secure, you need it to live in Retool. As building proliferates across orgs, so do the security risks 😨 . You can start building anywhere (Cursor, Claude, Replit) and bring those apps into Retool. But you can also just build natively in Retool! This week, the team launched our first interactive App Gallery that features apps our team built that you can click into and even edit! Just this week, I built a brand tracker that auto-populates with fresh data from across our Paid, Social, and AEO/SEO teams to give anyone in the company an at-a-glance look at our brand awareness efforts. Try it out ➡️ https://lnkd.in/gMQ3JWtB

Our Senior Developer Advocate Angelik Laboy Torres tested whether an app could be built entirely by voice with no keyboard, only using Claude Code connected to Retool through MCP. The result was a published engineering onboarding tracker with role-based permissions built entirely through spoken prompts, and production-ready. Watch the full video ↓

Day 1: "We built it in hours." 🏎️ Week 3: "We need approvals, permissions, and audit logs." 🥴 The trick is not having to retrofit them later.

Three questions tell you whether you're actually governing AI, or just have a policy that says you do: Who's acting: human, agent-as-user, or agent-as-service? What can they reach: is that access scoped, or broad by default? Can you stay in control: deterministic rules, audit trails, bounded spend? If those answers come easily, governance is working. If they don't, you've found your roadmap. Eytan Lerba, who leads Product for Governance & Infrastructure at Retool, broke it down in a new blog post → https://lnkd.in/dnh9TuUz

So you built an app in Lovable, Replit, or Claude Code. Before it goes to production, here's what it still needs: Audit logging. Authentication. Source control. Access control. Server-side secrets. Dependency scanning. Parameterized queries. Governance for risky changes. That's eight things to set up and maintain for every vibe-coded app. Or deploy into Retool, where they're handled by default. Full checklist → https://lnkd.in/dins7adv

Governing what you build is the new build vs. buy. Angelik Laboy Torres breaks it down Aug 20 → https://lnkd.in/g6sJq_ey