On-Premises Replication
On-Premises Replication allows you to continuously replicate data from your Frappe Cloud dedicated servers to infrastructure that you manage. In the event of a disaster, such as cloud infrastructure failure or internet connectivity issues, you can fail over to your on-premises environment and continue serving your sites.
This feature is currently in beta. It is disabled by default and must be enabled by the Frappe Cloud Support team before it can be used.
Requirements
- Dedicated Architecture Only – On-Premises Replication is supported only when your application server and database server are deployed separately. Unified server deployments are not supported.
- Feature Access – Submit a request through support.frappe.io with the list of servers where you want this feature enabled.
- On-Premises Server – You must provide and manage your own server. This can be a physical server or a virtual machine hosted on another cloud provider such as AWS or Google Cloud.
- Server Management – Frappe Cloud does not monitor or manage your on-premises infrastructure. You are responsible for maintaining its availability and health.
Pricing
This feature is currently available at no additional cost during the beta period. Pricing may be introduced in the future, and customers will be notified in advance.
How Replication Works
Frappe Cloud establishes a secure WireGuard peer-to-peer network between:
- Application Server
- Database Server
- Your On-Premises Server
Once connected, Frappe Cloud:
- Creates a replica of your database on the on-premises server.
- Synchronizes Docker images required to run your benches.
- Replicates bench files and application data.
- Continuously syncs new changes automatically.
Set Up On-Premises Replication
- After the feature has been enabled by Support, open your Server dashboard.
- Go to Server Actions.
- Select Manage On-Prem Replication.
- Follow the setup guide to configure your on-premises server.
- Start the replication process from the dashboard.
- Monitor the setup progress until replication is completed successfully.
After the initial synchronization finishes, all existing data is copied to your on-premises server, and future changes continue syncing automatically.
If the replication setup fails, contact support.frappe.io for assistance before attempting additional configuration changes.
Perform a Failover
Once replication is configured, a lightweight daemon runs on your on-premises server to assist with failover operations.
Access the failover dashboard at:
http://<your_on_prem_server_ip>:5000
From the dashboard you can:
- Monitor replicated benches and sites.
- Configure sites for failover.
- Stop database replication.
- Start serving your sites directly from the on-premises server.
After failover, each site is served on its assigned port.
Example:
http://<your_on_prem_server_ip>:8394
Stop Replication
If you no longer want to synchronize changes from Frappe Cloud to your on-premises server, open Manage On-Prem Replication and choose Stop Replication. This stops future synchronization while leaving your existing replicated data intact.
Regularly verify that replication is healthy and periodically test your failover procedure. This helps ensure your disaster recovery environment is ready when needed and minimizes recovery time during an outage.