Data sovereignty and compliance
Meeting content, message history and documents stay in a specified region or data centre, with retention, encryption and access auditing defined by the organisation for internal audit and regulatory review.
Private deployment
Why put real-time collaboration on your own infrastructure
Private deployment is about control: where data lives, how systems integrate and how costs evolve. These are the points we discuss most with customers.
Core reasons
Four decision factors we see most often
In practice these factors appear together rather than on their own.
Network and system isolation
Where production networks are isolated or reachable only through dedicated links, public SaaS cannot be used directly. Private deployment can run entirely inside the intranet.
Deep integration and customisation
Account systems, org structures, permission models and approval flows differ. Private deployment allows message models, signalling flows and audit logic to be customised on top of them.
Long-term cost predictability
At steady, sizeable usage, self-hosted resources plus licensing are usually easier to forecast and budget than long-running usage-based billing.
Deployment models
Three common deployment approaches
The right choice depends on network conditions, data sensitivity and operational capability.
Fully isolated intranet
All components run in a network separated from the internet. Suitable for highly sensitive environments; upgrades and dependency distribution need internal processes.
- Isolated network
- Offline upgrades
Private or dedicated cloud
Deployed in customer-owned or dedicated cloud environments, balancing isolation with elasticity and centralised operations.
- Private cloud
- Central operations
Hybrid connectivity
The core data plane stays inside the intranet while only necessary signalling or operations channels are exposed, suitable for cross-site collaboration.
- Hybrid deployment
- On-demand egress
Private deployment tends to fit when
- Data cannot leave a specified region or data centre
- Accounts, permissions and audit need deep integration
- Long-term usage is steady and cost must be predictable
- You have infrastructure and operations staff available
Public cloud may be the better choice when
- You need fast validation with minimal upfront cost
- Volume fluctuates significantly and is hard to forecast
- You have no infrastructure or operations resources
- You want the vendor to own end-to-end operations and global access
Private deployment is not the default answer. During solution design we explain the costs and trade-offs of both paths honestly.
FAQ
What to confirm before implementation
What infrastructure is required?
Typically compute nodes, databases, object storage and network egress policy. The exact inventory depends on the products and concurrency involved, and we provide reference configurations and deployment documentation.
How are upgrades and maintenance handled?
Your team performs upgrades through your internal change process; FeiyanCloud provides release notes and technical support. Isolated networks need offline upgrade packages prepared in advance.
Can we run a small-scale trial first?
Yes. Teams normally validate a single room or a small pilot in a test environment before scaling according to the capacity plan.
Assess whether private deployment fits you
We will combine business scale, network conditions and compliance requirements into an executable recommendation.