# Introducing OpenRL: A self-hosted post-training API for fine-tuning LLMs

DevFeed: [Introducing OpenRL: A self-hosted post-training API for fine-tuning LLMs](<https://devfeed.tech/articles/introducing-openrl-a-self-hosted-post-training-api-for-fine-tuning-llms-34311.md>)

Original publisher: [Read original article](<http://opensource.googleblog.com/2026/06/introducing-openrl-a-self-hosted-post-training-api-for-fine-tuning-llms.html>)

Author: Google Open Source (noreply@blogger.com)

Published: 2026-06-11T18:30:00Z

Content type: release

Language: en

Sources: [Google Open Source Blog](<https://devfeed.tech/sources/google-open-source-blog.md>)

Topics: [API](<https://devfeed.tech/topics/api.md>), [Fine-tuning](<https://devfeed.tech/topics/fine-tuning.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [Self-hosted](<https://devfeed.tech/topics/self-hosted.md>), [post-training](<https://devfeed.tech/topics/post-training.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Orchestration](<https://devfeed.tech/topics/orchestration.md>), [reliability](<https://devfeed.tech/topics/reliability.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [fine-tuning](<https://devfeed.tech/tags/fine-tuning.md>), [gke](<https://devfeed.tech/tags/gke.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [llms](<https://devfeed.tech/tags/llms.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [orchestration](<https://devfeed.tech/tags/orchestration.md>), [post-training](<https://devfeed.tech/tags/post-training.md>), [reinforcement-learning](<https://devfeed.tech/tags/reinforcement-learning.md>), [reliability](<https://devfeed.tech/tags/reliability.md>), [rl](<https://devfeed.tech/tags/rl.md>), [self-hosted](<https://devfeed.tech/tags/self-hosted.md>), [sft](<https://devfeed.tech/tags/sft.md>)

## AI overview

This article announces OpenRL, an open-source research preview from GKE Labs. OpenRL is a self-hosted training API for fine-tuning LLMs on a Kubernetes cluster, designed to separate post-training infrastructure from AI research workflows. The article describes potential benefits including concurrent reinforcement-learning jobs, improved GPU utilization, and simpler researcher workflows.

## Source excerpt

by Sunil Arora, Shuby Mishra & Chuang Wang, GKE We are pleased to share a research preview of OpenRL, a new open-source project coming out of GKE Labs. OpenRL is a self-hosted training API for fine-tuning LLMs on your own Kubernetes cluster. Why we built it If you look at agentic RL on LLMs, it is incredibly easy to get bogged down in system complexity. To run a single RL loop, you have to coordinate a dozen different things: selecting and cleaning datasets, choosing RL environments, debugging training loops, managing reward signals, handling inference mismatches, allocating hardware, and managing infrastructure. Picture looks something like this: Figure shows an AI researcher and an infrastructure engineer staring at the hurdles in post training along the way to the summit. Each of these is a hard problem. But what makes it more complex is how tightly AI research and infrastructure concerns are mixed together in today's tooling and frameworks. We believe decoupling the infrastructure from AI research can make these problems more tractable so that infrastructure engineers and AI researchers can independently tackle them. We have seen this pattern with Kubernetes where Kubernetes abstracted out the infrastructure and made application developers and SREs life easier. So, can you abstract out post training infrastructure? We believe so and drew huge inspiration/validation from Tinker (from Thinking Machines). The Tinker APIs for post training hit that Goldilocks zone where it hides all the post training infrastructure behind four key APIs: Figure shows high level components and their interaction in a OpenRL based RL workflow So the end result of this abstraction is that AI Researchers get full flexibility on their RL loop and infrastructure engineers can focus on scaling, orchestration, and reliability. OpenRL allows you to run the same training APIs but on your own infrastructure. And this decoupling has other interesting benefits. Sharing GPUs Traditional RL loops ar