Live data from Hacker News

DigitalOcean S-1

sec.gov

301–310 of 442 posts

Re: DigitalOcean S-1

#301
post #75
post #62

Earlier quoted context omitted.

Actually, Ben and Moisey owned a managed hosting company that was coming under a lot of pressure from rackspace. DigitalOcean as a product was a direct response to that market pressure. I think if you ask any of the early executives, none of us loooovveed the venture component, it was a way to grow the business that was already growing rapidly with strong product market fit. Remember, a16z only invested once we were…

I remember Linode being hesitant to dip below $20 because the thinking was that it would diminish the quality of support. That thinking was reinforced when you started with $10 (if I recall, it’s been nearly a decade) and we started getting large numbers of refugees burned by experiences with your support organization. Neighboring comments tell me it’s still a problem. We consciously didn’t want to grow $5 fast becau…

I've been a customer of both for years -- in Linode's case, since 2009. Your comments are coming across like sour grapes, so I think this is a good opportunity to hear about some of Linode's mistakes from a longtime Linode customer.

First, you guys had the customer support interface compromise in 2013, and the worst part about that was the way that it was handled by your organization. Linode wouldn't own up to the compromise initially, dragged their feet on announcing anything about it, and then tried to downplay it.

Then there was another similar incident in 2016, and, amazingly, the response from Linode was nearly identical to 2013. No lessons learned. After that, I started seeing influential people on HN say things like, "don't use Linode". I stayed on Linode, but I also started using DigitalOcean after the 2013 compromise and split my hosted services evenly between the two of you after 2016.

DigitalOcean aggressively iterated multiple aspects of their products in that time period. They announced block storage in 2016. Your customers immediately started asking when Linode would come out with a competing service, and that didn't happen until 2018. Here, it was Linode rushing to build a DigitalOcean feature.

Linode initially focused on expanding RAM and disk space for your customers' instances at the same price points. Every year, you'd announce, "hey, we're doubling your RAM!" or some such thing. It was awesome, but I also thought at the time that you were shooting yourselves in the foot. How many customers looked at that and went, "yep, cool, now I can downsize my Linode and give them less money each month"? I know I did, at least a couple of times.

Then, you chose to try to compete with DigitalOcean on price. As a long time Linode customer, I never wanted that. If I want a $5 VPS, I'll just go to DigitalOcean. Hell, you shouldn't even want me as a customer for $5. Let them deal with me instead. I wanted Linode to be the larger, slightly more expensive provider with the even better support.

I've had to deal with Linode support a few times over the years. They've mostly been awesome and first class. I've never been unhappy enough with Linode to want to leave altogether. Both of you should be focused on eating AWS, not each other; showing up to a competitor's HN thread to complain about them being copycats is really poor form.

Re: DigitalOcean S-1

#302
Public companies are when private companies have grown to the point that the leaders don't know what to do with it and can't figure out how to compete any longer.

Re: DigitalOcean S-1

#303
post #159
post #93

Earlier quoted context omitted.

> it was a product that looked remarkably similar to ours As a developer, DO never looked anything like it. Linode was expensive and on the same playfield as Rackspace and a ton of other cloud hosts, very different from the instantly-spin-up-a-tiny-vm-for-five-bucks model. Their web UI also has always been miles ahead. The competition also didn’t have SSD as an option until much later, and that was a HUGE selling poi…

> As a developer, DO never looked anything like it. The UI, the simplicity, SSDs, additional block storage... but also the API and its doc, as well as IPv6, regions, snapshots/backups, and availability. Later on, load balancers, object storage and k8s. All of that much simpler than AWS and both better thought out and more featureful than Linode or OVH. DO truly deserved their success.

DO definitely had UI, SSD first. But Block Storage, Regions, Snapshots Backup and Load Balancer all were either first on Linode or being worked on for a long time. Linode also had Pooled Transfer and other tidbit for a long time well before DO.

Remember we are talking about early days of DO. Of course later DO innovate more and Linode had to follow. And the new Linode UI is arguably better than DO. Although it did took them years to make it. The beauty of competition.

Re: DigitalOcean S-1

#304

Earlier quoted context omitted.

Whether your claim is true or not, there’s more to a product than the underlying technology. Frankly, this line of discussion reads as sour grapes and reflects poorly on the Linode team.

I don't think it reflects poorly on them at all. When DO started everyone still used the help document of Linode and Slicehost to setup and spin a server on DO. They could do that because DO was a clone of these services. To their credit DO improved and grew, and that's no mean feat.

Yes. For those of us that actually went through the Slicehost, Linode era, the time when paying per month and not per hour for a simple VPS before everything was rolled into the word Cloud. Those comment read more like an accurate account of history while others read it as an attack of a company.

Re: DigitalOcean S-1

#305
post #32

Interestingly it was very clear at around $10MM ARR that DO was on a trajectory to IPO. You can thank Moisey Uretsky for a fantastic product idea and his brother Ben for CEOing it for so long. Congratulations to everyone who was involved in building DigitalOcean, it was an INCREDIBLY wild ride in the early days, lots of chaos but through all the chaos and disfunction, I think everyone involved knew this day would com…

I remember interviewing with DO back in late 2014 and it was nuts! The entire interview process took ~3 months and it was clear that they were defining the process as they went. The entire process was basically: 1. initial call with recruiter 2. homework project 3. call with engineer to discuss said homework project 4. two phone screens with engineers 5. onsite interview with 6 engineers Finally I had was at the fina…

Not to hijack this sub-thread, but just a general question: how does one deal with unethical 'homework projects'? I've had a case during an application where I was given a 'homework project' that seemed to me very much not like a theoretical scenario, but more like the company wanting me to do free work for an actual real-world issue they had. Have people had situations where you suspected the same? How do you deal with it?

Re: DigitalOcean S-1

#306
post #32

Interestingly it was very clear at around $10MM ARR that DO was on a trajectory to IPO. You can thank Moisey Uretsky for a fantastic product idea and his brother Ben for CEOing it for so long. Congratulations to everyone who was involved in building DigitalOcean, it was an INCREDIBLY wild ride in the early days, lots of chaos but through all the chaos and disfunction, I think everyone involved knew this day would com…

The best year of my career was at DO in 2014/15. We were growing like a weed. It was hard to appreciate the magnitude of the growth until I compared it to everywhere I've worked since.

It was a heck of a lot of fun. Thanks for bringing me on board.

Re: DigitalOcean S-1

#307

Earlier quoted context omitted.

I remember interviewing with DO back in late 2014 and it was nuts! The entire interview process took ~3 months and it was clear that they were defining the process as they went. The entire process was basically: 1. initial call with recruiter 2. homework project 3. call with engineer to discuss said homework project 4. two phone screens with engineers 5. onsite interview with 6 engineers Finally I had was at the fina…

Not to hijack this sub-thread, but just a general question: how does one deal with unethical 'homework projects'? I've had a case during an application where I was given a 'homework project' that seemed to me very much not like a theoretical scenario, but more like the company wanting me to do free work for an actual real-world issue they had. Have people had situations where you suspected the same? How do you deal w…

If it were me I would be like: "here is proof I completed it and that it works, source code contingent on my being hired ;)"

Re: DigitalOcean S-1

#308

Earlier quoted context omitted.

I'm really happy to see Ben and Moisey get this far. They are both extremely competent sysadmins and system architects too. They retained a lot of equity as well - good to see.

Between the two of them, they own less than 20% of the company. Is this a lot? Not in my opinion. They sold 80% of their company.

They are also in the holding co

Re: DigitalOcean S-1

#309

I might have mentioned this before, but DigitalOcean's support is (or was, before I stopped being their customer) absolutely abysmal. I had a default card set up for auto billing. That card expired. I went to remove the default card -- you cannot remove a default card. Okay. I added a new card and tried to set it as default. It didn't take. (Refreshing the browser reverted the change.) So I tried another browser, ano…

My support issue was that I had a dead box and needed it to be available again. Their system thought it was up, but I could not reach it. There was no live support, just submit a ticket and pray. They need real-time support. I’m fine paying for it. Hell, bill me per minute, but I needed eyes in the issue. Instead of waiting for some unknown time for a support response, I deleted my stuff and rebuilt everything. If this were backing a commercial offering of mine, this would be unacceptable.

Re: DigitalOcean S-1

#310
post #32

Interestingly it was very clear at around $10MM ARR that DO was on a trajectory to IPO. You can thank Moisey Uretsky for a fantastic product idea and his brother Ben for CEOing it for so long. Congratulations to everyone who was involved in building DigitalOcean, it was an INCREDIBLY wild ride in the early days, lots of chaos but through all the chaos and disfunction, I think everyone involved knew this day would com…

I remember interviewing with DO back in late 2014 and it was nuts! The entire interview process took ~3 months and it was clear that they were defining the process as they went. The entire process was basically: 1. initial call with recruiter 2. homework project 3. call with engineer to discuss said homework project 4. two phone screens with engineers 5. onsite interview with 6 engineers Finally I had was at the fina…

I was bored so I clicked on the key proof in your profile and it says it's been revoked.
Post reply on HN