Thought Leadership

Why Virtual Lab Flexibility Matters, and What It Looks Like in Practice

Jessica Varsames

Sep 29, 2026 - 5 min read

The most revealing test of a virtual lab platform often comes after the first successful launch, when someone asks it to support a use case you hadn’t planned for. A product demo may need to become a detailed proof of concept, a customer onboarding program may expand to partners in another region, or a product team may need a different configuration for testing. Much of the original work is still useful, but the requirements around it have changed.

That’s why virtual lab flexibility deserves attention during platform evaluation. The initial environment tells you whether the platform can support today’s task; the effort involved in changing it tells you what future requests are likely to demand of your team. Looking at environment creation, integrations, reuse, and user guidance together gives you a more useful basis for that decision.

What does flexibility mean when it comes to virtual lab platforms?

Virtual lab flexibility is the ability to adapt software environments, management workflows, and user guidance as requirements change, while reusing configurations and content you’ve already built.

Businesses use virtual IT labs to give prospects, customers, partners, and employees browser-based access to working software environments. A flexible virtual lab platform accommodates differences in what those people need to do and how you deliver that access. 

Below are four key areas where virtual lab platforms should offer flexibility to help your team adapt to changing demands.

Create environments that fit your business’s requirements

An environment built for a brief product demo may need substantial changes before it can support a prospect’s proof of concept (POC). The buyer might need to explore a different configuration or work through a scenario that wasn’t relevant to the original presentation. Similar requests arise when product teams need a particular setup for testing or when customer-facing teams introduce a new workflow.

CloudShare’s September 2026 release adds two AI agents that provide new ways to create these environments:

• Demo and evaluation environments: The Sales Experience Creation Agent lets sales and solutions engineering teams describe what they need to create, a POC, product demo, proof of value (POV), or a trial environment through a chat.
• Custom virtual IT labs: The Training/Custom Environment Creation Agent lets instructors and administrators build a custom environment without starting from an existing blueprint or working through a configuration wizard.

These capabilities are useful when adapting a standard setup would require substantial work. You can begin with the scenario you want someone to explore and use the appropriate creation agent to build an environment around it, then assess whether the configuration supports the task as intended.

Reuse environments and content as requirements change

The environment you create for an unusual request may turn out to be worth keeping. Once you’ve refined a configuration or written guidance that works well, being able to reuse it gives you a stronger starting point for the next product evaluation, onboarding program, or internal test.

CloudShare’s September 2026 release supports reuse at both the environment and content levels:

• Guided content: The Guided Journey Repository lets authors save and load Guided Journeys from a shared repository within a project. Authors working in that project can draw on established content when preparing another guided experience.
• Shared environments: New environment management options let users create a single training experience with three different blueprints to create a new dimension of instructor control and allow users to access multiple environments across a shared network. This new configuration can become a new default for subsequent experiences, directly within CloudShare.

Keeping configurations and guidance available as reusable resources gives you more control over what changes. For example, you might retain a prepared environment while adapting its instructions for a different audience, or update the software configuration while keeping guidance for a workflow that hasn’t changed.

Manage labs through the tools your business already uses

The effort involved in running virtual labs also depends on where that work happens. An administrator may manage resources through automation, while a developer spends much of the day in a development tool and uses an AI assistant to carry out routine tasks. When lab management fits those workflows, there’s less need to move between tools to complete related work.

The CloudShare MCP Server connects the platform to external AI assistants, integrated development environments (IDEs), and automation workflows through Model Context Protocol (MCP). This open standard lets compatible AI tools interact with external systems. In CloudShare, it provides control over environments, blueprints, and users without requiring a custom application programming interface (API) integration, including the ability to manage policies, like extending the life of an environment, while they’re running.

For teams building their own integrations, API Productization introduces a new V4 API structure and simpler documentation, beginning with the endpoints customers use most. This gives developers a clearer reference for connecting CloudShare to their own processes, with the available endpoints defining which actions an integration can perform.

CloudShare’s New Platform Navigation supports the work that administrators and instructors continue to do in the web interface. The redesigned left-hand menu makes it easier to move between environments, content, and account settings when preparing an experience or managing an ongoing program.

Adapt guidance to the people using your software

A customer exploring an unfamiliar product needs different support from a partner who already knows the core workflows. Language preferences and the availability of live help also affect how independently someone can use an environment. Flexibility here means being able to adjust the support around the software as well as the software configuration itself.

Three capabilities in the release address different parts of that experience:

• Language preferences: Multi-Language Support covers the Participant Viewer and Instructor Console in nine languages, including newly added Brazilian Portuguese, Russian, and Italian. Browser-based detection and a manual selector let people use their preferred interface language.
• Help with unfamiliar controls: Visual Guidance for CloudShare’s Virtual Instructor lets authors embed on-demand visual cues in lab instructions. A click highlights the exact interface element on the user’s screen, and authors can add this guidance without changing existing labs.
• Confirmation of progress: Script Validation Checkpoints let authors define checks that validate participant progress directly inside the virtual machine, including results that visual AI alone may not detect. Instructors can see each participant’s check results in real time.

These capabilities can work together in a customer onboarding or partner enablement program. An author might use visual guidance to help someone find a setting, then define a script checkpoint to confirm the resulting configuration. The instructor can use that evidence to decide where further assistance is needed, while users have guidance they can request as they work.

How to Evaluate Virtual Lab Flexibility

A useful evaluation should include a change to your original requirements. Start with an experience your business actually needs, such as a product evaluation or an isolated testing environment, and then introduce a second configuration or audience. This gives you a way to assess both the initial build and the work required to adapt it.

Ask the vendor to demonstrate the following with your scenario:

• Build an environment for a requirement that isn’t covered by an existing template, and identify the setup steps that still need manual work.
• Adapt that environment for a second use case, showing which configurations and guided content you can retain.
• Carry out routine environment and user-management tasks through the tools your administrators already use.
• Demonstrate the available language options and guidance with someone who is less familiar with the software.
• Define a specific task outcome and show what evidence becomes available when a user completes it.

Record which resources you reused, where you needed specialist help, and what you had to recreate. Those observations give you a practical basis for comparing platforms and estimating the ongoing work your programs will require.

CloudShare’s massive September 2026 release adds capabilities across these areas, so you can assess how environment creation, reuse, integrations, and user support fit together in your own process. To explore them, book a personalized CloudShare demo and bring a scenario that your current setup takes too much work to accommodate.