Skip to content

Features

Superphenix is organized in two layers: the foundation provides the infrastructure platform (IaaS and operations), and managed services consume it to deliver higher-level offerings. The web console exposes these capabilities as products (compute, storage, network, SSH keys, and more), scoped by organization, project, and availability zone (AZ).

Read Tenancy and console first for organizations, projects, IAM, and how to navigate resources.

Foundation

The foundation provides the core capabilities that the rest of the platform relies on.

  • Virtualization

    Instances (VMs), live migration, snapshots (VM and scheduled volume), restores, cloud-init, SSH, serial, and VNC.

    Virtualization

  • Network

    VPCs, subnets, NAT gateways, load balancers, Elastic IPs (EIPs), and firewalls: CSP-style networking with IPAM and optional Internet exposure.

    Network

  • Storage

    Disks and disk snapshots: block volumes (and classes such as high-speed), create from blank, HTTP image, snapshot, or clone; online resize.

    Storage

  • Tooling

    GitOps, web console, SSH key store, observability, and quotas—deploy and operate the platform and tenant resources from one place.

    Tooling

Managed services

These services run on the foundation. Availability depends on your Superphenix version and configuration.

  • PaaS

    Kubernetes (KaaS) — VM node pools, integrated CNI/CSI, upgrades, and the same VPCs and storage as IaaS. Console availability varies by release.

    PaaS

  • SaaS

    Managed applications (databases, registries, Git, file sync, …) — the service catalog is evolving; see the SaaS page.

    SaaS

How they fit together

  • Tenancy — Organizations and projects isolate resources and access; see Tenancy and console.
  • Foundation — Virtualization runs VMs; the network layer provides VPCs and subnets; storage backs disks; tooling drives GitOps and the console.
  • Managed services — When enabled, PaaS and SaaS consume the same virtualization, storage, and network primitives.

See Architecture overview for AZs, regions, and central administration.