Brief Overview

WalkMe's Self-Hosting model allows core WalkMe end-user experiences to be delivered from customer-owned servers. This option is typically used when WalkMe cannot access the application environment, when WalkMe domains cannot be allowlisted, or when devices operate in air-gapped or restricted networks.

While core in-app guidance can be self-hosted, many administrative tools and analytics capabilities continue to rely on WalkMe's SaaS services.

Self-Hosting Model

Analytics and Insights Support

WalkMe Insights and analytics data are not fully self-hosted. To keep Insights functional in a self-hosted environment, data must still be transmitted to WalkMe servers.

Supported approaches include:

• Sending events directly to WalkMe servers (out-of-the-box SaaS method), or
• Using a proxy server to securely transmit analytics data from the customer environment to WalkMe

In proxy-based configurations:

• Insights data is encrypted and stored on WalkMe servers
• Admins access Insights data through WalkMe's SaaS Console
• The proxy server acts only as a secure intermediary and does not store analytics data long term

Some Insights capabilities are available only with additional licensing and are not enabled by default.

Insights Feature Availability

The following Insights-related features are supported in self-hosted deployments, typically through a proxy-based setup:

• Engaged Elements
  Supported through a proxy server.
• Tracked Events
  Supported through a proxy server.
• Reports
  Generated from data transmitted to WalkMe servers.
• Digital Experience Analytics (DXA)
  Supported through a proxy server.

The following advanced Insights features rely heavily on WalkMe's SaaS infrastructure and are not fully supported in self-hosted environments:

• Sessions Playback*
• Session Stream*
• UI Intelligence*

* Requires additional licensing and relies on SaaS-based processing.

Integrations and External Services

Some integrations can operate in hybrid mode, meaning they require limited connectivity to WalkMe servers to function.

• Integrations
  Supported in hybrid mode and require access to WalkMe services.
• IDP integrations
  Require connectivity to WalkMe servers.

Admin Tools

Administrative tools are not self-hosted and are available only through WalkMe's SaaS environment.

This includes:

• Console
• Admin Center
• Editor
• Support Site
• Community
• WalkMe Shield

The WalkMe Editor remains a desktop application that creates content locally. Content is shared and managed through WalkMe's SaaS services and then downloaded for self-hosted deployment.

DeepUI Support in Self-Hosting

Self-hosted deployments support DeepUI, with limitations depending on configuration.

• Partial support is available for on-premise self-hosted deployments
• Dynamic updates (such as elements and Lexicon updates) are not supported
• After a Builder Assistant ticket is resolved, content must be republished and a new self-hosted package downloaded

A more detailed breakdown of DeepUI functionality is available in the full on-premise DeepUI documentation.

In-App Guidance Support

Core in-app guidance components can be self-hosted, including:

• Smart Walk-Thrus
• Launchers
• ShoutOuts
• SmartTips
• Shuttles
• Surveys

Additional considerations:

• Onboarding Tasks store completion data locally. If a user clears cache or cookies, onboarding progress resets.
• Multi-Language files are included when downloading content for self-hosting.

ActionBot Support

ActionBot support varies by component:

• ActionBot container
  Can be self-hosted.
• User input to ActionBot
  When privacy mode is enabled, user input is stored locally and deleted after processing. Data is not sent to WalkMe servers.
• Preconfigured ActionBot responses
  Stored and delivered from WalkMe servers.
• Conversation data
  Not self-hosted. Conversations and message history are retrieved from and stored on WalkMe servers, which cannot be hosted on customer infrastructure.

Assets and Content Libraries

• Assets stored in the Assets Library on WalkMe servers are downloaded with the self-hosted package
• Assets uploaded to the Assets Library are publicly accessible
• TeachMe*, Desktop/Mobile Menu*, and Native Mobile* are not supported in self-hosted deployments

* Requires additional licensing and relies on WalkMe SaaS services.

Summary

The self-hosting model supports delivery of core in-app guidance, while analytics, administration, and advanced capabilities continue to depend on WalkMe's SaaS infrastructure.

Self-hosting is best suited for organizations with strict network or security requirements and the operational capacity to manage deployment, updates, and validation.