The centerpiece of CRANQ's innovation is the Repo: it takes the gobal database of editable code of GitHub, the universal reusability of npm packages, and the ease of use of Zapier connectors, and blends them into an global, extensible component library that is accessible right from the CRANQ app.
Searchable contents of the Repo
Unlike GitHub, the code you find in the CRANQ repo can be put to use right away. The Repo is integrated into the IDE, and all CRANQ components share a common makeup of interface and internal structure. This allows you to just drag-and-drop anything from the Repo right into your program.
Unlike code on GitHub, CRANQ code is an actual database - the representations of hierarchical dataflow graphs - and thus, is a much richer medium than text code for expressing what components are expected to do.
Unlike npm, the CRANQ repo hosts individual components instead of packages of components. Your running CRANQ program will only contain code that it actually uses.
Unlike npm packages, CRANQ components are editable in place.
Unlike Zapier, the CRANQ repo is extensible without limit. Building new API integrations, data transformations, and webhooks are all possible without ever stepping outside CRANQ.
Unlike Zapier triggers, apps, and actions, CRANQ components are editable with sophisticated version control.
The CRANQ repo aspires to be the place where all future code will be stored and accessed with ease.
Last modified 4mo ago