Practical overview
When it fits
Consider OpenLake when building or adapting GPU-backed inference or training infrastructure and the need is a storage layer, rather than a model-serving application. The repository's most concrete setup path connects its KV store to vLLM.
Who it is for
- Teams operating vLLM inference on GPU hosts that want to configure OpenLake as KV-cache storage.
- AI infrastructure engineers evaluating persistent storage for training, checkpointing, vector, or context-retrieval workloads.
Documented uses
- Configure vLLM to write and read inference KV cache through an OpenLake store.
- Share a KV pool across GPU hosts using configured OpenLake nodes and ordered vLLM peer addresses.
- Evaluate a storage engine for training reads, checkpointing, vector workloads, or agent context.
Requirements & limits
The project repository is public and identifies the software as Apache-2.0 licensed. The README shows a Linux-oriented build path and identifies Rust 1.91 or newer.
- The documented inference integration is specifically a vLLM connector configuration.
- The quickstart uses same-host offload by default; cross-host use requires store configuration and ordered node addresses.
- The implementation is identified as Rust-based and built on
io_uring. - The README's throughput and latency statements are project claims rather than independent performance evidence.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Configure OpenLake KV storage for vLLM on one host
Start the OpenLake store and configure vLLM to use its connector for KV transfer on the same host.
Before you start
- A Linux GPU host with vLLM available.
- Python package installation and the OpenLake command
openlaked. - A model name for the vLLM serving command.
Steps
Install the connector with the command below.
pip install openlake-vllmStart the store with
openlaked.Set
PYTHONHASHSEED=0and runvllm servewith the README's--kv-transfer-configJSON, usingOpenLakeConnector,openlake_client.openlake_connector,kv_rolekv_both, node127.0.0.1:9400, and devicelocal.
Expected outcome
The documented vLLM configuration points its KV connector at the OpenLake store on the same host.
Guide limitations
- The quickstart defaults to same-host offload; a GPU fleet requires starting
openlakedwith a configuration. - This recipe covers the documented configuration steps, not a tested deployment or performance result.
Compare options for Model inference and serving
These projects document a common task and share a project role. This is a source-based comparison, not an execution benchmark or a guarantee of interchangeability.
| Project | Documented purpose | Platform | Access and requirements |
|---|---|---|---|
| Openlake | Configure vLLM to write and read inference KV cache through an OpenLake store. | Linux, Server | The project repository is public and identifies the software as Apache-2.0 licensed. The README shows a Linux-oriented build path and identifies Rust 1.91 or newer. |
| Morphingdb | Import a libtorch model and create predictions from values in a PostgreSQL table. | Docker, Linux, Self-hosted, Server | The README documents a Docker image and a build-from-repository option, followed by connecting to PostgreSQL and enabling the pgdl extension. |
| Gateway — pyadav | Send chat-completion requests to a provider through a common server endpoint. | Server | The repository is public and identifies the project as Apache-2.0 licensed. README installation instructions include binaries, platform package managers and Docker. |
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 11 October 2026
- Original website title
- openlake-project/openlake · Official homepage title · retained in its source language

