Distributed Polars on Ray Polars released polars-nanook-ray, a package that runs the distributed engine behind Polars Nanook inside an existing Ray cluster, letting standard Polars queries execute across Ray actors with the engine handling partitioning and shuffles. Users install polars-nanook-ray on every Ray node with a matching ray version, authenticate with a Nanook service account, and call .remote(ctx) on a query instead of collecting locally; the example starts a cluster with 2 workers of 4 CPUs and 16 GiB of memory each. The package targets preprocessing joins and group_bys that outgrow a single machine, replacing hand-written shuffle code built on @ray.remote tasks. TL;DR: Distributed Polars now runs on your own Ray cluster. Install polars-nanook-ray on your Ray nodes and your existing Polars queries run across Ray actors, while the engine takes care of partitioning, shuffles and scaling. Get started at https://nanook.pola.rs/portal https://nanook.pola.rs/portal . Ray https://www.ray.io/ is an open-source framework for scaling Python over a cluster of machines, and has become a common foundation for machine learning platforms: training, hyperparameter tuning, serving and batch inference all run on the same Ray cluster. Before any model sees data, that data has to be prepared. Cleaning, joining and aggregating raw tables into features is where many teams use Polars for its performance and ergonomics. As datasets grow, that preprocessing step outgrows a single machine, while the Ray cluster next to it has plenty of capacity. With polars-nanook-ray https://github.com/polars-inc/polars-nanook-ray your Polars preprocessing can use that capacity. It runs the distributed engine behind Polars Nanook https://pola.rs/nanook/ directly inside the Ray cluster you already operate. Why not just @ray.remote ? You can run open-source Polars on Ray today: split your data into partitions, wrap your Polars logic in @ray.remote tasks and fan them out over the cluster. For a simple map over files this works fine. It stops working as soon as your query needs data from more than one partition. A join or a group by needs all rows with the same key in the same place, so now you are writing the shuffle yourself: choosing a partitioning scheme, re-partitioning between stages, and wiring tasks together. You end up maintaining a small, hand-written distributed query engine next to your actual pipeline. Aside from the maintenance burden, you also miss out on many distributed optimizations Polars Nanook does. We think that should be the engine’s job, so with polars-nanook-ray you write a single Polars query and the engine plans it, partitions the data and shuffles between stages on its own. Ray does what it is good at: placing the Polars scheduler and workers as actors on your nodes and keeping them alive. Quickstart Already have a Ray cluster running? Install the package in the environment of every Ray node, with the same ray version as your cluster: uv venv source .venv/bin/activate uv pip install polars-nanook-ray ray==