Case Study
How Sella Delivers Scalable Credit Risk Explanations with Prometheux
Read More
Capabilities / Graph & Complex Data Processing

Hard Logic.
Huge Data.

Prometheux turns readable rules into parallel execution plans, so recursion, multi-hop joins and graph logic run at production scale. The same program runs on a laptop, across a cluster, and on GPUs.

Proven in production

Why complex workloads stall

Hand-Tuned Jobs.
Or a Real Engine.

Recursive and multi-hop logic is where hand-written pipeline code and SQL slow down and get fragile. Prometheux plans and parallelises it for you.

Hand-tuned PySpark / SQL
Prometheux engine
Recursion written as loops of self-joins, tuned by hand
Recursion is native: the engine iterates to a fixed point for you
Each new join path means rewriting and re-tuning the job
Write the rule; the engine compiles it to parallel, distributed jobs
Data is loaded into a new database before the job can run
Sources are read where they live; the engine runs the joins and recursion itself
Performance work lives in one engineer's head
Optimisation lives in the engine, so every rule benefits
Scaling up means re-architecting or loading data into a new database
The same program runs in local mode and across a cluster, and on NVIDIA GPUs
Results can shift with parallel execution order
Same input, same output, however many nodes run it
Distributed by design

Rules In.
Parallel Plans Out.

Vadalog Parallel compiles every rule into project, select and join primitives, then runs them as map, filter, reduce and shuffle transformations that run in parallel across a cluster. You describe the logic. The engine decides how to spread it.

Compiled for Parallel Runs

Rules become distributed transformations that run in parallel across your cluster, not row by row in a driver.

Recursion at Scale

Supply chains, org hierarchies and multi-hop dependencies run as recursive rules over graphs with billions of edges.

Read in Place

Iceberg, Parquet and your databases are read where they live, with no copy.

GPU Acceleration

With NVIDIA RAPIDS, Vadalog Parallel ran AstraZeneca's biomedical reasoning 9× faster on GPUs.

What this means for you ⟶

Talk to an engineer

Run the logic you avoided because it was too slow. Get results in seconds where batch jobs took hours. Spend engineering time on rules, not tuning.

How it runs

From Rule to
Cluster in Four Steps

01

Write the Logic

Express joins, recursion and aggregations as declarative Vadalog rules.

02

Plan the Execution

The engine turns rules into project, select and join primitives and optimises the plan.

03

Read Data in Place

Each source is read where it lives, with no load into a new database.

04

Run in Parallel

The plan executes as distributed transformations on your cluster, locally or on GPUs.

In production

Built for the
Heaviest Workloads

Pharma

GPU-Accelerated Reasoning

AstraZeneca reasons over millions of compound, gene and disease data points, 9× faster with RAPIDS and Vadalog Parallel.

NVIDIA blog →
Finance

Billion-Edge Graphs

A financial institution sped up critical reasoning tasks by more than 250% on graphs with hundreds of millions of nodes.

Graph analytics →
Risk

Network Risk

Fraud rings and multi-tier supplier risk need recursion over the whole network. The engine runs it in parallel instead of in nightly batches.

Data teams

Recursive Pipelines

Hierarchies, bills of materials and lineage graphs stop being special cases. They are a few rules the engine scales for you.

Speed Proven at Scale

“With Prometheux, we achieved a speed-up of over 250% on critical tasks involving complex reasoning over knowledge graphs with hundreds of millions of nodes and billions of edges.”
HR Head of R&D
Financial institution
“Prometheux technology powers highly scalable and explainable reasoning over some of the world's largest knowledge graphs.”
NV NVIDIA Technical Blog
Accelerating Neurosymbolic AI with RAPIDS and Vadalog Parallel
FAQ

Questions,
Answered

How does Prometheux execute at scale?

The engine compiles rules into project, select and join primitives, then runs them as map, filter, reduce and shuffle transformations in parallel across a cluster.

Where can the engine run?

On Databricks (as a native app or installed on your clusters), on self-managed Kubernetes, or in local mode for development and testing.

Do I need new infrastructure?

No. The engine runs on your existing Databricks clusters, on Kubernetes, or locally. There is no new database to load data into: it reads Iceberg, Parquet and your existing systems in place, and the engine runs the logic as distributed jobs.

Does it support GPUs?

Yes. Vadalog Parallel with NVIDIA RAPIDS accelerated AstraZeneca's neurosymbolic reasoning 9× on GPUs, as described on the NVIDIA Technical Blog.

Is it faster than PySpark?

For complex and recursive processing, Prometheux outperforms optimized PySpark, because recursion, planning and parallel execution are handled by the engine instead of hand-written loops.

How is this different from a fast analytical database?

Analytical databases are built to scan and aggregate quickly. Prometheux is built for the logic that SQL handles badly: recursion to any depth, multi-hop joins and graph rules, planned and parallelised by the engine, with deterministic results.

Bring Your
Slowest Job

Share the query that takes hours today. We'll show you how it runs as rules on the Prometheux engine.

We use some essential cookies to make this site work. By clicking "Accept All" you agree to the storing of cookies on your device to enhance site navigation, analyse site usage and assist our marketing efforts. For more detailed information see our Cookie Notice.

Accept AllDecline