> For the complete documentation index, see [llms.txt](https://docs.adaptiva.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adaptiva.com/patch/overview/saas-comparison.md). # 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. ## Advantages of SaaS deployment * Fully managed SaaS deployment of OneSite Patch. * Offloads infrastructure, updates, and database management to Adaptiva to manage. * Does not require any additional hardware. * Platform automatically scales. * Deployments receive the latest features, security patches, and improvements automatically, with no manual intervention. * Built-in redundancy and failover. ## Key Differences | Topic | Description | | ------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 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 removed settings along with new additions compared to OneSite Patch On-Premises. Please see our [Platform User Guide](https://docs.adaptiva.com/platform-guide) for more information regarding available settings. ![](/files/Axai6PdEuFaAZ1WdnV1j) The following settings have been removed from OneSite Patch SaaS: | Setting | Reason | | ------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | |

Adaptiva Content Publication

Cloud Storage

| Custom content is not supported in the SaaS environment. | | **Client Authorization** |

This is now managed by the Tenant.

For more information about managing Tenants, please see our Set up Tenant 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.

|