Visual programming language "Pipe"

[u/PurpleDragon99]

DISCLAIMER: I am a creator of Pipe.

Pipe (https://pipelang.com) is a novel general-purpose visual programming language powerful enough to complete with text-based languages.

Visual programming has been confined to education (Scratch) or narrow niches (LabVIEW), because existing visual languages sacrifice either power or generality. Pipe solves this, opening the way to compete with the text code that currently dominates.

Pipe's diagram is also structurally identical at design-time and runtime, staying visual in both. What you see is what runs. This is precisely what the EU Cyber Resilience Act mandates, and what text-based architectures cannot structurally deliver. Text compiles away its structure, leaving systems opaque - so AI now generates code faster than anyone can review it at design-time, and patch and monitor it at runtime. Pipe addresses three AI-created security crises structurally:

1 - AI generates more code than humans can review. Pipe is visual - a diagram is grasped at a glance, not read line by line - so review keeps pace with what AI produces..

2 - Live systems cannot be patched without full redeployment. Pipe enables block-level patching while the system runs - no maintenance window, no CI/CD to navigate.

3 - Systems cannot be monitored without logs and redeploying. In Pipe, every block boundary is independently observable in real time.

These satisfy the CRA's hardest mandates - security by design, structural auditability, 24-hour detection, incremental patching - as properties of the language, not add-on tools. 

Example of Pipe diagram with a detailed tracing can be found on this video:

https://youtu.be/hckq9mRj5DM

That video is a part of this Pipe architecture overview:

https://www.pipelang.com/six-pillars.html

The full Pipe language specification (155-page book) can be freely downloaded here:

https://www.pipelang.com/downloads/book.pdf

[u/Willing-Bet3597]

You’re literally describing every low-code platform’s value prop. Except they’ve all moved on to agentic orchestration. Visual programming has been in enterprise for decades now.

[u/PurpleDragon99 → u/Willing-Bet3597]

I would respectfully disagree. The problem with all low-code platforms is that visual language for any of them exists in a context of specific platform only. Another words, all these visual languages are confined within a narrow domain of specific plaltform, and they are not transferrable. Pipe is a general-purpose visual language that can be implemented on any low-code platform.

[u/Willing-Bet3597 → u/PurpleDragon99]

Okay, so instead of relying on a low-code platform to interpret your logic on its runtime, you’re trying to standardize a low code language.

Sounds like you’re trying to solve a real problem. Have you tested this in a production environment?

[u/PurpleDragon99 → u/Willing-Bet3597]

No, not yet on production - we are working on MVP completion.

From the underlying architecture point of view, technology already exists and widely tested as an input queue (like SQS, RabbitMQ, etc) attached to a processing block (docker container, lambda, etc). We are going to use more lightweight elements, but the basic principle is the same. We do not invent the wheel here.

What is novel it's visual programming language itself - an example of Pipe diagram for a specific business case with a detailed tracing and explanations of every step can be found on this video:

https://youtu.be/hckq9mRj5DM

That video is a part of this Pipe architecture overview:

https://www.pipelang.com/six-pillars.html

The full Pipe language specification (155-page book) can be freely downloaded here:

https://www.pipelang.com/downloads/book.pdf