Hybrid

Hybrid: JFrog SaaS with Self Hosted

  • A central JFrog Platform site, which can be deployed as either a fully managed JFrog SaaS service or as a self-hosted instance
  • Optionally, one or more JFrog Artifactory Edge sites (either SaaS or self-hosted) to support distributed teams or remote locations
  • Optionally, additional JFrog Platform sites (SaaS or self-hosted) for further scalability, redundancy, or regional requirements
  • Artifacts can be distributed from the main site to edge sites using release bundles, or accessed via Smart Remote repositories that allow edge sites to proxy and cache content from the main site
  • Common use cases include:
    • Needing to self-host digital assets while still sharing or distributing them with other organizational teams, customers, or vendors
    • Requiring on-premises storage of digital assets, but also maintaining an off-premises copy for compliance, business continuity, or disaster recovery purposes

JFrog Bridge

Typically, self-hosted sites are not accessible from JFrog SaaS due to network restrictions or firewall configurations. To enable secure, bi-directional connectivity for features like Distribution and Federation between SaaS and self-hosted sites, JFrog Bridge can be used.

Architecture

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

  • SaaS as the main site
    • Self-hosted edges (with JFrog Distribution and/or Smart Repositories)
    • Self-hosted CI instances with federation of only relevant repositories. It can be used as a CI - CD separation topology
  • Self-hosted as the main site
    • SaaS as the CD site with 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 such a topology

Hybrid Hybrid