Not specific to DO but here are some checklist might helpful to you.
1.1. Elastic IP - Allow you to remap IP to another instance, this is very important for HA where you can bring up another server and remap IP to new instance.
1.2. Alternative to elastic IP is load balancer
2. Bock storage - Allow you to use persistent storage with redundancy. Important to keep data safe when some instances down. You can bring up new instance and start using existing block storage.
DO support all of the above so DO is good enough for production usage. If you need latency sensitive services like RDS, maybe you can consider AWS. I know some people use RDS with compute on other provider like DO.
it happens, and the legalities really vary from company to company. a few years ago there was the "startup logo generator" or something like that here on HN it got so bad.
also, let's say I work for Staples in customer support. Me and my 3 buddies use Flock to communicate at work using Flock, and send files back and forth...now "Staples uses Flock."
Yes, and? When you build a product hoping for bottom-up user adoption (as opposed to getting the CtO to make a company wide mandate) then its totally fair to do this. Half the hosting companies on earth have Disney and NewsCorp and Nike and Starbucks logos on their client pages because an employee used his work email to buy a $5 shared hosting account for his mom's blog.
Machine/deep learning based github/gitlab/bitbucket issue bot that auto label issue with "bug", "enhancement", or "question" label. Currently implemented machine learning(no tuning yet) part but no time implement bot part.
This post make me never use egdefs in any form.