Red Hat Enterprise Linux9 and later
MCgovnmapSupported
MCintelligentplusSupported
Product DocumentationPlatform & deployment supportYour stack.
Your stack.
Our support.
MCgovnmap and MCintelligentplus run on the enterprise infrastructure you already operate. Declared and supported across Red Hat Enterprise Linux 9+, Docker, Podman, Kubernetes 1.28+ and Red Hat OpenShift 4.18+.
RHEL9+ Docker Podman Kubernetes1.28+ OpenShift4.18+
Declared support
Applies to both products
- Red Hat Enterprise Linux9+
- DockerEngine on RHEL 9+
- PodmanRHEL-native runtime
- Kubernetes1.28+
- Red Hat OpenShift4.18+
Support matrixOne baseline.
One baseline.
Both products.
Every platform below is declared and supported for both MCgovnmap and MCintelligentplus. If your environment sits inside these baselines, it is covered by standard MCsoftware product support.
| Platform | Version baseline | MCgovnmap | MCintelligentplus |
|---|---|---|---|
| Host-based deployment | |||
| Red Hat Enterprise LinuxHost operating system | 9 and later | Supported | Supported |
| DockerContainer deployment | Docker Engine on RHEL 9+ | Supported | Supported |
| PodmanContainer deployment | Podman on RHEL 9+ | Supported | Supported |
| Cluster-based deployment | |||
| KubernetesSelf-managed or managed | 1.28 and later | Supported | Supported |
| Red Hat OpenShiftEnterprise Kubernetes platform | 4.18 and later | Supported | Supported |
Host-based deployment
DockerDocker Engine on RHEL 9+
MCgovnmapSupported
MCintelligentplusSupported
PodmanPodman on RHEL 9+
MCgovnmapSupported
MCintelligentplusSupported
Cluster-based deployment
Kubernetes1.28 and later
MCgovnmapSupported
MCintelligentplusSupported
Red Hat OpenShift4.18 and later
MCgovnmapSupported
MCintelligentplusSupported
Supported means the combination is covered by standard product support within the stated version baseline.
Notes. RHEL, Docker and Podman rows apply to single-host deployments. Kubernetes support covers conformant distributions that provide the prerequisites on this page. OpenShift 4.18+ is a separately listed target. Newer platform releases are assessed as part of our release cycle. Platforms not listed are outside standard support until validated with us.
Swipe horizontally to view all columns →
Running a different version or distribution? We can scope a validation for your environment.
Talk to a deployment engineerDeployment modelsFour ways to run.
Four ways to run.
One support promise.
Use the operating model your team already runs — from a compact single host to a production OpenShift cluster. Both products are supported on every model below.
Single host
Docker
Run both products as containers on a RHEL 9+ host with Docker Engine. Straightforward to operate, with a small infrastructure footprint for pilots, edge locations and compact production deployments.
- Docker Engine on RHEL 9+
- Single-node container deployment
- Good fit: pilots, edge and small footprints
Supported products MCgovnmap MCintelligentplus
Single host
Podman
Use the container runtime built into Red Hat Enterprise Linux, with no Docker daemon required. A natural choice for teams standardising on Red Hat tooling and operations.
- Podman on RHEL 9+
- Daemonless, RHEL-native runtime
- Good fit: Red Hat-standardised estates
Supported products MCgovnmap MCintelligentplus
Cluster
Kubernetes
Deploy both products to a conformant Kubernetes 1.28+ cluster using the storage, ingress and identity services your platform team already provides.
- Kubernetes 1.28 and later
- Default StorageClass and ingress required
- Good fit: scaled production platforms
Supported products MCgovnmap MCintelligentplus
Enterprise cluster
Red Hat OpenShift
Run on OpenShift 4.18+ with the policy, RBAC and multi-tenant project isolation your platform team already manages, in a dedicated namespace or project.
- Red Hat OpenShift 4.18 and later
- Dedicated namespace or project
- Good fit: regulated, multi-team platforms
Supported products MCgovnmap MCintelligentplus
Reference architectureOne stack,
One stack,
from host to product.
The same deployment architecture applies to both products, whether you run containers directly on RHEL or orchestrate them with Kubernetes or OpenShift.
Deployment topology Supported
IT governance
AI knowledgeHost-based
Docker Podman
on RHEL 9+
Cluster-based
K8s 1.28+ OpenShift 4.18+
on your cluster platform
Platform services you provide
- Persistent storage
- Ingress & TLS
- DNS
- SSO (optional)
In scope for this baseline
- Both products
- On-premises
- Private cloud
- Air-gapped (MCintelligentplus)
IT governanceGovernance data, where it belongs.
A knowledge-graph platform that centralises controls and policy management across multi-vendor IT estates.
- Dedicated namespace or project
- Persistent storage for governance data
- Multi-tenant isolation
AI knowledgeAI knowledge, inside your perimeter.
Cited answers from your own documents, with local models, local indexes and no data leaving your network.
- Fully on-premises or private cloud
- Designed for air-gapped networks
- SSO via ADFS, SAML or OIDC
Deploy prerequisitesWhat to have ready
What to have ready
before you deploy.
A short checklist for a smooth rollout. Final sizing, topology and access model are agreed with your MCsoftware deployment engineer.
On your side
Platform prerequisites
- Supported host or clusterRHEL 9+ for host-based deployments; Kubernetes 1.28+ or OpenShift 4.18+ for cluster-based.
- Container runtimeDocker Engine or Podman on RHEL 9+ host targets.
- Persistent storageLocal volumes for single-host; a default StorageClass for Kubernetes and OpenShift.
- Network accessDNS, TLS certificates and, for clusters, ingress or a load balancer.
- Registry accessPull access to MCsoftware images, or an internal registry mirror for restricted networks.
- Installation accessRoot or sudo on hosts; a scoped namespace or cluster role on Kubernetes and OpenShift.
- Identity provider (optional)IdP metadata if SSO via ADFS, SAML or OIDC is in scope.
On our side
MCsoftware delivery
- Architecture and sizingA deployment design matched to your platform, data volume and availability targets.
- Release artifactsContainer images and deployment guidance for your supported platform baseline.
- Operational guidanceInstallation and upgrade guidance for the declared deployment topology.
- Validation during rolloutDeployment engineering support through your validation window and go-live.
- Air-gapped planningDelivery planning for restricted networks and MCintelligentplus air-gap deployments.
- Engineering accessA direct line to MCsoftware deployment engineering throughout the rollout.
- Support handoverA documented route to product support and escalation, as defined in your agreement.
Support policyWhat “supported”
What “supported”
means here.
A clear platform baseline protects your deployment as much as ours. These are the rules that apply to both MCgovnmap and MCintelligentplus.
01
A declared baseline
Both products share the same supported baseline on this page. Platform combinations outside it are not implicitly covered.
02
Clear ownership
MCsoftware supports the applications, deployment topology and configuration within the baseline. Red Hat, Docker and your Kubernetes vendor support the underlying platform.
03
Kept current
New releases of RHEL, Docker, Podman, Kubernetes and OpenShift are assessed against the declared baseline as part of our release cycle.
04
Outside the baseline
Older or unlisted platform versions require a scoped validation engagement before production use. Standard product support does not extend to them by default.
FAQQuestions,
Questions,
answered.
The practical details platform teams ask us before a deployment. If your question isn’t here, our deployment engineers can help.
Ask a deployment questionIs Red Hat Enterprise Linux 8 supported?
No. The current baseline starts at RHEL 9. If you're planning a RHEL 8 environment, contact us before deployment and we can scope a validation engagement.
Can we use Podman without Docker?
Yes. Podman on RHEL 9+ is a supported deployment path in its own right. No Docker daemon is required.
Which Kubernetes distributions are in scope?
Any conformant Kubernetes 1.28+ distribution that meets the prerequisites on this page is within the declared baseline, including managed Kubernetes services. Red Hat OpenShift 4.18+ is supported as a separately listed target.
Can both products run on the same cluster?
Both products are supported on the same Kubernetes or OpenShift baseline. We plan namespaces, resource allocation and combined sizing during deployment design, based on your isolation and capacity requirements.
Can MCintelligentplus run fully air-gapped?
Yes. MCintelligentplus is designed for air-gapped networks, with locally hosted models and indexes. Image and artifact delivery through your internal registry is planned with our deployment team. For MCgovnmap in restricted networks, contact us to plan delivery and validation.
Are Windows hosts supported?
No. Windows hosts are not part of the current baseline. Both products are supported on the Linux, Kubernetes and OpenShift platforms listed above.
Next step
Let’s validate your environment.
Send us your OS, container runtime and cluster version. Our deployment engineers will confirm support, share sizing guidance and map the fastest path to production.
MCgovnmap MCintelligentplus RHEL 9+ Docker Podman Kubernetes 1.28+ OpenShift 4.18+
Red Hat, Red Hat Enterprise Linux, and OpenShift are trademarks or registered trademarks of Red Hat, Inc. Docker is a trademark of Docker, Inc. Kubernetes is a registered trademark of The Linux Foundation. All other marks are the property of their respective owners.