Freedom of choice can make choosing harder. Since a JFrog cloud (SaaS) account provides the same functionality as a self-hosted JFrog Software Supply Chain Platform how will you decide which is right for you? Choice without tradeoffs is one of the key ways JFrog enables you to be cloud-nimble, and run the mission-critical heart of your DevSecOps process wherever you need it to be — in any cloud, public or private, as SaaS, BYOL, or on-prem. So how will you decide?

To recap from our first blog post, JFrog Workers is a service in the JFrog Platform that provides a serverless execution environment, similar to AWS Lambda services. The Workers Service is similar to the user plugins available in JFrog self-hosted, and can be used to perform tasks that extend the capabilities of the JFrog Platform according to your requirements.

If you’re building apps to run on Kubernetes, chances are you’re using Helm. If you fall into that category, we have good news for you: Helm users will now benefit from JFrog Artifactory’s support of Helm OCI registries in JFrog Artifactory.

Great news for developers who leverage containers — JFrog has expanded its support for the OCI Container standard with dedicated OCI repositories! Before we touch on that, let’s do a quick recap on OCI containers for those unfamiliar with them outside the context of Docker.

To no one’s surprise, cloud adoption continues to be a focus for organizations of all sizes and verticals. However, for those who are used to the flexibility and adaptability that comes with customizing self-hosted software, moving to a SaaS offering and losing some of that customization can be a deal breaker. At JFrog, giving developers the freedom – and flexibility – to work however they want to has always been a central tenet to our offering.

Software development begins with code, which is then integrated, compiled, tested, and in the end distributed to users. This is often the secret sauce of innovation that organizations must protect to keep their competitive edge. With the software application development market growing at almost 30% per year and the average project taking just 4-6 months to complete – and trending downwards – the result is more software to develop and constant pressure to release it as fast as possible.

JFrog Artifactory is a “binary artifact repository with a name that is so well known that it is synonymous with artifact repositories in general.” But why is Artifactory the solution chosen by most Fortune 100 companies and millions of developers for their artifact and binary management?

With five keynotes and 15 breakout sessions in one day, there was no shortage of important industry knowledge and key insights from this year’s JFrog swampUP DevOps and DevSecOps user conference. Presenters discussed the role of DevOps at Netflix, how Fidelity migrated to the Cloud, the trend of shifting further left than left, and more. In this post we highlight the three presentations below that challenged attendees to rethink the status quo and reassess their own DevOps and security practices.

JFrog’s IDE integrations such as IntelliJ and VS Code, allow developers to work with the JFrog Platform right from within their existing dev environment. By leveraging the advantages of JFrog’s features, developers can develop, build, and deploy applications quickly and securely. Large organizations working with the JFrog Platform, can now easily use a SSO (single-sign-on) login to authenticate access, directly from within IntelliJ IDEA and VS Code.

Since inception in 2008, JFrog has hosted its own development environments on-prem. While this approach worked well for a time, the increasing need to deploy faster, while sustaining high quality and reducing hosting costs made us realize that we needed to leverage the JFrog SaaS Production environment. So in 2022, we started an effort to migrate our RnD environments from an on-prem solution to JFrog SaaS Production.