Live data from Hacker News

JFrog S-1

sec.gov

21–30 of 67 posts

Re: JFrog S-1

#22
post #14
post #10

Earlier quoted context omitted.

For me JFrog is synonymous with Artifactory -- I think that was their earliest / bread & butter product? That may just be my interaction. It's an on-premise/cloud hybrid source artifact repository. The nice thing about it is that it is one product that can act as a maven/npm/pip/etc. repo. If you're in a polyglot org (big enterprise) and you have security needs/historical baggage to host on-premise (big enterprise) t…

What is an artifact in this context?

Anything your build server produces that you want to serve or archive. Binaries, packages, test results, etc.

Re: JFrog S-1

#23
post #14
post #10

Earlier quoted context omitted.

For me JFrog is synonymous with Artifactory -- I think that was their earliest / bread & butter product? That may just be my interaction. It's an on-premise/cloud hybrid source artifact repository. The nice thing about it is that it is one product that can act as a maven/npm/pip/etc. repo. If you're in a polyglot org (big enterprise) and you have security needs/historical baggage to host on-premise (big enterprise) t…

What is an artifact in this context?

A library. If you're familiar with pip or npm or the like, you've probably used public repositories. npmjs.org hosts all the free and open source node libraries. But a big org might have a loads of closed and proprietary libraries they need to share and version among multiple development teams or partners. A product like artefactory hosts those kind of libraries for multiple languages and is compatible with the popular package managers.

It's also like a local cache of public repos. That means faster builds, some level of quality control (ie black or white list of safe libraries) as well as protection against things like the leftpad fiasco or 2016.

Re: JFrog S-1

#25

With Helm, there is no need for Artifactory. You get Harbor, Verdaccio, etc. It is silly to pay a company 100k+ when all this stuff is easily managed using official or far more powerful tools.

What about things that arn't built on top of Kubernetes?

Those tools aren't built on Kubernetes, just easier to deploy in a production manner using the official Helm charts.

Re: JFrog S-1

#27
post #7
post #3

Earlier quoted context omitted.

this is very standard language. the goal with this section is just to cover your tracks so no investor can sue you for omitting something, regardless of the likelihood any of these risks ever come true.

Interesting. Everyone was giving Uber a lot of heat on HN for writing similar stuff in their S-1.

Yet, it's commonplace.

Re: JFrog S-1

#28
post #4

Three S-1's in one day, and the AirBNB prep last week. Is there just light shining, or are these companies worried about the future prospects of the IPO market?

In addition to what others have said, I think Amazon's Elastic Container Registry is a huge threat to JFrog's prospects. Perhaps they need to IPO now to gain access to the deep pools of capital they'll require to face down the threat from Amazon. Or maybe this is one of those IPOs like SendGrid that is fairly quickly followed by an acquisition.

Re: JFrog S-1

#30

With Helm, there is no need for Artifactory. You get Harbor, Verdaccio, etc. It is silly to pay a company 100k+ when all this stuff is easily managed using official or far more powerful tools.

That's not necessarily true. Helm is a way to install things, it is not a replacement for an artifact store. Binaries are still required. Besides, not everything can be containerized. In the finance industry that I work in, we do push k8s a lot, but regardless, there are still many things that simply cannot just be pushed to containers without serious re-writes. Artifactory is a lifesaver for us, especially when it comes to handling proxy servers for library repos (npm, nuget, rubygems, etc).
Post reply on HN