Can I put a lock on a droplet to prevent inadvertent destroy?

I have some droplets that I’d like to ensure this never inadvertently happens (e.g. some intern etc.). Somewhat like the feature on Amazon EC2 instances. Does this feature exist, or are there any plans to introduce it? Thanks.


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Feature requests are taken by DigitalOcean here:

I don’t speak for DO. From what I’ve seen, only DO can put a lock on an account to prevent further actions and that’s when billing is involved. But it’s definitely not at a granular level like destroy. This feature would be interesting indeed.