Live data from Hacker News

HashiCorp – S1

sec.gov

241–250 of 277 posts

Re: HashiCorp – S1

#241
post #203

Earlier quoted context omitted.

Every one of the Facebook companies is a household name with hundreds of millions of users. The same cannot be said for the Alphabet companies aside from Google.

YouTube and Fitbit come to mind

Both are subsidiaries of Google, not Alphabet.

Re: HashiCorp – S1

#242
Is it just me that while I hear good things about their product, I don't find the need to use their product?

Do they have a product that has no good competition or is the first choice as a tool?

Nevertheless, nice accomplishment.

Re: HashiCorp – S1

#243

Earlier quoted context omitted.

If they wanted, they can expand easily to a lot more - which is probably what happened to them inside facebook anyways. Even then, they can still be insanely profitable per engineer.

> which is probably what happened to them inside facebook anyways I think initially they only expanded to ~50 engineers until 900M users. Even today they are estimated to have only ~500 employees (no idea what percentage of that are engineers).

LinkedIn lists 1823 people working at Whatsapp, not sure how accurate that number is, probably self-reported so could be lower/higher, but ~500 seems off. Employee count seems to grow 1-5% month-to-month.

Engineering is listed as 25% of those 1823, operations 8%, education 6% and business development 6%.

Re: HashiCorp – S1

#244
post #206

Earlier quoted context omitted.

> Consul - EVERYONE should use service discovery, cloud or not. Discovery means that you don’t know your service name? Or endpoints? How can one lose his service? Im def missing something :)

There are many scenarios where it's useful, but I will illustrate a simple and important one. When you do a rolling upgrade, a new service must be assigned to an available port different to the existing one. After starting you'll probably run some health checks, and once satisfied you'll want to switch traffic over to the new instance and halt the old. How do you tell the rest of your infrastructure what the new port…

I make a new stack, new VMs, new loadbalancer and just update dns record of the service from old stack to new. Thats blue-green.

Rolling is trickier, but still, native cloud solutions do not use service discovery, imho.

Re: HashiCorp – S1

#245

Earlier quoted context omitted.

TBH what I got out of this is that he’s got a simple solid setup that works for him. He clearly doesn’t burn time changing his setup often and that makes sense.

Nix is hardly simple

On the face of it not, no. But when you consider the immense power and versatility of it (you can do anything from setting up simple virtual envs to automatically deploying a multi-container setup on AWS), it starts to become a lot simpler than the sum of all the other tools that it replaces. Nix is a single principled idea, but can be used in so many different contexts.

Re: HashiCorp – S1

#246
post #203

Earlier quoted context omitted.

If F => M then doesn't G => A? Which is good, we don't want to have to go around calling them MAGNA!

Every one of the Facebook companies is a household name with hundreds of millions of users. The same cannot be said for the Alphabet companies aside from Google.

Oculus does not have hundreds of million users.

Re: HashiCorp – S1

#247

Earlier quoted context omitted.

I can’t believe there was a time where Microsoft wasn’t considered as big of a tech company as Netflix.

It wasn’t about size but about fast appreciating tech stocks. This was pre cloud boom MSFT

Exactly. Ten years ago people thought of MSFT more like INTC or IBM than GOOGL or AMZN

Re: HashiCorp – S1

#248
post #99

I love the products but that S1 didn't exactly blow my socks off. They are hemorrhaging cash and their growth strategy is pretty WeWork-ish. Seems to boil down to "Get more customers", "HCP is probably going to make money", and finally "the rest of the world needs hashicorp too"

They're making hundreds of millions of dollars per year. They have software economics, not commercial real estate economics. Most software companies are "hemorrhaging cash" by the time they file an S1, because if you invent a machine that turns nickels into dimes, the obvious thing to do is spend all your money making as many of those machines as you can, not cranking a small number of them for a small, consistent st…

> They have software economics, not commercial real estate economics.

I don't believe this. Snowflake for instance could be profitable if they chose and they have almost no debt. Furthermore their expenses grow logarithmically with their revenue. It doesn't cost much more to have 2 customers as it does to have 1, but the revenue doubles. Their services are an add-on that supplements the revenue from the platform. Its the growth in platform adoption that moves the earnings number.

>They're making hundreds of millions of dollars per year.

No they are losing 10's of millions of dollars a year. Revenue is not earnings. Wework had revenue of billions of dollars a year and but the cost of that revenue meant they had no path to profitability.

I see the same thing here. The bulk of their revenue come from selling services on top of their software. Services have a high COGS. For every service contract you sell you have to pay someone to service the contract. Your costs grow linearly with your revenue. This is the trap yelp fell into. Making billions by paying 95-105 cents for every dollar because opening a new market meant building all the infrastructure for that market.

If hashicorp can't find a way to make the growth in adoption of their software directly influence their earnings I don't think this is a good investment.

Re: HashiCorp – S1

#249
post #42

Holly mother of God. Mitchell was still on HN yesterday, as he was replying something about Backblaze IPO and its business. Today it is his IPO, $259 million revenue. 2100+ Customers, 1500+ employees, $10 Billion Valuation......... I mean I felt it wasn't that long ago Vagrant was "the" tool for the job. How it all started, the submission on HN [1], quote: > This project has been the love child of myself and John Ben…

> Edit: I wonder how many company started or partially started on HN that went on to IPO. I know Dropbox is one. Do we have a list somewhere?

Let's not make whether a company went public a metric for assessing quality. Going public is mostly a matter of how much a company expects the public to pay to get a share for the company. Also, it is a matter of how much the bank which facilitates the offering expects to make. Currently, the markets are sky high, so even not so good companies will make crazy amounts of money for the bank and the company which went public. Just look at the dot com bubble and the IPOs for more information.

Re: HashiCorp – S1

#250
post #210

I have actively used Vagrant, Consul, Terraform, and Vault and I really have never understood all the fanboyism for Hashicorp. Their products are OK but easily replaceable and often redundant in modern cloud providers. Wish them luck on their attempt to cash in but I for one do not intend to buy any stock.

I actually tend to agree, and am surprised that the discussion in this post is so breathless. Having used (and continuing to use) multiple Hashicorp products fairly extensively, they tend to have a lot of warts, just fewer warts than the alternatives. Terraform is a great example: * It's slow , and new versions often get slower. * Apart from the most serious ones, bugs often don't get fixed for years, and GitHub issu…

What's slow in your opinion? I assume it's either config evaluation or the state refresh?
Post reply on HN