Labs: where the next Engine gets tried first.
Labs is the platform's research layer — experimental work, prototypes, and ideas that haven't shipped, kept separate from the Hubs people actually depend on every day.
Research, kept separate from production
Labs is where new ideas get tried before they're trusted: a new reasoning approach, a capability no Engine has yet, an experiment that might not work out. None of it is customer-facing. Labs is deliberately not a Hub and not an Engine — it's the space upstream of both, where something either proves out and graduates into an Engine, or doesn't and gets set aside.
Reliability and exploration need different environments
A Hub that people depend on for real work has to behave consistently. Research, by nature, doesn't — it's supposed to fail sometimes, that's how it finds what actually works. Labs exists so that exploration can happen honestly, without either slowing down or compromising the Hubs already in people's hands.
Upstream of Engines, several steps from a Hub.
Something in Labs becomes part of an Engine once it's proven reliable — and only then does it become available to any Hub. A Labs experiment is never wired directly into a live product.
None directly — and that's the point
Labs work isn't meant to reach a live product directly; it reaches one indirectly, once it graduates into an Engine. Today's Labs work includes the research feeding Academic Hub's research and assignment tooling, and further capabilities for the reasoning Engine that already powers Resume Optimizer and Interview Coach.
A Hub you can depend on, and one that keeps improving.
What ships has already been tested
Nothing reaches a Hub as a live feature until it has been through Labs first — the exploratory, uncertain phase happens somewhere that isn't a production workflow.
New capabilities, not just improvements
Labs is also where genuinely new Engine capabilities get their first attempt, before there's a Hub built around using them yet.
Labs → Engines → Hubs → Tools
Labs sits furthest from what a user directly touches. Research that proves out becomes part of an Engine; an Engine becomes available to any Hub built on the platform; a Hub applies it inside a specific Tool. Every layer between Labs and a finished product is a deliberate checkpoint, not a shortcut.
See what Labs research has already shipped
Resume Optimizer and Interview Coach both run on Engines that started as Labs research.