Custom labs
Commission a private lab modelled on an application your team ships, graded like every other lab.
What custom labs are
A custom lab models your application's retrieval structure, tool schema and failure mode rather than using a generic stand-in. It runs inside your workspace and is assigned and graded like any other lab on the platform.
Custom labs is a Team plan add-on, currently in preview and enabled per organization. If you don't see Custom labs in your sidebar, ask us to enable it. It's for teams who've worked through the public catalogue and want a lab to match a pattern in their own codebase, such as a prompt builder, retrieval filter or tool validator.
How it works
Before building starts, a scoping call establishes the feature, vulnerability class and intended audience.
A build typically takes about two weeks after scoping. Once ready, the private lab appears in your workspace. Assign it as you would a public catalogue lab: to a person, a group, or a cohort, with an optional due date. See assignments for details.
Your data stays yours
The lab uses a sanitised stand-in for your application rather than your production system. No production data leaves your side at any point in the process.
Modelled, not mirroredThe scoping call captures your feature's retrieval structure, tool signatures and failure pattern. These are rebuilt in the lab, seeded with the flaw and graded.
What it costs, and how to start
A custom lab costs $499, billed once per lab. One year of support is included at no recurring fee, keeping the lab calibrated against current model behavior during that period.
Custom labs are priced and billed separately from your Team subscription. Commissioning one doesn't change your seat price. The process starts with a scoping conversation before purchase; see the pricing page for current add-on terms.