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

Hello, We have a self hosted Gitlab server. We would like to pull our containers from our server. Is this something DO would support in the future?

Options to set how long to keep backups or how many to keep would be nice or at the very least an option to select multiple backups to delete that way it would be easier to clean up older backups.

A similar notion on here was monitoring apps. Monitoring ports would also allow for ensuring that the app is responding to network traffic, and that things such as SSL certificates were valid or warn if they are getting near expiration. The opportunity to have a page for uptime and up/down service status purposes could also potentially be available in a future release.

At the moment, monitoring alerts can only be sent via email or Slack.It 'd be super nice to be able to set up web hooks for alerts. :)

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.

Powered with NVIDIA GPUs would be awesome for machine learning

Creation of cancel button command, to delayed or not response actions in the server.

If you have MySQL with master-slave setup and both are on the same physical host, you're totally screwed when there is a hardware failure - both master and slave are dead and there's no point in even doing replication. Or, if you have 2 Rails application servers and they are on the same host, it's an SPOF. In other words, whenever you have multiple droplets in a project, you need to confirm if any combination of droplets are on the same host or not. Right now, we have to write a support ticket to confirm if those droplets aren't on the same host. But it's been quite a hassle to do so, as all of our servers need such a redundancy. It would be great if there's a self-service way to verify that ourselves. Or better yet, offer a way to explicitly create a droplet on a different host. Right now, some customers might be at risk that unknowingly have multiple droplets on the same host and learn the hard way when it goes down, that it had been an SPOF. Nobody wins from this. This feature will save time for both customers and DO support staff. Win-win. For the record, Linode offers this by showing the host name (like newark313) on the dashboard.