Skip to content
DataWalk / Platform Overview

A platform for bigger questions.

An enterprise knowledge graph. Graph, relational and search in one engine.

Three ways to ask.
No three-way balancing act.

Meet the unlikely combination

Three questions to help you decide what to evaluate. No score or registration.

Answer all three questions to see an evaluation route.
01What does the answer depend on?
02How does the analysis develop?
03What must work around the analysis?

Consider source mapping, identity matching where needed, permissions, refresh and delivery to other tools.

A platform that breaks physics.

1 STATE Graph Relational Search

When more
means more.

Add a source. Change the model. Now keep every analytical engine in agreement.

When more
means less.

Graph, relational and search share one engine. There are no separate analytical engines to keep in agreement.

A whole category
of work. Gone.

When the model changes, reconciling separate analytical engines isn’t cheaper. It isn’t a job.

Why we break physics
Storage ≠ working memory

More graph
than memory.

Persistent storage holds the graph. RAM supports the work.

Under the architecture
Depth ≠ delay

Deeper.
Still subsecond.

Hop 6Hop 8Hop 10

Reported bounded tests: essentially flat per-hop latency from hops 2-15.

The workload. The results.
490 billion objects.

Scale deserves its own conversation.

About the figure

Bring the question
you’ve put off.

See it live