Skip to main content

Architecture

Radish is a layered platform. Different parts of the system operate at different levels of abstraction.

Layered Model​

Intent Layer
  ↓
Blueprint Layer
  ↓
Architecture Generation Layer
  ↓
Application Layer
  ↓
Infrastructure / Operations Layer

Intent Layer​

The process begins with an application idea or business need.

Examples:

  • "A workflow tool for approving invoices"
  • "An application for managing shipping statuses and approval timelines"
  • "A blueprint library for storing prompt-to-architecture examples"

Blueprint Layer​

The blueprint is the formal representation of application intent.

A blueprint can describe:

  • entities
  • fields
  • relationships
  • ownership
  • roles and permissions
  • metadata
  • routes, pages, layouts, and components (via ui.json)
  • infrastructure intent and deployment config

Blueprints are the primary source of truth for generation.

Architecture Generation Layer​

Radish CLI compiles blueprints into generated architecture.

Radish CLI compiles blueprints into multiple generated layers. Because blueprints describe application structure — not implementation — the same blueprint can target different technology stacks. A --stack flag selects the target; the default is Node/SvelteKit/MongoDB, with Laravel/PHP in production and Python in development.

  • Datalayer — contracts, validation, repositories, services, metadata APIs, access control, documentation, manifests (Zod + Mongoose for Node; Form Requests + Eloquent for Laravel)
  • Admin panel — entity CRUD pages, user/role management, settings, login/logout
  • UI layer — pages, layouts, and components from ui.json blueprints
  • Skeleton — SvelteKit app structure with route groups, SEO, setup wizard
  • Theme layer — DaisyUI theme configuration from blueprint
  • Deployment artifacts — Dockerfile, docker-compose, CI config
  • AI agents, skills & slash commands — Claude Code context for AI-assisted development

For a detailed breakdown of generated architecture, see the Architecture Reference.

Application Layer​

Developers and AI assistants build application behavior on top of the generated architecture.

This includes:

  • UI code
  • workflows
  • integrations
  • custom pages
  • custom route behavior
  • business-specific orchestration

Infrastructure / Operations Layer​

Radish Hub and Radish Cloud operate above the generated application layer.

They manage concerns such as:

  • blueprint lifecycle
  • application orchestration
  • deployment coordination
  • version management
  • environment organization
  • hosted management