SUSE Multi-Linux Manager 5.2

Open-source Linux infrastructure management and automation platform deployed as a customer-operated container or cloud virtual machine.

6 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    SUSE Multi-Linux Manager 5.2 container with mgradm on SL Micro 6.2 or SLES 15 SP7, or a SUSE-provided cloud VM image

  2. Operated by

    Your team

    Customer manages the cloud VM, private networking, DNS, storage, server and proxy containers, repository synchronization, backups, upgrades and registered systems.

Deployment boundaries by provider

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodSUSE Multi-Linux Manager 5.2 container with mgradm on SL Micro 6.2 or SLES 15 SP7, or a SUSE-provided cloud VM image
InfrastructureServers / containers
The supported 5.2 deployment runs persistent server and proxy containers on customer virtual machines with large durable repository and database volumes.
Licensing modelOpen Source / Open Core
SUSE describes Multi-Linux Manager as an open-source infrastructure-management solution based on Uyuni and publishes corresponding GPL source. SUSE-provided images, updates, support, host entitlements and trademarks remain governed by the selected subscription and commercial terms.
LicenseOpen-source product based on Uyuni with component open-source licenses; SUSE subscriptions, support, images and trademarks use separate commercial terms.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

12 of 12 fields researched (100%) · 7 documented · 5 unresolved. Evidence coverage is not a feature score.

Marketplace delivery
Edition-dependentEvidence and scope for Marketplace delivery

The public-cloud guide documents AWS BYOS/PAYG and Azure BYOS routes. Google Cloud is tested but a corresponding Marketplace offer is not established by the guide; proxies are BYOS only.

Product-specific public-cloud delivery variants · Source ↗ · Reviewed 2026-11-17

Edition-dependent · Editor reviewed.

Cloud commitment eligibility
Not confirmedEvidence and scope for Cloud commitment eligibility

AWS PAYG and BYOS variants have different entitlement/billing terms. The public-cloud guide does not establish qualifying charges under a buyer commitment agreement.

Reviewed public evidence for SUSE Multi-Linux Manager 5.2; unresolved within this edition/deployment · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Single sign-on
AvailableEvidence and scope for Single sign-on

Multi-Linux Manager supports SAML 2 SSO with signed/encrypted assertions and SP metadata. The corresponding Manager user must exist before enabling SSO; selecting an IdP and its support remain customer responsibilities.

SUSE Multi-Linux Manager 5.2 server authentication · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

SCIM provisioning
Not confirmedEvidence and scope for SCIM provisioning

The SAML guide requires the Manager user to exist before enabling SSO. It does not establish a SCIM endpoint or automatic lifecycle provisioning.

Reviewed public evidence for SUSE Multi-Linux Manager 5.2; unresolved within this edition/deployment · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Compliance attestations
Not confirmedEvidence and scope for Compliance attestations

The reviewed SUSE Multi-Linux Manager 5.2 material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage.

Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Security controls
DocumentedEvidence and scope for Security controls

The SSO workflow requires mapping the IdP uid to an existing Manager user and protecting signing/encryption material. SSO does not automatically provision accounts or grant other SUSE products the same identity support.

Manager identity trust; not SCIM or a certification · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

Air-gapped operation
Not confirmedEvidence and scope for Air-gapped operation

The reviewed 5.2 administration PDF identifies itself as Beta 1 and describes disconnected repository synchronization. It does not settle the supported GA installation, subscription renewal, container updates and client-content transfer workflow.

Reviewed public evidence for SUSE Multi-Linux Manager 5.2; unresolved within this edition/deployment · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The 5.2 server workflow deploys containers using mgradm on the supported host OS, with persistent volumes and separately prepared repository/database storage. Select the matching BYOS/PAYG cloud image and entitlements.

Multi-Linux Manager container deployment · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

Size the server and proxy for managed clients and mirrored repositories, not human users. PostgreSQL must be local; remote PostgreSQL and NFS database storage are unsupported. Separate persistent repository/database devices and supported filesystems are recommended.

5.2 storage and database requirements; not an approved active-active HA design · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

SUSE describes Multi-Linux Manager as an open-source infrastructure-management solution based on Uyuni and publishes corresponding GPL source. SUSE-provided images, updates, support, host entitlements and trademarks remain governed by the selected subscription and commercial terms.

SUSE Multi-Linux Manager 5.2: software entitlement and edition boundary; infrastructure and operating costs are separate · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

Operating cost estimate
Not confirmedEvidence and scope for Operating cost estimate

Specify managed clients, OS repositories/proxies, subscription units and a supported HA/recovery design. The guide requires local PostgreSQL, so substituting RDS Multi-AZ is not established. A complete monthly operating estimate is not established.

Requested planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA, average usage; missing workload metrics and commercial terms are explicit · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

The reviewed 5.2 Server notes include 5.2.1 updates, PostgreSQL 18, platform changes and security fixes. Kubernetes deployment remains a Technology Preview; the notes document host/feature support separately from container and proxy versions.

5.2 Server release notes; document revision time is not a software release timestamp · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

Scope & considerations

SUSE documents public-cloud installation tested on Amazon EC2, Google Compute Engine and Microsoft Azure. Keep the server on a restricted private network with working forward-confirmed reverse DNS and external persistent disks for repositories and database data. AWS supports PAYG and BYOS; Azure supports BYOS, while the public guide's GCP path is a tested customer-operated installation rather than a confirmed marketplace billing offer. Public-cloud proxies are BYOS-only.

Category fit

DevOps
Automates Linux provisioning, patching, configuration, monitoring, inventory and compliance operations across managed systems.

Compare within DevOps

  • Argo CDGitOps continuous delivery controller and interface for deploying and reconciling applications in Kubernetes clusters.
    • AWS
    Customer-operated · Open Source / Open Core
  • Azure DevOps ServerSource control, CI/CD, work tracking, testing and package management installed on Azure virtual machines you operate.
    • Azure
    Customer-operated · Commercial Only
  • Bitbucket Data CenterCommercial self-managed Git collaboration and code-review platform for eligible existing Atlassian customers, with an announced Hybrid License transition.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • CircleCI ServerCommercial self-hosted CI/CD platform installed in a customer-operated Amazon EKS or Google GKE cluster.
    • AWS
    • Google Cloud
    Customer-operated · Commercial Only
  • CloudBees CI on Modern Cloud PlatformsEnterprise continuous-integration platform installed with Helm in a Kubernetes cluster you operate.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • GitHub Enterprise ServerCustomer-operated GitHub software-development platform deployed as a licensed virtual appliance.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • GitLab Self-ManagedSource control and CI/CD on infrastructure you operate.
    • AWS
    • Azure
    • Google Cloud
    • Oracle Cloud
    • Alibaba Cloud
    Customer-operated · Open Source / Open Core
  • HarborContainer and OCI artifact registry for managing software images within customer-operated infrastructure.
    • Railway
    Customer-operated · Open Source / Open Core

Showing 8 of 27 other listings in DevOps. These products address related workflows; read their category-fit notes before comparing scope. See all of DevOps →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • SUSE Multi-Linux Manager public-cloud installation on EC2, Azure and GCE ↗ · AWS, Azure, Google Cloud

      Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.

      SUSE states that its public-cloud requirements and procedures were tested on Amazon EC2, Microsoft Azure and Google Compute Engine. The customer operates the instance, DNS, private networking and durable storage; billing and image availability differ by provider.

    • SUSE Multi-Linux Manager BYOS and PAYG public-cloud models ↗ · AWS, Azure

      Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.

      The public-cloud guide documents BYOS on AWS and Azure and PAYG on AWS. This evidence qualifies procurement models; it does not extend PAYG availability to Azure or Google Cloud.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory