Retool HTML component events: why every handler fires at once
Why one click triggers every handler on a Retool HTML component, and how to route each event to the right one.
What we build
Internal toolsAdmin panels, portals and ops consoles
AI in productionAgents in queues and workflows, with audit on every model call
Workflow automationApprovals, handoffs and exports that no longer live in a spreadsheet
Data foundationsOne view over SAP, Salesforce and Snowflake, with safe write-backs
Rescue and migrationStalled builds and legacy apps: an audit first, then a realistic plan
Security and complianceSSO, RBAC and audit trails built in, not added before go-live
How we buildOur method
One method, four stages, from the first scope to long-term care. Jump to a stage:
Products LabVisit the lab
The products we have built and shipped ourselves. We feel the pain, build for our own team, then extract the product.
BlogHow we build internal tools, and whyCustomer storiesProof from the field — the numbers, the builds
Customer storiesAll storiesFeatured · CS.01Banking78.3% faster to market at Saxo Bank. Here is what changed..How Saxo Bank's creative operations team moved requests, approvals, and assets onto one platform and cut median time to market by 78.3%.Read the story
More stories
CS.02From a manual fraud queue to a daily risk scoreEducationCS.03Error monitoring in Retool, without a log leaving the regionTechnology