Flexible deployment, without losing the platform.
FocalScope can be used in the managed cloud, as a hybrid setup, or in a controlled environment approved by your organisation. The difference is choice: your team can match the deployment model to its risk, governance, and operating needs.
Deployment options, explained simply
This page focuses on the practical differences between cloud, hybrid, on-premise, and Bring Your Own Cloud (BYOC). It explains where each model can help and what should be discussed before choosing one.
Why deployment choice matters →
Why some organisations need more than standard public SaaS.
Ways to deploy FocalScope →
Cloud, hybrid, on-premise, and BYOC in plain language.
What changes in practice →
Data location, ownership, rollout, and operating control.
Compared with standard SaaS →
The difference is less about features and more about control.
What still stays the same →
The FocalScope agent workspace and core channels remain familiar.
How it is scoped →
Controlled deployments are reviewed before any commitment.
Cloud, hybrid, on-premise, and Bring Your Own Cloud (BYOC)
The right choice depends on the balance your organisation needs between speed, internal control, operational overhead, and data governance. FocalScope can help you review the options before you decide.
On-premise
FocalScope runs in an environment approved by your organisation. This can help when customer communication, attachments, or records need to remain within tighter internal controls.
Best for: organisations with strong data-control, regulatory, or internal governance requirements.
Hybrid
A hybrid setup can combine local control for selected parts of the operation with managed components where they make day-to-day running easier.
Best for: teams that want more control without making every part of the service fully local.
Bring Your Own Cloud (BYOC)
FocalScope can be scoped for a customer-controlled cloud environment, where infrastructure choices sit closer to your own cloud policies and account structure.
Best for: larger organisations that want a dedicated cloud approach rather than a standard shared SaaS model.
Some organisations need more than one standard cloud model.
Customer communication platforms hold emails, attachments, call notes, internal comments, customer records, and operational history. For many teams, standard cloud is the right fit. For others, the deployment model needs closer review.
On-premise or hybrid can be useful when the organisation wants more say over where customer work sits, how access is managed, and how change is introduced across teams.
Data location choice
Discuss where customer conversations, attachments, and operational records should be held.
A better fit for IT policy
Align the deployment with the access, review, and ownership process your team already uses.
More controlled rollout
Introduce the platform in a way that fits departments, channels, and internal change windows.
Continuity for agents
Keep the FocalScope workspace familiar while the deployment model is adjusted behind it.
Choose the deployment model that matches the operating need.
The main difference is not the agent screen. It is where the platform runs, who manages the surrounding environment, and how much control your organisation needs.
On-premise
Runs in an organisation-approved environment when local control is a priority.
Hybrid
Combines selected local elements with managed components where that is the better operational fit.
Cloud
The simplest route when speed, lower internal overhead, and standard hosting are acceptable.
Bring Your Own Cloud (BYOC)
A customer-controlled cloud path, scoped with larger organisations that need a dedicated approach.
More control, without turning the page into an infrastructure manual.
The advantage of on-premise or hybrid is practical: more say over data location, access, rollout timing, and how the setup fits your existing governance. The exact model should be confirmed during scoping.
Access approach
User and administrator access can be planned around your internal approval process.
Network fit
The setup can be reviewed against how your organisation manages secure access.
Visibility needs
Reporting and operational visibility can be discussed as part of the deployment scope.
Separated environment
A dedicated setup can support clearer ownership than a generic shared workspace.
AI, where appropriate
AI Copilot can be included where it fits your data, approval, and operating requirements.
Change planning
Updates and rollout timing can be coordinated instead of treated as an instant self-service install.
The difference is control over the operating model.
Standard public SaaS remains the easiest route for many teams. FocalScope is different because larger organisations can also discuss hybrid, on-premise, or BYOC when their risk model needs more control.
Set by the vendor-hosted model.
Reviewed and agreed with your organisation.
Standard platform controls.
More room to align with internal processes.
Usually self-service or vendor-led cloud setup.
Scoped project with technical and operational review.
Shared public SaaS.
Dedicated, hybrid, on-premise, or customer-controlled cloud path.
Based on the vendor’s standard release approach.
Can be coordinated as part of the deployment model.
Limited to the vendor’s available hosting options.
Cloud, hybrid, on-premise, and BYOC can be discussed.
The deployment changes. The workspace stays FocalScope.
A controlled deployment should not mean a stripped-down experience. Email ticketing, live chat, voice, IVR, WhatsApp and messaging, social channels, AI Copilot, mobile access, and reporting can be included where they fit the agreed scope.
A controlled deployment starts with a proper review.
On-premise, hybrid, and BYOC are not one-click installs. They need a conversation about channels, users, ownership, rollout, and the level of control the organisation actually needs.
- Confirm deployment model
- Agree practical scope
- Review approved setup
- Plan access and ownership
- Start with what is needed
- Add channels by phase
- Align with internal process
- Avoid unnecessary complexity
- Plan agents and supervisors
- Support phased onboarding
- Coordinate testing
- Prepare handover