Skip to main content

Deployment Model

Radish supports more than one deployment and operating model.

Local / Repository-Centric Use​

At the simplest level, Radish CLI is used directly inside an application repository.

In this model:

  • blueprints live in the repo
  • generated architecture lives in the repo
  • developers work locally
  • standard Git workflows apply

Hub-Orchestrated Use​

Radish Hub can manage applications and blueprints at a higher level.

In this model, Hub provides:

  • blueprint organization
  • app-level orchestration
  • generation history
  • deployment coordination

Cloud-Managed Use​

Radish Cloud adds a hosted management layer on top of hubs and environments.

A team may use:

  • a single hosted hub
  • multiple hubs
  • self-hosted hubs registered to cloud management
  • separate hubs for staging and production
  • one hub with multiple app environments

Portability​

A core requirement of the platform is portability.

Teams should be able to:

  • take the repository
  • keep the blueprints
  • keep the generated architecture
  • continue using Radish CLI
  • or take full ownership without the rest of the platform