On-Premises Deployment
On-Premises Deployment refers to installing and running Surfly’s platform within an organization’s own IT infrastructure or private cloud, rather than on Surfly’s hosted SaaS environment. This gives organizations full control over data, security, and compliance.
What you need to know about On-Premises Deployment
On-Premises Deployment refers to a deployment model where the Surfly platform is installed and operated within your organization’s own controlled infrastructure whether that’s physical servers in your data centers, virtual private servers (VPS), or private cloud environments such as AWS, Azure, or Google Cloud.
Unlike Surfly’s standard SaaS (Software-as-a-Service) offering, where Surfly hosts and manages everything on its own globally distributed infrastructure, an on-premises setup transfers hosting, data management, and operational responsibility to your IT team.
This approach is often chosen by organizations that have strict security, compliance, or data residency requirements — common in industries like finance, healthcare, government, and defense.
How On-Premises Deployment Impacts Surfly’s Functionality
Opting for an on-premises deployment of Surfly gives IT and security teams direct authority over the entire application environment, from the network layer to the physical hardware.
Attain Maximum Data Control and Security
An on-premises installation provides a high degree of control over the security environment where co-browsing sessions occur. It allows organizations to enforce their own security protocols.
- All session data and network traffic remain entirely within the corporate network boundary, never traversing the public internet.
- The deployment can be integrated directly with internal security information and event management (SIEM) systems and other monitoring tools.
- This model eliminates the third-party data processor relationship for co-browsing, simplifying security and vendor management.
Meet Strict Regulatory and Compliance Mandates
For businesses in highly regulated sectors, an on-premises deployment is often a prerequisite for using collaboration technology. It directly addresses major compliance concerns.
- On-premises deployment satisfies data residency and sovereignty requirements that mandate customer data must be stored and processed in a specific geographic location or on company-owned assets.
- The self-contained nature of the deployment simplifies the process for internal and external audits, as all logs and infrastructure are directly accessible.
- It enables the use of co-browsing in air-gapped or other highly restricted network environments common in government and financial services.
Enable Deep Integration with Internal Systems
An on-premises instance can connect with internal applications and infrastructure that are not accessible from the public cloud. This allows for more cohesive internal workflows.
- Surfly can be configured to interact with internal-only CRMs, knowledge bases, or legacy systems that do not have public-facing APIs.
- Organizations can manage update and maintenance schedules in full alignment with their internal change management policies.
- Network routing can be optimized for minimal latency between the Surfly instance and other internal applications.
The importance of On-Premises Deployment
A Practical Example of On-Premises Deployment
Frequently asked questions about On-Premises Deployment
We’ve compiled answers to the most frequently asked questions about
On-Premises Deployment
.
In SaaS, Surfly hosts and manages the platform in its cloud infrastructure. In on-premises deployment, your organization hosts, manages, and maintains the platform on its own servers or private cloud.
Yes. Surfly provides comprehensive deployment guides, support during installation, and assistance with upgrades, though ongoing server maintenance and security patching are managed by your team.
Organizations typically choose on-premises deployment to meet strict data sovereignty or residency requirements, comply with regulations such as national banking laws or government security mandates, integrate with their internal security controls or identity management systems, and support operations in isolated or restricted networks where external internet access is limited or prohibited.
Yes. Some organizations choose a hybrid approach keeping sensitive operations on-premises while using Surfly SaaS for lower-risk use cases or external customer interactions.