Skip to main content

Hybrid


Overview

A central JFrog Platform site, SaaS or self-managed, with optional extra sites for remote teams, scale, or a second copy of the data.

Why

  • Some digital assets must stay self-managed and still be shared with other teams, customers, or vendors
  • An on-premises copy and an off-premises copy support compliance, business continuity, or disaster recovery
  • One hosting model is not enough for every site

How

  • Run the central site as JFrog SaaS or as a self-managed site
  • Optionally add Artifactory Edge sites, SaaS or self-managed, for distributed teams or remote locations
  • Optionally add more JFrog Platform sites for scale, redundancy, or region
  • Distribute with release bundles, or let edges proxy and cache with Smart Remote repositories
  • When a self-managed site is unreachable from JFrog SaaS, use JFrog Bridge for Distribution, Federation, and related workflows

Architecture

There are many combinations of JFrog SaaS and self-managed sites. A few examples are:

  • SaaS as the main site
    • Self-managed edges (with JFrog Distribution and/or Smart Repositories)
    • Self-managed CI sites with repository federation of only relevant repositories. It can be used as a CI/CD Separation topology
  • Self-managed as the main site
    • SaaS as the CD site with repository federation of only relevant repositories. It can be used as a CI/CD Separation topology
    • SaaS site as data backup (with replication or federation)

The following is a schematic high-level architecture of this topology.

Hybrid Hybrid