Overview
Trusted by millions of developers, engineers, architects, and security professionals at thousands of enterprises, including the majority of the Fortune 100, the cloud-native JFrog Software Supply Chain Platform is the single source of truth for all software packages, data, and ML models utilized and generated in the development process.
The JFrog Platform on AWS manages all software inputs and outputs, providing organizations with complete visibility across their supply chain. This flexible, massively scalable, and hybrid platform helps improve developer efficiency by reducing wait times from builds to security scans. It allows organizations to take to the clouds with agility, leveraging both managed and self-managed instances. Critically, it enables teams to manage application risk end-to-end by applying evidence-based policies across the SDLC. Finally, the JFrog Platform helps accelerate AI/ML pipelines by treating models like a package, simplifying AI development and ensuring the success of initiatives.
Contact JFrog at cloud@jfrog.com for private offers on annual subscriptions, or visit <www.jfrog.com/pricing > for more information.
The JFrog Platform is often leveraged to consolidate enterprise DevSecOps solutions for companies utilizing GitLab, Sonatype, Snyk, or Veracode, among other solutions. Key capabilities include:
- Universal artifact management with JFrog Artifactory
- Modern, holistic SCA with JFrog Xray
- Contextual analysis of vulnerabilities with JFrog Advanced Security
- Early blocking of malicious open source packages with JFrog Curation
- Application risk governance with JFrog AppTrust
- Control and govern AI/ML development with JFrog ML
- Simplify model discovery and access with JFrog AI Catalog
- AI-assisted remediation with Agentic Software Supply Chain Security
- Real-time Kubernetes security monitoring with JFrog Runtime
- Speed up secure software consumption with JFrog Distribution
- IoT device management with JFrog Connect
- Includes 24x7 Support and in-region 99.99% uptime SLA, plus an assigned support resource with regular touch points
Highlights
- 50+ natively supported package and file types, including ML models and generic repositories.
- Comprehensive, enterprise-grade security solution integrated across the entire SDLC, eliminating tool sprawl and alert fatigue. Go beyond scanning with contextual analysis and vulnerability prioritization, anti-tampering mechanisms, and signed provenance, ensuring best practices and compliance.
- Fast, secure distribution of verified, multi-repository release bundles to sync large-scale geo-distributed teams and accelerate deployments to any target: SaaS, self-managed, or connected devices.
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Buyer guide

Financing for AWS Marketplace purchases
Pricing
Vendor refund policy
Contact service@jfrog.com
Custom pricing options
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
Software as a Service (SaaS)
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.
Resources
Vendor resources
Support
Vendor support
24/7 SLA support service@jfrog.com
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.

Standard contract
Customer reviews
Efficient, Scalable Artifact Management That Streamlines the Software Delivery Lifecycle
In rapidly scaling engineering setups, where there is constant creation, deployment, and management of cloud-based applications from multiple engineering teams, having control over software packages, their dependencies, and the release pipelines has been a challenge. JFrog has been immensely useful for streamlining and improving the entire software delivery lifecycle.
The ability to manage artifacts and packages via JFrog Artifactory stands out as one of the main advantages for me.
Performance and scalability have also been strong in my experience, particularly when handling large-scale artifact storage, container registries, and high-frequency deployment pipelines.
One particular difficulty I've encountered is the necessity to understand various aspects of repository management, including permission handling, pipeline integration, and software supply chains. It becomes somewhat burdensome to onboard engineers into using the platform if there are not so many of them or their background is somewhat simple.
In terms of usability and user experience, one might say that the platform is very efficient and offers lots of opportunities but some administrative functions may come as challenging. Namely, working with multiple repositories, access controls, and distributed environments at once can require certain skills and experience.
Finally, I would mention some of the difficulties I had with some of the integrations and automation processes. While JFrog works excellently within different CI/CD ecosystems in general, it might take some effort to make the most out of advanced workflow configurations and automations.
The biggest advantage I found with JFrog is its ability to manage artifacts and packages through JFrog Artifactory. Previously, we had to manage different repositories and track dependencies manually, but now it’s way more organized. It's pricing is also balanced.
JFrog Centralized Our Artifacts and Streamlined CI/CD
Artifact management has simplified CI/CD pipelines and continuously improves security insights
What is our primary use case?
JFrog Artifactory allows you to create many repositories. Currently, I'm using Docker , so it is very easy for me to create repositories in Docker and we can push Docker artifacts to that repository and pull and use them. It's very straightforward.
Currently, we have many different repositories created in JFrog Artifactory. We use them for versions. We can create multiple repositories and store artifacts in different packages.
I haven't experienced any downtime for JFrog Artifactory because we are currently operating at a small scale with small units stored in JFrog Artifactory, not a large volume. This is why we haven't faced any issues yet.
Currently, I'm using Docker and Kubernetes for JFrog Artifactory. My Docker creates images and pushes them to JFrog Artifactory, which stores my artifacts and images. When it comes to pulling, my Helm chart retrieves those artifacts and deploys my newer version if I change anything. It's a full CI/CD process that I'm using currently.
What is most valuable?
Whenever we push artifacts to JFrog Artifactory repository, they are automatically scanned. We just need to enable that feature and it will provide vulnerability scan reports.
JFrog Artifactory provides metadata. Whenever we access the UI and open those artifacts, it gives you information about which version is present. You can also tag those versions in your script file and we can automate that dynamically to create those tags in the script.
JFrog Artifactory also provides authentication features. If we are using JFrog with an enterprise grid, we can invite users who can access the same repository. We can add those users so they can access and view the repository. We can also share repositories with others and generate authentication tokens there. It provides encrypted tokens.
What needs improvement?
For how long have I used the solution?
How are customer service and support?
Which solution did I use previously and why did I switch?
The offerings are almost the same in both JFrog Artifactory and Nexus in some aspects. I cannot define those differences precisely right now, but there are some distinctions. Vulnerability scanning is one feature where they differ, and there are some other differences as well.