Data Stays Inside Your Network
Messages, users, groups and recording files all live on your servers and object storage, and you maintain the account system yourself.
Private Deployment
The same IM and real-time video (RTC) capabilities, deployed as a whole stack on your own servers: data stays inside your internal network, and accounts, messages and recordings stay in your hands. Delivered as offline packages or as container images-based deployment, with a plan built around your data center and network.
When Moving the System Back In-House Makes Sense
When data has to stay on the internal network, when data-center ownership is a hard requirement, or when you want to set the upgrade cadence yourself, public cloud is no longer the only option: same capabilities, a different delivery model.
Same Capabilities as the Cloud
The same server and SDKs: moving from cloud to private deployment does not mean rewriting your service, and APIs and data models stay unchanged.
Offline and Internal Delivery
The whole stack is delivered as an offline package or through an internal image registry, so installation and upgrades do not depend on the internet; deployment plans follow your data center conditions.
Upgrades on Your Schedule
Version upgrades follow canary and rollback steps, and you decide the change window, avoiding the uncertainty of automatic cloud upgrades.
Delivery Models and Deployment Shapes
Choose by network environment and data center conditions; what we deliver and how we support it stays the same.
Standard Private Deployment
Services and data are all deployed in your data center and reach users over the internet or a dedicated line, which suits most businesses.
- Full IM and RTC modules
- Horizontal scaling by node
- Standard delivery and annual maintenance
Fully Offline
Built for physically isolated environments: images and dependencies ship inside the installation package, and installation and upgrades never reach the internet.
- Offline install package and dependencies
- Import into an internal image registry
- Offline upgrade packages
Flexible Deployment Shape
Start on a single server, or go straight to a multi-server cluster or container orchestration; node count and topology follow your business scale.
- Single server / multi-server / containers
- Plan by data center and network
- Nodes assessed by scale
Deployment Architecture
All three layers run inside your internal network and only the access layer is exposed to the internet; the database and object storage reuse the infrastructure you already run.
Access Layer Your internal entry point
Load BalancerPersistent-Connection GatewayMedia Access NodeHTTPS and Certificates
Service Layer IM and RTC services
IM Messaging and RelationshipsGroups and Chat RoomsRTC Control PlaneRTC Media Plane (SFU)Recording and RelayCallback Delivery
Data and Storage Your existing infrastructure
relational databaseObject Storage (S3-Compatible)Message Storage ReplicasLogs and Monitoring
Base Environment
Start with a single server; the server side is delivered as container images images. The database is relational database, files and recordings live in S3-compatible object storage, and you can keep using your existing storage.
Network and Security
Internal network connectivity is enough and only the access layer is exposed; certificates, load balancing and access control follow your existing operations setup, and offline environments install from offline packages.
Client Integration
Keep using the cloud SDKs: point the server address at your internal entry point and the rest of the integration code is identical to the cloud service.
Capacity and node counts are assessed against your business scale; describe them in the form below.
Delivery Process
From requirements to acceptance and training, five stages, each with its own deliverables.
- 1
Discovery
Clarify the use case, concurrency, deployment environment and compliance requirements, then produce sizing advice and a capacity estimate.
- 2
Proposal
Set out module scope, deployment topology, delivery timeline and licensing model; sign the contract once both sides agree.
- 3
Environment
Prepare servers, database and object storage to the environment requirements, and open the necessary internal ports and domains.
- 4
Installation
The delivery team completes installation, initialization and load testing, and integrates the client SDKs, callbacks and metering data.
- 5
Handover
Confirm each item on the acceptance checklist, deliver the operations manual, and run one training session for operations and engineering.
Deliverables
- Server software packages and container images
- Installation, initialization and scaling scripts
- API documentation and client SDKs
- Operations manual: deployment, backup, upgrade, troubleshooting
- Acceptance checklist and implementation training
Annual maintenance covers version upgrade packages and ticket support; the exact scope is set in the contract.
Tell Us What You Need, Get a Plan and a Quote
Describe your use case and deployment scale, and a pre-sales engineer will confirm the environment and module scope with you.
Contact Us Directly
- Pre-Sales
- service@feiyancloud.com
- Sales Phone
- service@feiyancloud.com
Phones are answered 9:00–18:00 on business days; requests submitted through the form are answered within one business day.
Tell Us What You Need, Answered within One Business Day
Leave your contact details and deployment context, and a pre-sales engineer will come back with module scope, node estimates and a delivery timeline based on your data center conditions.
- Business scenario and concurrency (daily actives, peak sessions)
- Network environment: internal network, fully offline or a dedicated line
- Modules needed: IM, RTC, recording and callbacks
- Expected delivery date and acceptance method
Submitted requests enter the pre-sales queue and are answered within one business day; your details are used only for this conversation, see the Privacy Policy.
Private Deployment Questions
What environments do I need to prepare for private deployment?
A single server is enough to start, and the server side is delivered as containers. The database is relational database, and files and recordings are stored in S3-compatible object storage. As scale grows, nodes scale horizontally, and the persistent-connection gateway and media nodes can be expanded independently.
What is included in the delivery?
Server software packages and images, installation and initialization scripts, client SDKs, API documentation, an operations manual (deployment, scaling, backup, upgrade, troubleshooting), plus one implementation training session and acceptance support.
How are later upgrades handled?
Version upgrades run through offline upgrade packages or an internal image registry, with pre-upgrade checks, canary validation and rollback steps provided. The change window follows your operations cadence, and we never force an upgrade.
Can data on the cloud service be migrated over?
Yes. Users, groups and message history can be exported per app and imported into the private deployment instance, and migration scripts ship with the delivery package. During migration you can run dual writes or switch over in read-only mode to reduce the risk of downtime.
Does private deployment include RTC?
Yes. IM and RTC can be delivered together or separately; RTC private deployment installs the control plane and SFU media nodes, with recording and stream push enabled as needed.
See the Demo First, Then Talk Deployment
The demo environment matches the private deployment build feature for feature, so you can validate the experience before choosing a delivery model.