Enso is a no-code interactive ELT and data-driven process automation tool. It lets you load, blend, analyze your data, and then automate the whole process, simply by connecting visual components together. DEMO: https://youtu.be/fQvWMoOjmQk
Author of data processing tools used by Pixar and Dreamworks. Haskeller, experienced in building compilers and GPU computing. Passionate about visual programming, aesthetics, and ergonomics. On a mission to empower people with tools to innovate and advance. Loves dogs.
Leader, software developer, physicist. Used to design materials to build 🚀 Now creates tools to open up new possibilities for people. Addicted to sports, 🐕 lover.
Enso (https://enso.org) is a visual programming language for Data Science, however, you do not need a programming background to use it. It lets you analyze, visualize, and automate data processing simply by connecting visual components together.
Currently, we’re focused on data analysis – data preparation, blending, and analytics (both in-memory and SQL). Oh, and Enso is, and always will be 100% Open Source and free for desktop use (download it here)!
https://www.youtube.com/watch?v=fQvWMoOjmQk
According to IDC, data analysts waste 44% of their time on repetitive manual work that can be automated. As a result, turning your data into knowledge is slow and error-prone.
We believe that the best explanation of Enso business applications is by providing a few use cases:
Most visual programming languages suck because they don't let you express abstractions. Try to build a complex pipeline and you'll end with an unreadable spaghetti of connections. It's like coding a web app in the assembler. I mean, you can do it, but no matter how much time you'd put into that, it will be complex to read, understand and reason about.
Enso is different. It allows you to express abstractions to manage the complexity. As a result, you'd never have more than 10-20 nodes on the stage in Enso (nodes are hierarchical). This is because Enso lets you create custom data types, custom components (functions), catch errors, using control version systems, etc. This is because Enso is a real programming language with a dedicated JIT compiler with some very unique characteristics:
We realize that currently, Enso still feels more like a developers tool rather than a business-user toolkit. We’re in the process of working on improving onboarding, making the documentation better, allowing people to easily share components, and adding interactive widgets on nodes (sliders, drop-down menus):