Home/Environments/Self-hosted deployment
Self-hosted deployment

Deployed on your server, the data stays with you

The entire platform is installed in your own computer room or a cloud account you control. Account data, session records, materials and logs are all within your network, We don't handle it. The functions are the same as the cloud version, and the upgrade pace is up to you.

What it delivers

  • A working systemDeployed on the server you specify, including all functional modules
  • Deployment and acceptance documentationInstallation steps, configuration instructions, acceptance checklist
  • Operation and maintenance handoverOperation instructions for backup, recovery, capacity expansion, and daily inspections
  • restricted capabilities listWhich functions that rely on external services will be affected after privatization?
When it fits

When is privatization appropriate?

Compliance requires that customer data cannot be stored in third-party systems

After privatization, the data falls on your storage and we have no access channel. Log retention and access control can be linked to meet your audit requirements.

I already have a machine room and an operation and maintenance team, and I don’t want to buy another cloud service.

Use your existing server and network resources and plan deployment according to your capacity. There is no need to pay extra for platform-side resources.

To connect with internal CRM, work orders, and data warehouse

There is no need to go through the public network for connection within the same intranet. Interface calls and data synchronization are all done through the internal network. The link is shorter and easier to troubleshoot.

Don’t want product version updates to disrupt ongoing business operations

You can arrange the time window for the upgrade. You can verify it in the test environment before moving to production, instead of following the release rhythm of the cloud version.

What's included

What does privatization involve?

Data does not leave the intranet

Account information, session records, material files, and operation logs are all stored in your database and storage.

Full functionality migration

The five digital employee roles, environment management, account maintenance, publishing, private domain management and other modules are consistent with the cloud version.

Independent version upgrade rhythm

It’s up to you to decide when to install the upgrade package. You can skip versions, or you can stay on a certain version for a long time.

Dedicated operation and maintenance support

Provide on-site or remote assistance during the deployment period, and respond to problems in the agreed manner after delivery. The specific response method is determined in the contract.

Access your own resources

Agent lines, object storage, and SMS email channels can all be replaced with your existing services.

Connect to internal systems

Provides APIs and Webhooks to directly connect to your CRM, work orders, and data warehouses on the intranet.

Permissions and audit docking

It can be connected to your unified login, and the operation logs can be exported to the internal audit system according to your retention requirements.

Model access can be replaced

The AI part can receive model services purchased by you or models deployed on the intranet, and you are not forced to use our channel.

Process

Deployment process

You must confirm the server specifications and network plan because it determines the subsequent capacity limit and line availability.

01
Demand and capacity assessment

Estimate the required computing, storage, and bandwidth based on your number of accounts, number of concurrent environments, cloud phone requirements, and data retention time.

We make a plan
02
Confirm server specifications and network plan

Which machines to use, how to divide network segments, which overseas route to take, and how to issue certificates. These involve your computer room strategy and procurement, which is up to you.

Needs you
03
Environment preparation and installation

You prepare the server, domain name and certificate according to the list, and we complete the installation and joint debugging remotely or onsite.

Collaboration
04
Acceptance and trial operation

Follow the acceptance list one by one: receive a batch of accounts, run a round of account maintenance, post content once, and go through a private domain session.

Collaboration
05
Operation and maintenance handover

Backup and recovery, capacity expansion, log checking, and upgrade steps are handed over to your operation and maintenance one by one, leaving executable documents.

Delivery

If the specifications are set small, the machine will need to be shut down for expansion later. If the specifications are set larger, the cost will be paid upfront for unused costs. This trade-off depends on your account growth expectations and purchasing cycle, and we only provide an estimate.

Prerequisites

Technical prerequisite

You need to have these items. By writing it truthfully, you can first judge whether the threshold is enough, and you don't have to wait until you have had several rounds of conversations to find out that it is not suitable.

Server resources
Several independent physical machines or cloud hosts are required to host applications, databases, environment containers and storage. The specific CPU, memory, disk and number of units are calculated based on the size of your account.
Operating systems and runtimes
A container running environment and database service are required. Supported system versions and dependent component version ranges
Network and overseas routes
It requires available overseas bandwidth and allows binding different exits by account. Bandwidth recommendations and line requirements
Domain name and certificate
A domain name you control is used to access the backend, equipped with an HTTPS certificate. Self-signed certificates on the intranet are also possible, and the root certificate needs to be installed on the client.
Operation and maintenance cooperation
You need someone on your side who can operate the server, configure the network and certificates, and perform backups. This person is required to be online during deployment.
test environmentSuggestions
A smaller test environment for pre-upgrade verification. It’s not necessary, but if you have it, the risk of upgrading is much lower.
FAQ

FAQ

What capabilities will be restricted after privatization?

There are several places. Parts that rely on external services: If the AI ​​model is not connected to the external network, it must use the model deployed on your intranet, and the capabilities depend on the model you choose; you need to purchase the agent line yourself, and our shared agent pool is not provided with privatization; cloud phones require additional equipment resources or third-party cloud phone services, and pure intranets cannot provide equipment out of thin air. In addition, platform adaptation updates require you to actively install the upgrade package. After the overseas platform is revised, your version may be repaired some time later than the cloud version. These will be listed item by item in the plan.

Can you see our data?

No. The system runs on your network and has no return channel. During remote assistance, you are given temporary access rights, you can see the operation process, and it will be recycled after the end. If your compliance requirements prohibit any remote access, you can agree to only do documentation and phone support.

Are there any differences in functionality between the cloud version and the cloud version?

The modules and interface are consistent. The difference lies in the restricted part of the above column, and the arrival time of new features - the cloud version will be released first, and the private version will follow with the upgrade package.

Is the upgrade mandatory?

No. You can stay on a version for a long time. However, platform adaptation and security fixes are included in the upgrade package. Failure to upgrade for a long time will cause the operation of some platforms to gradually fail. You need to weigh this risk yourself.

How to calculate the price?

Privatization is quoted on a project-by-project basis, consisting of three parts: software licensing, deployment and implementation, and follow-up support, which are related to your scale and support methods. The resource costs of servers, bandwidth, and proxies are purchased by you yourself and not by us. For a specific quotation, a capacity assessment must be done first, and the consultant will give a detailed description.

Can I use the cloud version first and then move to privatization?

Yes, this is also the order we recommend. First run through the process in the cloud version and find out the actual usage, and the capacity assessment will be much more accurate. Existing data can be exported and imported into the privatized environment, and the migration plan will be confirmed during the evaluation phase.

Do a capacity assessment first

Explain clearly your account size, compliance requirements and existing computer room conditions, and the consultant will give you a server list and quotation details.