# Deployment

---

## Overview

The JFrog Platform can be deployed in various environments, with Kubernetes being the recommended deployment method. Our official [JFrog Platform Helm chart](https://github.com/jfrog/charts/tree/master/stable/jfrog-platform) provides a production-grade, easy-to-maintain deployment solution.

## Kubernetes Deployment

The JFrog Platform Helm chart offers:
* Unified deployment of all platform components
* Built-in high availability configuration
* Automated upgrades
* Integration with cloud-native storage and databases
* Predefined sizing templates for different scale requirements

## Deployment Considerations
Before you deploy the JFrog Platform, it is important to be aware of several critical considerations, including platform compatibility, sizing, networking, storage, security, and migration strategies. 

##### [Deployment Considerations →](considerations/)

## Deployment Options

The JFrog Platform can be deployed in several environments, including:

##### [Amazon Web Services (AWS) →](aws)
* Amazon Elastic Kubernetes Service (EKS)
* Integration with AWS services (S3, RDS, etc.)
* Regional and multi-region deployments

##### [Microsoft Azure →](azure)
* Azure Kubernetes Service (AKS)
* Integration with Azure services (Blob Storage, Database, etc.)
* Support for Azure Government Cloud

##### [Google Cloud Platform (GCP) →](gcp)
* Google Kubernetes Engine (GKE)
* Integration with GCP services (Cloud Storage, Cloud SQL, etc.)
* Support for private GKE clusters

##### [Private Data Center →](private-datacenter)
* On-premises Kubernetes clusters
* Bare metal installations
* VMware infrastructure

## Common Requirements

Regardless of the deployment environment, consider these key aspects:
* High availability configuration
* External database (PostgreSQL)
* Scalable object storage
* Network security and access control
* Monitoring and logging setup
* Disaster recovery and backup strategies

Each deployment option is detailed in the sections on the left navigation menu with specific configurations and best practices.