
2026-08-08 by Chris
Some names grow with you. Some names you grow out of. Wanderer was a good name for what we were building when we started. It captured something true: a system that moves through a graph, finding its way, following edges, exploring paths. There was poetry in it.
But as the platform matured, the name started to feel like it was describing the journey rather than the destination.
GraVersal is a portmanteau of Graph and Traversal. That is exactly what the engine does at its core: it traverses a graph, continuously and reactively, evaluating state and determining what should be active at any given moment. The name is precise without being dry. It says something real about the technology underneath.
Wanderer-Flow.de has moved to graversal.io. The platform is now GraVersal. The brand is new. The engine is the same one it always was, just with a name that fits it properly.
One thing stays exactly as it is: Wanderer remains the name of the runtime in the codebase. If you work with GraVersal at the programming level, you will still see Wanderer there. It lives on as the technical name of the engine itself, the part that actually does the traversal. That felt right. Wanderer earned its place in the code.
For everything external, though, the platform, the domain, the brand, GraVersal is the name going forward.
Naming is not just cosmetic. The old name occasionally created confusion about what GraVersal actually is. People expected a hiking tool, or a map editor, or yet another chatbot builder. Wanderer did not signal "graph engine" to anyone who had not already been told.
GraVersal does. It front-loads the core concept. Graph-native. Traversal-based. Reactive by design. The name gives new visitors an immediate, accurate intuition about what they are looking at before they have read a single line of documentation.
That is the kind of work a good name should do.
Title image: https://unsplash.com/de/fotos/neonlicht-beschilderung-andern-mG28olYFgHI