What it does
The SDK puts labs inside pages you already own. Your product, your LMS, your docs, your branding. The lab environment is real and runs on our side.
It covers the lab session from end to end: list the labs your organization can use, launch one for a learner, follow its status while it builds, hand back access, and end the session.
What you own, and what we run
You own the page: the layout, the copy, the design, where the lab sits in your learning flow.
We run the parts that are expensive to get right and easy to get wrong: account vending, isolation between learners, scoped permissions, temporary credentials, spending controls, and cleanup when the session ends.
Keys are scoped to your organization
An API key sees your organization's labs plus the shared Cybr catalog, and nothing else. Every launch made with it is attributed to your organization.
Keys are managed in the portal, where you can create, rotate, disable, and archive them.
When to use it
Use the SDK when the lab needs to feel like part of your product, and you have engineering time to spend on it.
If you do not, Hosted Lab Pages deliver the same labs on a page we run, and you can move to the SDK later without rebuilding anything.
See everything else that shipped on the changelog, or what's coming next on the roadmap.