Hosted Lab Pages - Cybr Labs

Hosted Lab Pages give your learners a ready-made lab interface. Your platform obtains a signed launch link and sends the learner to Cybr. Cybr builds and maintains the lab page and the cloud environment. Your team does not build the lab screens.

What you build

Your integration identifies the learner and decides their lab access. A server request exchanges your mint secret for a signed launch link. Your website can show that link directly or embed a compact launch card. The card opens the full lab page in a new tab. The mint secret stays on the server. The integration guide includes the request, response, and browser events.

What Cybr provides

The hosted interface includes these features:

Lab controls: Start and end actions, deployment status, and a countdown.
Environment access: Connection details and optional web terminal access.
Learning content: Guides, knowledge checks, and available diagrams, videos, and resource links.
Completion: CTF flag verification and learner completion records.
Learner engagement: Ratings, feedback, and discussions where enabled.
Session recovery: Access to the saved deployment after a page reload.

Content and terminal availability depend on the lab. Discussions also depend on the hosted configuration. Cybr offers branding options for your organization. Branding arrangements are part of onboarding, separate from the signed-link API.

How this differs from SDK and REST integrations

	Hosted Lab Pages	SDK or REST API
Lab interface	Cybr provides and maintains it	Your team builds and maintains it
Integration work	Obtain a signed link and show it to the learner	Connect your screens to lab actions and data
Interface control	Hosted interface with available branding options	Your own layout, navigation, and interactions
Lab environment	Cybr manages it	Cybr manages it
Completion in your platform	Observe the embed notification or read completion through the API	Use API responses in your application

The SDK and REST API provide the same freedom to build your own interface. The SDK reduces API code for JavaScript and TypeScript. You can use Hosted Lab Pages for some labs and a custom interface for others. Both approaches use your organization’s lab access.

Signed-in and guest learners

A stable learner ID connects launches to the same learner over time. Your integration can use a signed-in session or a guest session. Without a learner ID, each mint request creates a new anonymous identity. Completion still belongs to that identity, but separate links do not share it. Automatically generated anonymous identities can read available discussions. They cannot post or delete comments.

Completion notifications

An embedded card can notify its parent page after completion. The message is a browser event, not a server webhook. A direct link does not install that relay on your website. The completion section explains the difference.

Before onboarding

Prepare these items:

Identify the labs your platform will offer.
Choose stable learner IDs and your free or premium access policy.
List the exact website origins that will embed the launch card.
Arrange the hosted branding options with Cybr.
Get your mint secret and endpoint URL from Cybr.

The integration guide explains how to use those values. For onboarding questions, contact support@cybr.com.

​What you build

​What Cybr provides

​How this differs from SDK and REST integrations

​Signed-in and guest learners

​Completion notifications

​Before onboarding