IDP control plane

Platform building blocks, without infrastructure lock-in.

Give teams a curated platform while keeping provider implementation, configuration, and credentials behind explicit boundaries.

Customer journey

A clear route from project to deployment.

  1. Create a project.
    Capture ownership and desired lifecycle.
  2. Select a provider.
    Incus is supported first; adapters isolate what comes next.
  3. Configure infrastructure.
    Define network, storage, image, CPU, memory, disk, and NIC.
  4. Select platform components.
    Choose versioned catalog entries such as Nexus, GitLab, and Grafana.
  5. Validate and deploy.
    Generate a secret-free contract and submit it to GitLab.

Architecture

Control plane, provider modules, and configuration stay decoupled.

CONTROL

Desired state

Accounts, projects, catalog revisions, validation, and deployment history.

PROVISION

Terraform modules

Provider-specific infrastructure behind stable module inputs.

CONFIGURE

Ansible collection

Provider-neutral roles addressed by fully qualified collection names.