Developers
The built-in algorithms are plugins too
There's no separate, more limited API for external contributions. Inductive Miner, the directly-follows graph view, the OCEL 2 importer — all of them are plugins, loaded through the same manifest format and host contract available to you.
Runtimes
Pick the runtime that fits the algorithm
WebAssembly
Compiled typically from Rust. The default choice for performance-sensitive discovery and conformance algorithms.
Pyodide (Python)
Runs CPython in the browser. Fits algorithms that lean on the existing scientific Python ecosystem.
Relational (DuckDB)
For computations naturally expressed as SQL over the imported event data.
Contribution points
What a plugin can add
Actions
Take one or more artifacts as input (an event log, a model) and a set of parameters, and produce a new artifact — a discovery algorithm, a conformance checker, a filter, an exporter.
Views
Render a specific artifact type in the main canvas or inspector panel — a process-graph layout, a statistics table, a custom object-centric visualization.
Importers
Parse a file format into artifacts the rest of the application understands, following the same host contract as the built-in XES, CSV, and OCEL 2 importers.
Go deeper
Where to go from here
Plugin development
Write an action or view plugin, package it, and load it into a workspace.
Architecture
How storage, the artifact tree, and the plugin sandbox fit together.
API reference
The host data contract and UI contribution points available to plugins.
The full plugin SDK, type definitions, and example plugins are in themain repository, under plugins/.