Skip to content

Concepts

Understanding how Appsuites works will help you get the most out of the platform.

An Appsuite is a logical grouping of related applications that form a complete product. For example, a typical Appsuite might contain:

  • A Payload CMS (Backend/Content Management)
  • An Astro Website (Frontend/Public Facing)

These applications share:

  • A single Git repository (Monorepo).
  • Shared configuration and secrets.
  • A unified deployment lifecycle.

Each component within an Appsuite is an Application.

  • Type: Defines the technology stack (e.g., payload, nextjs, astro).
  • Services: Each app exposes one or more services (e.g., HTTP endpoints).

The Appsuite platform uses a declarative deployment model. Instead of scripting individual steps, you define a Target State (e.g., PRODUCT_DEPLOYED). The Planner Engine then calculates the necessary actions to transition your Appsuite from its current state to the target state.

This ensures reliability and consistency across deployments. When you click “Deploy All”, the system automatically:

  1. Builds new container images.
  2. Pushes them to the registry.
  3. Updates the Kubernetes deployment manifests.
  4. Waits for the pods to become healthy.