Appliance, console and portal

Aicerine runs as a proprietary, self-contained appliance on your infrastructure. Everything in the decision path runs there, and it works air-gapped.

What runs where

Part	Where	What it does
Appliance	A VM or a Kubernetes namespace on your side	Reads Nova and Placement, receives telemetry, plans, and, at the autonomy level you set, writes ratios and starts live migrations
Host agent	Each compute host	Measures usage and pushes it to the appliance; read-only and outbound-only
Console	Served by the appliance	Your operators' view of one installation: hosts, plans, decisions, control, audit
Portal	`aicerine.com/portal`	Your organisation's account with Aicerine: installations, licences, downloads, support

Nothing is pulled from the internet. In an air-gapped install, images, packages and the console arrive in a signed bundle, through your own software intake process.

What it needs on your network

Outbound to the internal APIs of Nova, Placement and Keystone, and to RabbitMQ if you enable notifications.
Inbound from your compute hosts (telemetry) and from your operators (console).
Nothing to the internet.

The console runs on the appliance and depends on nothing outside it. Operators sign in through your identity provider (OIDC); a group-to-role table in the appliance maps your groups to viewer, operator, admin or auditor. Every move is shown with its calculation line.

The portal

The portal at aicerine.com/portal is a separate surface with its own sign-in. It covers your organisation, not one cloud: installations, licences, downloads and support tickets.

The portal has no command path to an appliance. It can never migrate a VM, change a ratio or stop Aicerine; those actions exist only in the console.

Operator control

The autonomy level, the guardrails and the emergency stop are set in the console. See Autonomy and control.

The exact prerequisites and the deployment procedure are part of the technical documentation shared with pilot partners.