Retool vs Knock
Side-by-side trajectory, velocity, and editorial themes.
Retool fills in its AI-native React app builder
Retool's recent work orbits its new app builder, which lets teams generate production-ready React apps from natural language, MCP-compatible coding agents, or imported React code. The latest entries fill in that builder with React import and app protection, while the rest is admin-console reorganization and routine self-hosted release-channel updates.
The product is converging on agent-built, React-based apps as its forward direction, treating the visual builder as one entry point among several. Self-hosted customers keep getting parallel Edge and Stable releases, signaling Retool is keeping its enterprise base in step with the builder rewrite.
Expect the new app builder to absorb more of the legacy builder's capabilities and MCP-driven app generation to deepen, with admin tooling continuing to consolidate.
Knock is building an agent-and-environments layer on top of its notifications infrastructure
Knock is shipping fast on two fronts: an agent surface (trigger Knock from Slack, package reusable agent skills, build audiences via agent) and developer-workflow primitives (reusable input schemas, dynamic audiences that version and promote between environments, new partial input types). The throughline is making notification engineering programmable and agent-operable.
Knock is moving from a notifications API toward an agent-operable platform with environment-promotion workflows — audiences, layouts, and inputs all becoming versioned, previewable artifacts drivable from dashboard, CLI, or agent. Expect more agent-triggerable surface area.
Likely more agent-driven authoring (additional data sources, agent skills) and continued environment/versioning tooling; the Slack agent and CLI/agent build paths point to deeper automation of notification ops.
See more alternatives to Retool →
See more alternatives to Knock →