The Red Hat Ecosystem Catalog is the official source for discovering and learning more about the Red Hat Ecosystem of both Red Hat and certified third-party products and services.
We’re the world’s leading provider of enterprise open source solutions—including Linux, cloud, container, and Kubernetes. We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.
The ARNIE AI UI is the web interface for the ARNIE AI operator. Type what you want in plain language and watch ARNIE generate the Ansible playbooks, pull Helm charts, and stand up applications and operators — reviewing and approving each change before it runs on your cluster. It's the front end that pairs with the ARNIE AI backend to turn requests into real infrastructure across GitHub, Ansible Automation Platform, and OpenShift. A BLCKBX product.
The following information was extracted from the dockerfile and other sources.
| Canonical image ID | arnie-ai-ui |
| Summary | ARNIE AI — web interface |
| Description | Nginx is a web server and a reverse proxy server for HTTP, SMTP, POP3 and IMAP protocols, with a strong focus on high concurrency, performance and low memory usage. The container image provides a containerized packaging of the nginx 1.24 daemon. The image can be used as a base image for other applications based on nginx 1.24 web server. Nginx server image can be extended using source-to-image tool. |
| Provider | Brandon Jumper |
| Maintainer | BLCKBX |
| Repository name | arnie-ai-ui |
| Image version | 1.0.0 |
| Architecture | amd64 |
| Usage | s2i build <SOURCE-REPOSITORY> ubi9/nginx-124:latest <APP-NAME> |
| Exposed ports | 8443:https |
The following evidence verifies the image's security and build process compliance with mandated internal standards.
| Security audit date | 7/4/2026, 12:52:47 AM |
| Container certification |
Pull the ARNIE AI UI image using the command shown above. The UI is the web front end for ARNIE and runs alongside the ARNIE AI backend component, which serves the API. Deploy both together, then use the interface to describe infrastructure tasks in plain language, review the generated automation, and approve changes to run on your cluster.