Core Compute Platform

I would like to suggest that DigitalOcean consider migrating its virtual machine infrastructure from Legacy BIOS to UEFI boot mode. This transition could offer significant benefits in terms of performance, enhanced security features, and broader compatibility with modern operating systems. UEFI provides faster boot times, support for larger disk sizes via GPT, and more advanced security measures such as Secure Boot, which helps prevent unauthorized or malicious code from running during the startup process. As more distributions and enterprise environments are shifting towards UEFI by default, this move could future-proof DigitalOcean’s platform and provide users with a more robust and secure experience.

It would be great if we could download a snapshot. I would use snapshot to replicate development environment on my local computer, I believe many others will do the same. Thanks

Currently, DigitalOcean is a no-go for any projects with the requirements to a) run GPU workloads and b) host/process data in Europe. GPU Droplets in the EU would open a lot of possibilities.

Why is monitoring limited to sending Uptime Alerts to emails attached to the DigitalOcean Team members? Please allow us to specify a custom email to receive the alerts. We use an Exchange Distribution group for this purpose.

It would be great if the new monitoring service also had webhooks. This would make it significantly easier for our orchestration service to respond to events and take action.

The Droplet Console uses SSH but does not support the latest SSH crypto config. This makes it difficult to lock a droplet down to only accept specific ciphers (which helps reject bot scans, though fail2ban is involved as well). The required crypto config for the Console is also not documented anywhere so it takes trial-and-error to get a minimal-but-acceptable configuration. This includes the Ciphers, KexAlgorithms, and Macs parameters for OpenSSH.

Add the ability to move backups across servers, zones, DCs, etc. and permit downloads for on-prem infrastructure including compute and storage.

After upgrade droplet OS to the new version, the older version is still listed in the control panel UI. The problem could be resolved in many ways: 1) Do not show the OS version for users at all; 2) Allow the user to write the OS version themselves; 3) Each droplet has a do-agent and a droplet-agent, but why can't they take the OS version and update the control panel UI?

Simply allow providing RISC-V ISA disk images to provide ISA longevity.