When you run JAX on a single machine, it works like an accelerated NumPy library. You run Python code, XLA compiles the computation graph, and your local GPU or TPU runs the kernels.
Everything shifts when you scale across several hosts. Process 0 spins up a coordinator to track worker nodes, while the cluster passes tensor slices over the network and caches compiled binaries on disk. If you do not configure these features deliberately, your cluster communicates in plaintext and can even execute arbitrary native machine code planted by neighbouring users.
Here is how those trust boundaries work and how to lock them down.
The Coordinator and Missing Auth
To run JAX across multiple nodes, you call jax.distributed.initialize() .…