NewMCP agent API — drive Promenade from your own AI agent
Launch Promenade
Event data, process mining and your own knowledge flowing through Promenade into charts, process models and dashboards — and out as deeper insights, better decisions and greater impact.

Welcome to Promenade

Powering your
Process Intelligence

Based on decades of research. Built with the latest web technologies. Designed to be open, scalable, and accessible for everyone who wants to turn data into insights.

Launch PromenadeStart the guide
  • Research-driven

    Built on the foundations of process mining research

  • Modern & Open

    State-of-the-art web technologies and open standards

  • Scalable

    From classroom examples to real-world data

  • For Everyone

    Researchers, students and practitioners

  • No installation
  • Local-first
  • XES, CSV & OCEL 2.0
  • Tab → container → cloud
  • 35plugins in the library, every one installable in a click
  • MB → TBthe same workspace, from a sample log to a warehouse
  • 4plugin runtimes — WebAssembly, Python, SQL and views
  • €0forever — open source, with no paid tier above it

Scale

A tutorial log and a terabyte warehouse, in the same window.

Start on a five-megabyte sample in a browser tab. Point the same workspace at a container on your laptop when the log reaches gigabytes, or at an engine on your own infrastructure when it reaches terabytes. Same artifact tree, same plugins, same clicks — you change one dropdown.

a 5 MB sample~20–50 M eventsbeyond one machineterabytesIN THE TABON YOUR MACHINEON YOUR INFRASTRUCTUREBrowser engineDuckDB-wasm and WebAssembly plugins.Nothing is uploaded, because there is no server.Local Docker engineOne container, one command. Native pluginrunners, real threads, spill-to-disk.On-prem or cloud engineThe identical image, next to the warehouse.Your network, your keys, your audit trail.
  1. In the tab

    Browser engine

    DuckDB-wasm and WebAssembly plugins. Nothing is uploaded, because there is no server.

  2. On your machine

    Local Docker engine

    One container, one command. Native plugin runners, real threads, spill-to-disk.

  3. On your infrastructure

    On-prem or cloud engine

    The identical image, next to the warehouse. Your network, your keys, your audit trail.

Same discovery run, three engines — more data, and more throughput to match.

Browser · WASM5 MB log0.8 s15 K events/s
Local Docker · 24 cores4 GB log6 s6 M events/s
On-prem engine2 TB log41 s115 M events/s
  • The same artifact tree
  • The same plugins, unchanged
  • The same actions and views
  • One provenance graph across all of them

Data locality follows execution.

Move an artifact to an engine and the heavy data stays there. Only metadata, previews and the paged results you actually look at cross the network — so a terabyte log never has to become a terabyte download. Artifacts on an engine stay in the same tree, with a badge rather than a separate list.

How engines work
EnginesBrowser (WASM)readyLocal Docker · 24 coresreadywarehouse-eu · on-premreadyAdd an engine

One workspace, four ways in

Whether this is your first event log or your fiftieth paper

  • Learn

    I'm new to process mining

    A demo log is already loaded. Fifteen minutes from a table of events to a model you can explain out loud.

    Start the beginner track

  • Analyze

    I run process work in a company

    One export, one laptop, no procurement cycle. Rework, waiting time and conformance on your own data this week.

    Open the practitioner track

  • Research

    I work on process mining itself

    Object-centric techniques, exact alignments and runs a reviewer can retrace. Publish your technique as a plugin others install in one click.

    Open the expert track

  • Develop

    I'm building with Promenade

    Ship your algorithm as a plugin in Rust, Python, SQL or TypeScript. One manifest, one data door, provenance for free.

    Plugin quickstart

Capabilities

Built for real event data, not just demos

Every capability below is in the core open-source application today. Nothing here is a roadmap item or a paid add-on.

  • Runs in the browser

    A streaming parser feeds DuckDB-wasm; artifacts persist as compressed Parquet in the browser's own file system and survive a reload.

  • XES and CSV event data

    Import the formats you already have, map columns to case, activity and timestamp, and get a first model in the same session.

  • OCEL 2.0, first class

    Object-centric Petri nets, OC-DFGs, TOTeM, an object-centric Inductive Miner, replay and a metro-map view — not a bolt-on mode.

  • Conformance, exactly

    Alignment-based replay computes the cheapest alignment per trace variant. Exact, computed locally, and animated over the model.

  • Extensible to the core

    Algorithms, views, importers and exporters are all plugins — ours included. Yours installs exactly the same way.

  • Grows with the data

    When a log outgrows the tab, point the workspace at a Docker engine on your machine or one on your own infrastructure.