System Architecture
JPD microservices architecture: each product runs with local services and a Router for API gateway and inter-service discovery.
A JFrog Platform Deployment (JPD) is the unit of deployment for all JFrog self-managed products. In JFrog Cloud (SaaS) offerings, JFrog manages platform deployment on your behalf. The JPD concept applies to deployments you install and operate. Each JPD contains one or more JFrog products — such as JFrog Artifactory, JFrog Xray, and JFrog Distribution. Every node within a JPD runs the product's internal services alongside a local Router, which acts as the API gateway and service discovery component for all inter-service communication.
The Enterprise+ Platform includes Artifactory, Xray, Distribution, Mission Control, JAS, Workers, Catalog, Bridge Client, Federation Service, Edge nodes, AI/ML, AppTrust, and MCP Server. Each product node runs its own microservices alongside a local Router. External clients (UI, REST API, CLI, CI/CD) connect through a load balancer, which routes all traffic to Artifactory's Router on port 8082. The Router on each node handles both inbound API requests and inter-service discovery within the JPD.
External Access Points
These components sit outside the JPD and provide external access:
| Component | Description |
|---|---|
| Load Balancer | Entry point to the JPD. Routes requests to Artifactory (and its Router service) and to Edge nodes. Configured by the customer. |
| Clients (UI / REST API / CLI / Terraform / CI/CD) | External clients interact with the JFrog Platform through the load balancer. |
Node Structure
A node is a single server or VM instance that runs one JFrog product's services. In a standard deployment, each product runs on exactly one node. In a high-availability (HA) deployment, a product can span multiple nodes for redundancy and load distribution.
Each node contains:
- The product's microservices
- A local Router for service discovery and API gateway functions
For more information about the services, microservices, and architecture of the JFrog Platform:
Checksum-Based Storage
Understand how Artifactory deduplicates binaries using checksums — each file is stored only once regardless of upload count.
High Availability
Configure multi-node HA deployments to maximize uptime and distribute load across the JFrog Platform.
JFrog Products Container Base Image
Specifications and OS details for the Docker base images used to deploy JFrog products and services.
System Directories
Directory structure created during installation — where configuration files, logs, and data are stored.
Artifactory Product
Architecture and microservices that make up JFrog Artifactory, including metadata, frontend, and access services.
Xray Service
Architecture and microservices powering Xray's vulnerability scanning, indexing, and compliance analysis.
Distribution Service
Architecture of the Distribution service that manages secure delivery of release bundles to edge nodes.
Router Service
The central service managing API routing, service discovery, and communication between JFrog microservices.
Self-Managed Reference Architecture (External)
Use these cross-references to learn self-managed deployment patterns and planning guidance from the JFrog Reference Architecture site.
JFrog Platform Reference Architecture
Start with the overview and goals to understand how to design enterprise self-managed deployments
Self-Managed Use Cases
Explore single-site, multi-site, hybrid, and air-gapped self-managed deployment models
Deployment Considerations
Review runtime platform, hardware sizing, network, HA, database, storage, security, and migration considerations
Disaster Recovery Guidance
Use disaster recovery tiers and playbook guidance when planning production resiliency
Related Topics
- Installing the JFrog Platform
- High Availability
- System Directories
- Checksum-Based Storage
- JFrog Router Service
- Reference Architecture
- System Requirements
Frequently Asked Questions
This section provides answers to frequently asked questions.
FAQs
Q: What is a JFrog Platform Deployment (JPD)?
A: A JPD is a self-managed deployment of the JFrog Platform that contains one or more JFrog products (Artifactory, Xray, Distribution, Mission Control, JAS, Workers, Catalog, Bridge Client, Federation Service, Edge nodes, AI/ML, AppTrust, and MCP Server — depending on your license tier). In JFrog Cloud (SaaS) offerings, JFrog manages this deployment on your behalf. Each product node within a JPD includes a local Router service that handles API routing and service discovery. Multiple JPDs can be interconnected in multi-site topologies.
Q: How do JFrog products communicate within a JPD?
A: All inter-service communication within a JPD is routed through the local Router service running on each node. External clients (UI, REST API, CLI, CI/CD tools) connect to the JPD through a load balancer, which routes requests to Artifactory's Router service on port 8082.
Q: What is the JFrog Router service?
A: The Router is a microservice that runs on every JFrog product node. It serves as the API gateway for incoming requests and as the service discovery mechanism for communication between microservices. The Router listens on port 8082 by default and is the primary entry point for all platform API calls. See JFrog Router Service for details.
Updated 22 days ago