OOMOL Studio
We built OOMOL Studio because we were tired of choosing between "easy to use" and "powerful enough."
As engineers, we love automation. We love chaining tools together to build pipelines, agents, and data flows. But whenever we tried to use existing "Workflow Platforms," we hit a wall.
"Why do I have to learn a proprietary JSON syntax just to write an if/else statement?"
"Why can't I just import a library? Why do I have to wait for the platform to support it?"
"Why am I coding in a textarea with no autocomplete?"
We realized that Low Code often meant High Frustration for professional developers. It abstracted away the things we actually liked: control, debugging, and the ecosystem.
So we decided to build something different. Not a "No-Code" toy, but a real IDE.
Our Design Philosophy
1. Code is the Source of Truth
We didn't invent a new visual language. We simply visualize standard code.
In OOMOL, a Node is just a Function. The inputs are arguments, the outputs are return values.
You don't "configure" a node; you write a function. The UI is just a reflection of your code's signature.
2. Respect the Tooling
We believe you shouldn't have to downgrade your environment just to use a visual tool.
That's why we embedded the full Monaco Editor (VS Code) into every node.
Intellisense, Type Checking, Linting, Formatting, and even full Debugging Protocol (DAP) support. It feels like home because it is home.
3. Containerized Deployment, No Artificial Limits
Traditional platforms run your code in a restricted, proprietary sandbox. If you need native Node.js modules or system-level tools, you're stuck.
OOMOL runs on Standard Docker Containers.
Need ffmpeg? apt-get install it. Need specific system dependencies? Just install them.
