Technical authority

Who builds RL environments, and who pays for them

Last updated November 4, 2026/Reinforcement learning environments

RL environment vendors and buyers are roles, and this page will not turn them into a directory. Someone holds the operational history. Someone may specify a task on top of a slice of it. Someone may want to attempt that task so an agent can be checked. Those can be three different parties, or two, or, inside one company, the same group wearing different hats. Paying is not the same as building, and building is not the same as owning the records. Big Data/Little Guy is none of the parties that take the dataset or deliver a running environment.

The types of teams that look for company records at all, still without logos, are which kinds of teams look for company operating data. What a buyer is shown before files exist is how an AI buyer reviews a dataset profile. Why a party that buys the archive in order to resell it is a different business from ours is how a licensing partner differs from a data broker. The object they are arguing about is defined on what reinforcement learning environments need from real work.

Why the role split matters before anyone talks about money

A finished environment is a designed object. The records it stands on are someone else's work. If the designer also claims to own the records, the company that lived the job has left the room. If the party who wants the check also writes the check, they can grade themselves on an easy miss. Splitting the owner of the history, the author of the task, and the team that wants a grade keeps those temptations visible. It does not, by itself, create a fair contract.

We sit beside that split as a licensing partner. Unlockt, LLC operates this site. We do not pay you for a finished environment, and we do not invoice you for one. What makes the work costly to specify is what drives the cost of an RL environment. That page has no rate card. Neither does this one.

The roles, without a roster

• The operator of the work. The company whose people took the actions and whose systems kept the endings. They decide whether a slice may be discussed. They are not required to become a software vendor.
• A task author. An internal research group, a specialist studio, or the operator's own staff might write the start, the moves, and the check. Writing it is design. It is not ownership of the history.
• A team that wants the check. Product groups shipping an agent, evaluation groups, or researchers. They may pay for the right to attempt a task. They are not entitled to the raw systems because they have a budget.
• A licensing partner. A party that can compare a profile with a stated need and stop when there is no fit. That is the role we claim. It is not a builder's role and not a buyer's role.

What we will not pretend to be

We will not list firms that sell environments, and we will not imply a relationship we do not have. We will not tell you a category of buyer is waiting. Why language-model agents need an environment explains a technical motive. A motive is not a purchase order. Concrete examples of environments drawn from business work shows task shapes, not clients.

Offers that blur the roles

• A vendor who asks for a full export in order to quote a build. The quote is premature, and the export is the risk.
• A buyer who wants the production console rather than a specified task. They are asking for access, not for an environment.
• A pitch that says the builder's fee includes the right to keep the records. That is a sale of the data wearing a services label. How a license differs from selling the data is the distinction.
• A promise that we will introduce a named laboratory. We describe types of need. We do not borrow reputations.
• Treating payment as proof the use is allowed. Whoever pays, the operator still needs the right to permit the slice. This page is not legal advice.

How a role conversation starts

If you operate the work, begin with the free data value check. It asks what you have. It does not appoint a builder and it does not find a buyer. If you are a team that wants tasks, the buyer-facing page is the right door, and you still will not receive files in order to shop.

A later profile can be shown to a type of need. It might match nobody. Empty is allowed. If there is interest, the operator still approves scope before any specification becomes a project. The steps for shaping an environment from company records are gates, not a staffing plan. You can refuse every role except the one you already have: you keep the company.