​

Overview

Cerulion Graph Editor is a visual programming tool for building real-time data flow systems. Instead of writing glue code to connect components, you build a graph by placing nodes on a canvas and connecting them with typed data channels. Think of it as a visual IDE where you design your system architecture by drawing connections between components, and the framework automatically generates the communication code for you.

​

What is Cerulion Graph Editor?

Cerulion Graph Editor is a visual programming platform that lets you design data pipelines and workflows by connecting nodes on a canvas. Each node represents a computation unit (like a function), and you connect them with typed data channels called topics. The editor automatically generates the framework code needed to run your graph, handling all the low-level communication details.

​

Why Use Cerulion Graph Editor?

​

How It Works

Cerulion Graph Editor follows a simple workflow:

1. Design Your Graph: Place nodes on the canvas and define their inputs and outputs
2. Define Schemas: Create type-safe message structures that flow between nodes
3. Connect Nodes: Draw connections between node ports to create data flow paths
4. Write Node Code: Implement the logic for each node in Rust, Python, or C++
5. Generate & Run: The editor generates framework code and runs your pipeline

​

Key Concepts

Before diving in, here are the fundamental building blocks:

​

Nodes

Nodes are computation units—like functions—that run code when data arrives. Each node has input ports (on the left) that receive data and output ports (on the right) that send data. Nodes can be written in Rust, Python, or C++.

​

Topics

Topics are named, typed data channels that connect nodes. When you connect an output port to an input port, you’re creating a topic that carries data between those nodes. Topics ensure type safety—only compatible data types can flow through a connection.

​

Schemas

Schemas define the structure of data that flows through topics. They’re like type definitions that ensure all nodes understand the data format. Schemas are defined in YAML and can be shared across multiple topics.

​

Ports and Links

Ports are connection points on nodes—inputs receive data, outputs send data. Links are the visual connections you draw between ports, creating the data flow paths in your graph.

​

Triggers

Triggers determine when a node executes. By default, all inputs are triggers—when new data arrives on any input, the node runs. You can configure specific inputs as triggers for more control over execution timing.

​

Projects and Files

Graphs are organized into projects, and each project can contain multiple graphs. Files in your project define schemas, node implementations, and configuration.

​

When to Use Cerulion Graph Editor

Cerulion Graph Editor is designed for systems where you care about:

• Real-time behavior — Low-latency data processing and immediate responses
• Clear, inspectable data flow — Visual representation makes system architecture easy to understand
• Performance-oriented messaging — Zero-copy patterns and efficient data transfer
• Modularity — Rearrange components without rewriting wiring code
• Multi-language integration — Combine Rust, Python, and C++ components in one system

​

Prerequisites

You don’t need to be an expert, but you’ll move faster if you have:

• A basic understanding of programming concepts (functions, inputs/outputs, variables)
• Familiarity with one of: Rust, Python, or C++
• Comfort with data structures and types (structs, classes, fields)

​

Next Steps

Ready to get started? Follow these guides: