Experimental features
Experimental features give administrators early access to Kasm Workspaces capabilities that are fully developed but not yet Generally Available (GA). Each capability ships as a governed preview, tested first in non-production environments, with limited support and possible change or removal before GA. The program lets Kasm gather real-world feedback while customers preview upcoming functionality inside the Zero Trust Workspace Delivery platform.
What experimental features are
Experimental features are completed capabilities that Kasm releases ahead of General Availability to validate them under real workloads. A capability may deliver new functionality, performance improvements, or workflow enhancements. The same capability may also contain bugs, incomplete functionality, or untested edge cases.
The program serves three goals:
- Gather real-world usage feedback from production-representative deployments.
- Allow customers to preview and access upcoming functionality early.
- Accelerate refinement and stabilization before the GA release.
Experimental features are an opt-in preview channel, not a separate product tier. An Administrator enables the program for a deployment, then individual experimental capabilities become available within it.
Risk and support model
Experimental features trade stability for early access. A capability in this program has not completed the full validation that a GA feature receives, so behavior can change between releases. Kasm recommends testing each experimental feature in a non-production environment before enabling it in production.
Enabling the program carries explicit tradeoffs. When an Administrator enables experimental features, the deployment accepts the following conditions:
- Experimental features may contain bugs or fail to support every use case.
- Experimental features may affect system stability, performance, or data integrity.
- Support for experimental features is limited, and a feature may change or be removed without notice.
Test experimental features in a non-production environment first. Enabling them in production exposes live workloads to capabilities that have not completed GA validation.
The risk model is why the program targets evaluation and feedback rather than production-critical workflows. Treat each experimental capability as a preview that informs the final GA design.
Feature lifecycle
Each experimental feature moves through a defined lifecycle, tracked in the Experimental features index. The index records the version that introduced a feature, the version that ended its experimental status, and the current state.
A feature occupies one of three states:
- Active — the feature is currently available as an experimental feature.
- GA — the feature has graduated to General Availability and is part of the main platform.
- Removed — the feature has been removed and is no longer available.
When a feature reaches GA, Kasm documents it in the standard Kasm Workspaces documentation alongside other supported capabilities. A feature can also be removed at any time if it does not meet release criteria. The index is retained as a historical record of both outcomes.
Enabling the program
An Administrator enables experimental features from a single deployment-wide control in Admin → Global Settings. The setting is named Enable Experimental Features. Toggling the setting on prompts a confirmation that acknowledges the risk model described above. Toggling the setting off does not require confirmation.
After enabling the program, review the Experimental features index to see which capabilities are currently Active and which versions introduced them.
Current experimental features
The Experimental features index lists every current and past experimental feature, with its introduction version, status, and description. Consult the index for the authoritative, up-to-date list rather than tracking individual features here.