RL environments for everything frontier AI does through code

Expert-built, containerized environments to train and evaluate agents on long-horizon work across domains. Each comes with tasks, verifiers, proof of solvability and pass rates.

What’s in an environment

Each environment is a self-contained folder that runs the same way in your harness every time.

The goal and the end state, written the way an engineer would receive it. The config sets the time and resource limits and records difficulty and category.

instruction.md
my-task/
├── instruction.md
├── task.toml
├── environment/
├── solution/
└── tests/

Shown in the Harbor task format. We also deliver SWE-bench style task sets and match other formats on request.

What happens in each rollout

The agent gets the instruction, works in the container, and the verifier grades the result. Labs use the same tasks to train with the reward and to evaluate with the pass rate.

  1. 1

    Instruction

    The task is handed to the agent.

  2. 2

    The agent acts

    It reads, edits and runs code in the container.

  3. 3

    Tests run

    The verifier checks the final state of the environment.

  4. 4

    Reward

    The tests compute the reward for the attempt.

What we check before a task ships

Every task is reproducible, properly specified and solvable. We run frontier models on our tasks and record the pass rate. Reviews catch reward hacking, shortcuts and non-determinism.

Properly specified and genuinely solvable

The reference solution passes every test inside the container. A fairness review confirms tasks are hard, not unclear.

Verified outcomes

Tests check the end state, not the steps the agent took, and accept any correct solution.

Leak checks

We check tasks against public benchmarks and check that they haven’t leaked into pretraining.

Two-layer review

A peer checks the tests and the code. A senior reviewer then checks complexity, reproducibility and test coverage, with consensus on disagreements.

Reproducible

Versioned environments with deterministic resets, so every rollout starts from the same state and results compare across runs and models.

Calibrated

We run frontier models on our tasks and record the pass rate, so you can choose tasks by difficulty. Terminal-Bench style tasks pass the same CI checks and rubrics as the original benchmark.

Environments built for your lab

We build custom environments to your spec, for your domains and failure surfaces.

1

Scope

A researcher sets the domain, the task format and the target difficulty with your team.

2

Author

Engineers who do this work in their own jobs author the tasks, from new problems, open source pull requests or real freelance jobs.

3

Verify

Each task gets its tests and a reference solution, then a solvability review.

4

Calibrate and deliver

We record frontier pass rates per task and deliver in Harbor or your own format, with the trajectory traces from every run.

Pre-built RL environments

Containerized environments authored by experts from our network, each with its tools, a task and a verifier, in formats you already run.

Harbor task environments

Terminal-Bench 4.0

Harbor task environments

SWE-Bench Pro Hard

Very hard coding tasks on real codebases, set at expert level.

Harbor task environments

SWE-Lancer Hard

Real freelance coding jobs, with tests.

More collections on request.

See all datasets

Environments for everything frontier AI does through code

Software engineering

Build, debug, refactor and migrate real codebases.

Terminal work

Configure systems, fix builds, run services.

Infrastructure

Infrastructure as code, networks, pipelines.

Security

Find and fix vulnerabilities, harden systems.

Machine learning

Data, training, evaluation and serving.

Other work through code

Scientific computing and more, scoped with you.

Formats

Most collections ship in the Harbor format, so they run in the harness you may already use. We also deliver SWE-bench style task sets and match other formats on request.

  • Harbor format
  • SWE-bench style
  • Other formats on request

Authored by experts

Each environment is authored by an engineer from our network of 400,000+, matched to the domain of the task.

400K+Engineers in our network
10+ yearsSourcing and hiring elite engineers
By domainEach engineer matched to the work in the task

Research from our lab

Our research team runs frontier models on private task sets and publishes the results.

Leaderboard
Revelo research

Code Index

A live leaderboard on private collections that stay unpublished: SWE-Lancer, Terminal Bench 2.1 and 3.0.

FAQ

What does an environment ship with?
A container with the task, the repository and the tools, a verifier that computes the reward, a reference solution that proves the task can be solved, and pass rates measured on frontier models. Many collections also include trajectory traces with failure analysis.
How is task difficulty calibrated?
We run frontier models on our tasks and record the pass rate with the model, the harness, the attempt count and the grading method attached. A fairness review then confirms that failures come from the task’s difficulty, not from an unclear instruction or a broken verifier.
Do you check for contamination?
Yes. We check that tasks haven’t leaked into pretraining, and every run is logged and replayable.
Your environments share names with public benchmarks. Are they the same tasks?
No. They follow the same formats and domains, but the tasks are new. Terminal-Bench style tasks are authored new, SWE-Bench style tasks start from merged open source pull requests, and SWE-Lancer style tasks start from real freelance jobs. We check SWE-bench style tasks against public benchmark sets so they don’t overlap.
Which formats do you support?
Most collections ship in the Harbor format. We also deliver SWE-bench style task sets. If you need a format that isn’t on that list, we’ll match it.
Can you build environments for our domain?
Yes. Our applied AI research team scopes the domain, the task format and the difficulty with you, then builds the environments.

See an environment before you train on it

Request dataset samples before you license a collection.