JFrog Artifactory is JFrog Ltd's universal software artifact repository, used as the single registry for Maven, npm, Docker, PyPI, NuGet, Go, Helm, Debian, RPM and Terraform packages, container images and machine learning models, with native support for over 50 package types. It comes in two deployment models with distinct licensing: managed by JFrog and charged by consumption, or installed on the customer's own infrastructure and charged per server.
JFrog Artifactory is JFrog Ltd's universal software artifact repository, used as the single registry for everything engineering produces and consumes: Maven, npm, Docker, PyPI, NuGet, Go, Helm, Conan, Debian, RPM and Terraform packages, container images, Helm charts and machine learning models, with native support for over 50 package and file types, according to JFrog.
It solves two problems at once. The first is organizational: without a central point, each team adopts a tool per language and nobody can say which binary reached production or where it came . The second is external dependency: Artifactory proxies public registries, caching packages locally, which prevents build failures when the source goes down and creates the single point where curation and vulnerability analysis become applicable.
This page is the product overview. Artifactory is sold in two deployment models with different licensing metrics, and each has its own page covering editions, requirements and counting rules: JFrog Artifactory Cloud, managed by JFrog, and JFrog Artifactory Self-Hosted, installed on the customer's infrastructure.
Predictable builds because external dependencies stay cached: if the public registry goes down, the build resolves the local copy instead of failing.
Storage kept in check by checksum-based storage, which eliminates duplicate copies of the same binary across different repositories.
Governance written once because a single service covers every ecosystem — access policy and auditing stop being replicated in one tool per language.
A path open to supply chain security because vulnerability analysis and package curation happen inside the repository itself, with no need to export artifacts to an external tool.
Artifactory serves platform, DevOps and release engineering teams that own the build chain and the CI/CD environment, plus IT leaders who need to consolidate scattered registries and answer for release traceability.
In practice, the recurring trigger is the organization that grew with one registry per language — one for npm, another for Maven, another for Docker — and reached the point where auditing what runs in production means checking three or four systems with independent access policies.
The choice between the two models defines the licensing metric and therefore precedes any quote.
The managed model makes sense when the priority is reducing infrastructure operations: JFrog takes on patching, scaling and high availability, and the customer picks provider and region — there are two São Paulo regions, one on AWS and one on Azure. It is the usual path for a new purchase.
The self-managed model makes sense when the requirement is control: local retention policy, a network with no internet egress, or ownership of the database, filestore and upgrade window. It is also the model supporting air-gapped operation.
The two topologies coexist: the enterprise editions upwards, a managed instance connects to on-premise installations in the same logical environment, with artifact synchronization across sites.
In the managed model, access is through a browser and the command line, with no server requirement on the customer side, running across roughly 30 locations spread over AWS, Microsoft Azure and Google Cloud. In the self-managed model, Artifactory runs on RHEL 8 and 9, Ubuntu 22.04 and 24.04, Debian 11 and 12 and Windows Server 2022, installed via Helm, Docker, Docker Compose, RPM, Debian package, Linux Archive or Ansible, over PostgreSQL 13 to 17, Oracle, MySQL 8, Microsoft SQL Server or MariaDB. JFrog states a minimum of 8 GB RAM in production.
Named integrations cover Jenkins, GitHub Actions, GitLab, Azure DevOps, Kubernetes and Helm. JFrog CLI and the IDE plugins run on Windows, Linux and macOS.
Editions vary by deployment model. In self-managed, OSB Software supplies Pro X, Enterprise X and Enterprise +; in managed, Enterprise X and Enterprise +, all on annual contracts.
What changes between them is the number of servers or included consumption base, high availability, Artifact Federation, Access Federation, edge nodes, project count and support level. The full matrix sits on each model's page. JFrog also offers free non-commercial licenses, such as JFrog Container Registry and Artifactory OSS, which include neither integrated security nor support and fall outside corporate supply.
It depends on the deployment model, because the two licensing metrics are different — and that is the first question in any sizing exercise:
In both cases the model is an annual subscription, with a multi-year option on the enterprise editions, and the investment depends on sizing: chosen model, edition, contracted volume, additional security and governance modules, term and whether it is a new purchase or a renewal. To buy JFrog Artifactory in Brazil, OSB Software maps that scope with you, sends the commercial proposal, issues the Brazilian invoice and delivers the licenses — request a quote to get the exact figure for your scenario.
What is the difference between Artifactory Cloud and Self-Hosted? Cloud is operated by JFrog on AWS, Azure or Google Cloud and charged by consumption; Self-Hosted is installed on the customer's infrastructure and charged per server. The choice changes the metric, the requirements and the quoting process.
Which package formats does Artifactory support? Over 50 natively, among them Maven, npm, Docker, OCI, PyPI, NuGet, Go, Helm, Conan, Debian, RPM and Terraform, plus machine learning models.
Do I need Artifactory to use JFrog Xray? Yes. Xray analyzes artifacts stored in Artifactory, and the same applies to JFrog Curation, JFrog ML and JFrog Connect — all operate on the platform and none is sold standalone.
Does Artifactory replace the registry built into my cloud provider? It can replace or coexist. The difference is breadth: provider registries cover a slice of formats, while Artifactory unifies every ecosystem under a single access and audit policy.
OSB Software is an official JFrog Ltd partner in Brazil and supplies 100% genuine JFrog Artifactory licenses to companies, with Brazilian invoicing, local contracting in Portuguese and full legal compliance — the safe way to buy imported software under a Brazilian corporate entity, with no risk of irregular licensing.
When you buy JFrog Artifactory OSB Software, you get:
If you are looking for where to buy JFrog Artifactory in Brazil with legal certainty and properly licensed imported software, request a quote: OSB Software delivers reliable technology, qualified support and a simple, transparent purchase.
You don't know what software you need or you haven't found what you were looking for? We have a team ready to help you choose the right software for your company.