# Retrospective: Openblocks and the 2022 Push for Native React in Low-Code > How an open-source challenger attempted to redefine internal tooling architecture through native component integration **Published:** November 16, 2022 **Author:** Editorial Team **Category:** devtools **Tags:** Openblocks, Low-Code, Internal Tools, React, Open Source, DevTools **Canonical URL:** https://pseedr.com/devtools/retrospective-openblocks-and-the-2022-push-for-native-react-in-low-code --- In late 2022, the market for internal tooling platforms was dominated by Retool, yet a distinct friction point remained regarding architecture and vendor lock-in. Openblocks emerged during this period as a direct, open-source challenger, positioning itself not merely as a cheaper alternative, but as a technically superior option for React developers. By rejecting the industry-standard iFrame architecture in favor of native component integration, Openblocks attempted to bridge the gap between rapid low-code assembly and professional software engineering standards. This analysis revisits the platform's entry into the market, evaluating its technical claims against the broader shift toward developer-centric internal tools that defined the 2023-2024 DevTools landscape. The primary value proposition of Openblocks in November 2022 centered on architectural fluidity. While competitors often relied on sandboxed environments to execute custom code—primarily for security and stability—Openblocks argued that this approach hindered performance and developer experience. The platform claimed to offer "native connections to PostgresSQL, MongoDB, MySQL, Redis, Elasticsearch, RestAPI, and SMTP" \[translated\], facilitating direct backend manipulation without the latency or complexity often associated with proxied requests in SaaS environments. However, the defining technical differentiator was its handling of the frontend. The platform introduced a WYSIWYG editor populated with "50+ built-in components" \[translated\], a standard feature for the category. Yet, unlike Retool, which at the time relied heavily on iFrames for custom component isolation, Openblocks touted the ability to "share custom components via React and the Openblocks SDK" \[translated\]. This allowed developers to embed Openblocks pages directly as React components within existing applications, theoretically removing the boundaries between the low-code tool and the core product codebase. From a governance perspective, Openblocks attempted to address enterprise concerns early in its lifecycle. The documentation highlighted "Role-Based Access Control (RBAC), audit logs to track activity, and auto-save with recoverable history" \[translated\]. These features were essential for competing with established proprietary vendors, as they addressed the compliance requirements of larger engineering organizations looking to self-host their internal tooling stacks. Despite the robust feature set, the platform's maturity in late 2022 presented distinct risks. The custom component SDK was explicitly marked as "Pre-beta" \[attributed\], indicating potential instability for early adopters. Furthermore, the platform's philosophy was "JavaScript everywhere" \[attributed\], a stance that alienated non-technical business users but strongly appealed to engineers. This strategic choice highlighted a growing bifurcation in the low-code market: tools designed for "citizen developers" versus tools designed to accelerate professional engineering workflows. ### Retrospective Analysis: The Open Source Trajectory Looking back from the present day, the emergence of Openblocks in 2022 signaled the peak of the "open-source alternative" trend in DevTools. As economic conditions tightened in 2023, the prediction that companies would seek to reduce SaaS spend by adopting self-hosted solutions largely came to pass. However, the market consolidated around platforms with the most active communities, such as Appsmith and ToolJet. The technical argument Openblocks made regarding iFrames versus native React execution remains valid. The limitations of sandboxed code execution continue to be a pain point for complex internal applications. While Openblocks correctly identified the architectural demand for native integration, the volatility of the open-source ecosystem also served as a lesson. For enterprise buyers, the choice between a proprietary vendor (Retool) and an open-source project often came down to long-term viability and support rather than pure feature parity. Openblocks represented a critical moment where the definition of "internal tools" shifted from simple drag-and-drop interfaces to complex, developer-first environments requiring genuine code integration. ### Key Takeaways * \*\*Architectural Differentiation:\*\* Openblocks distinguished itself by rejecting iFrames, allowing for native React component integration and embedding, a significant technical shift from 2022 standards. * \*\*Developer-Centric Design:\*\* The platform prioritized engineers over business users, enforcing a "JavaScript everywhere" philosophy that required coding skills for logic implementation. * \*\*Enterprise Governance:\*\* Despite being an early-stage project, it included essential compliance features like RBAC and audit logs to compete with proprietary SaaS. * \*\*Market Context:\*\* The project's emergence coincided with a broader industry move toward self-hosted, open-source alternatives to combat rising SaaS costs. --- ## Sources - https://docs.openblocks.dev/ - https://github.com/openblocks-dev/openblocks