Build explainable player journeys that survive real operational complexity.
Design event-triggered journeys with conditions, waits, branches, actions and goals. Jurnexus preserves durable execution state and the exact published version behind every player enrolment.
Marketing teams connect typed nodes on a visual canvas, validate the graph and simulate a profile before review. Published versions are immutable and new edits create a fresh draft.
Triggers, conditions, delays and event waits
Draft, review, approval and publish workflow
Safe simulation without real delivery
02
Persistent execution, not browser automation
Each enrolment stores its current node, scheduled actions and transition history. Idempotency and locks protect external actions when queues retry or workers race.
Durable timers and resumable waits
At-least-once safe effects
Controlled pause, cancellation and re-entry
03
Eligibility immediately before every action
The journey proposes an action; central decisioning makes the final call using current suppressions, pressure rules, channel posture and technical destination state.