DigitalOcean S-1
sec.gov
DigitalOcean S-1
1–10 of 442 posts
Re: DigitalOcean S-1
#2Re: DigitalOcean S-1
#3Re: DigitalOcean S-1
#4Re: DigitalOcean S-1
#5I don't think DO's offerings are strong enough to compete with the big players long term, especially in production.
Seems like an exit for a later acquisition by a bigger company, like Slack with Salesforce.
Re: DigitalOcean S-1
#6What is the point of DigitalOcean, Linode etc, when one can use the more reliable big cloud providers GCP/AWS/Azure. I don't think DO's offerings are strong enough to compete with the big players long term, especially in production. Seems like an exit for a later acquisition by a bigger company, like Slack with Salesforce.
Re: DigitalOcean S-1
#7Re: DigitalOcean S-1
#8Re: DigitalOcean S-1
#9A big red flag is that 570,000 customers bring in only 357m in rev. That's $50 a month for the average customer. That's way too low.
Re: DigitalOcean S-1
#10BUT:
1. Their web UI stability is terrible (constantly hangs and errors out)
2. Their hosted DB IOPS aren't competitive with other PaaS providers. There's also no way to scale DB size dynamically without upgrading to a new price tier which is overkill.
3. Their Kubernetes Control Plane scaling is obfuscated. I had to contact support to realize that the control plane nodes are somehow tied to the size of your node pool when you create the cluster? That's not documented anywhere and was the cause of many control plane timeouts.
4. No ALIAS dns record, no way to serve Spaces from an apex domain. (I know this is a vendor specific implementation but it's table stakes imo)
Again, I'm a (mostly) happy DO customer and wish them the best but if they really want to be seen on the same level as AWS or GCP in terms of some parity, they need to include some of these QoL features.