Studio · Discover
Watch your real process emerge live.
Drop a CSV with case · activity · timestamp — or pick a sample. Everything runs on your machine. Nothing is uploaded.
or try a sample:
Event Log Guide
What your CSV should look like
Three columns are all you need. Each row is one event — one thing that happened to one case at one point in time.
case_idactivitytimestamp
ORD-1001Create Order2026-06-01 09:12
ORD-1001Approve Order2026-06-01 11:40
ORD-1001Ship Order2026-06-02 08:05
ORD-1002Create Order2026-06-01 10:33
ORD-1002Cancel Order2026-06-01 14:20
- ✓ case_id — anything that follows a process (order, ticket, invoice, patient).
- ✓ activity — the step that happened.
- ✓ timestamp — any parseable date/time.
What happens next
- 1Your file is parsed locally — never uploaded anywhere.
- 2We reconstruct a directly-follows graph of every step transition.
- 3Variants are ranked by frequency so the dominant path is obvious.
- 4Throughput, bottlenecks and basic KPIs surface in under a second.
No event log handy? Pick a sample above to see it in action.