OneSite Patch SaaS comparison

Adaptiva offers both a self-hosted and a cloud-hosted (SaaS) model for OneSite Patch. This guide outlines key differences between the SaaS deployment and self-hosted versions.

Key Differences

• Object Handling and Workflow Execution

  In OneSite Patch SaaS, server and business workflows are restricted to prevent changes to the shared environment. These workflows must use already signed activities that Adaptiva has approved as secure.

• Custom Data Providers for Custom Dashboards

  Custom Data Providers cannot be created in the cloud environment. Custom Dashboards can use existing Data Providers. Subscriptions can be set up using existing Data Providers.

• Content Distribution and Publication

  Content distribution and publication is restricted to OneSite Patch content only. All content required by the server is stored and managed on a secure storage container in the Adaptiva CDN.

  Content distribution works the same in both cloud and self-hosted models. Content is delivered through P2P methods, with fallback to the built-in CDN for Adaptiva.

  Customers migrating to OneSite Patch SaaS will not be able to leverage Adaptiva content or ConfigMgr, Intune, or Workspace One content distribution and publication. Adaptiva content cannot be created.

• Client Communication and Authentication

  To ensure successful communication between clients and OneSite Patch SaaS, customers must enable outbound traffic to Adaptiva cloud URL's.

  • HTTP Proxy Configuration Allow outbound traffic to Adaptiva cloud URLs through any HTTPS proxies in your environment.

  • Firewall Settings: Open the necessary UDP ports in your firewalls to enable peer-to-peer content distribution between client devices. See Adaptiva Port Detail.

• Admin and Identity Management

  SaaS customers manage all administrator accounts and usage of identity providers (OIDC, SAML ) through the OneSite Cloud Portal. Administrator accounts can be assigned to roles within the tenant server.

• Support and Troubleshooting

  Customers cannot directly manage the tenant infrastructure in the OneSite Cloud Portal. Common requests that require redirection or escalation include unsigned workflows, admin or identity configuration changes, missing content due to Adaptiva CDN publishing errors, or integration issues caused by restricted APIs.

  Note

  Customers with complex RBAC setups may need specific adjustments.

• Migrating to SaaS

  Migration from self-hosted to OneSite Patch SaaS requires coordination across teams to assess workflows, scripts, RBAC roles, and content delivery configurations. Customers should consider the following when migrating to OneSite Patch SaaS: Intent objects will not be lost, but historical data will be lost.

  Note

  The SaaS deployment automatically re-acquires the current state, and all dashboards will populate quickly with current data during the migration from Self-hosted to SaaS.

Locations in OneSite Patch Saas

OneSite Patch SaaS changes the way you create and manage Locations compared to a self-hosted environment. For more information, see On-Premises Client Detection in OneSite Patch SaaS.

Settings in OneSite Patch SaaS

OneSite Patch SaaS has some additional settings compared to an on-premises server.

Self-hosted Server	Cloud Environment
The screenshot below displays all available Settings for the Self-hosted server. This can be accessed by going to the gear icon in the upper right of the Admin Portal.	The screenshot below displays the available Settings in the SaaS tenant. These settings can be accessed using the gear icon in the upper-right of the Admin Portal.

The following settings have been removed from OneSite Patch SaaS:

• Adaptiva Content Publication: Custom content is not supported in the SaaS environment.

• Client Authorization: This function can be found on the OneSite Cloud Portal tenant management page.

• Legacy Client Upgrade (Windows): The Adaptiva Client Upgrade is now released automatically after the tenant is upgraded.

  For more information see: Automatic Client Upgrade.

• Cloud Storage: Custom content is not supported in the SaaS environment, so there is no requirement for Cloud Storage.

• Sensor Offline Cache: The SaaS tenant manages the sensor control.

The following new option is available in OneSite Patch SaaS:

• Client Downloads: Provides links to download the installation media for all supported operating systems.

The following settings have additional functionality in OneSite Patch SaaS:

• Security page: This page includes everything from the Self-hosted server, including the following changes:

  • Administrators: All accounts must be created in the OneSite Cloud Portal and assigned a role on the SaaS tenant.

  • OIDC Providers and SAML Providers: Identity Providers using OIDC and SAML must be configured in the OneSite Cloud Portal.

• About page: This page is mostly the same between versions, with the following changes:

  • The Server Time Zone option was added to the SaaS tenant and may be set to your desired time zone.

  • The Synchronize UI State option was removed from the SaaS tenant.