Cloud Provider Comparison
Although all cloud providers allow you to deploy any kind of bench and sites, some advanced features may not be available on all providers. Please refer to the comparison matrix below for a better understanding.
Comparison Matrix
| Feature | AWS | OCI | Hetzner |
|---|---|---|---|
| Basic Functionalities (Analytics, Monitoring, Server Management) | Yes | Yes | Yes |
| Add-on Storage (Add more disk space without upgrading server plan) | Yes | Yes (Requires Reboot) | No (Support planned for the future) |
| Disk Size Reduction | Yes (Mumbai Region Only) | No | No |
| Restriction on Plan Downgrade | No | No | Partially (Cannot downgrade to a plan with smaller disk size) |
| Automated Disk Snapshot (Retention Window – 2 days) | Yes | Yes | Yes |
| Server Snapshot (Allows automated recovery) | Yes | No | No |
| App Server Auto Scaling [Beta] | Yes | Yes | No (Support planned for the future) |
| Physical Backup for Large Sites during Site Update / Migration | Yes | No | No |
| Support | L1 & L2 (FC + Apps) | L1 & L2 (FC + Apps) | L1 & Limited L2 FC |
Support
For the Shared Instance plan, we provide limited L2 Frappe Cloud (FC) support.
Shared instances can experience variable performance. If the server reaches certain thresholds, it may be throttled, and there is no reliable way to distinguish whether performance degradation is caused by application-level issues or underlying server-level constraints.
As a result, if your site encounters performance-related issues while running on a shared instance, we will not be able to provide support for those cases.
We recommend using Shared Instances primarily for development and UAT environments. For production workloads, it is strongly recommended to use Dedicated Instances to ensure consistent performance and full support coverage.
FAQ
- Why is there no Add-on Storage support on Hetzner ? Hetzner machines usually come with a single root disk by default. Increasing disk size requires upgrading the server plan. We plan to add support for this in the future.
- Why does only AWS Mumbai support disk size reduction ? No upstream cloud provider natively supports disk size reduction. Frappe Cloud implements this feature, but it relies heavily on multiple EBS disks. During the ARM migration on the Mumbai cluster, all servers were migrated to a dual-disk setup, which enables disk size reduction only on AWS Mumbai servers.
- Why is there a restriction on plan downgrade on Hetzner ? This is an upstream limitation. On Hetzner, the root disk size increases with the plan size. If you upgrade the disk during a plan change, you cannot downgrade to a plan with a smaller disk. As an alternative, choose CPU and Memory Only Upgrade during a site plan upgrade.
- Why are Server Snapshots not available on OCI and Hetzner ?
Server Snapshots are different from Disk Snapshots. This feature allows users to take on-demand snapshots and restore servers directly from them, and it relies heavily on AWS APIs. Due to technical limitations, it is not yet available on OCI and Hetzner.
Note: We always keep snapshots of the entire machine for the last 2 days. In case of any issue, we can restore your server from these snapshots, although they are not visible on the dashboard. - Why doesn’t Hetzner have the Auto Scaling feature ? Auto Scaling is a relatively new feature and is still in beta. It has currently been rolled out only for AWS and OCI servers. Support for Hetzner will be added once Auto Scaling becomes stable across providers.
- Why is Physical Backup available only in AWS regions ? Database Physical Backup heavily depends on AWS EC2 and EBS snapshot features, which is why it is not yet available on other providers. Where Physical Backup is unavailable, we use Logical Backup instead. The main drawback is that backups during updates or migrations of large sites can take longer.