The capsule, counted alongside the parent.

Satellite capsule server licensing describes the entitlement model for the Satellite capsule, the distributed content proxy and discovery service that extends a Satellite Server across geographic sites, network segments, and air gapped enclaves. The capsule runs on RHEL, holds a synchronised copy of the content the central Satellite Server delivers, and serves that content to managed RHEL hosts at the local site. The capsule does not carry its own product SKU on the Red Hat price list; it is provisioned from the Satellite Server interface and its entitlement reading is derived rather than direct.1

Two distinct entitlements meet at the capsule host. The Smart Management entitlement covers the managed RHEL hosts that the capsule serves; that entitlement scales with the managed host count, not with the capsule count. The RHEL subscription on the capsule host itself covers the operating system the capsule runs on; the capsule host is a RHEL host in the standard counting sense and is entitled accordingly. A buyer who has named only one of these two entitlements has named half the licensing reading on the capsule. The sibling treatment of the smart management entitlement sits in the Satellite Smart Management entitlements note.

The relationship to the Satellite Server is the reading that frequently confuses procurement. The Satellite Server itself is licensed under the same Smart Management model and the underlying RHEL subscription; capsules are extensions of the Satellite Server topology that share the managed host count without re entitling those hosts. Adding a capsule to an existing Satellite topology does not add to the Smart Management entitlement requirement unless the new capsule begins to manage hosts that were previously outside the topology. The cross reading on the broader Satellite topology sits in the Satellite practice hub.

Three patterns shift the capsule reading on the audit. Each is structural to the topology rather than to the capsule product itself.

The first pattern is the high availability capsule pair. A buyer who provisions a capsule in an active passive pair for resilience runs two RHEL hosts at the site; both hosts require a RHEL subscription regardless of which is active at any given moment. The Smart Management entitlement on the managed hosts does not change; the RHEL host count does. The pattern is frequently read as one capsule rather than two RHEL hosts in the procurement register. The cross reading on the broader audit posture sits in the audit evidence subscription manager output note.2

The second pattern is the multi site federated topology. An enterprise with capsules at twenty branch sites is running twenty RHEL hosts at those branches; the Smart Management entitlement scales with the managed host count served by those capsules, not with the capsule count, but the RHEL host count rises by twenty regardless. The audit reading walks both numbers separately; the buyer who has counted only the managed hosts misses the capsule RHEL count. Every capsule is a RHEL host before it is a capsule. The sibling treatment of distributed estate counting sits in the RHEL image builder and image mode licensing note, where the same host class question recurs for edge image management.

The third pattern is the content delivery at the air gapped edge. An enclave that cannot reach the central Satellite Server requires a capsule synchronised on a periodic schedule from a connected donor host; the capsule then serves the enclave's RHEL hosts directly. The audit reading on the enclave turns on whether the managed host count inside the enclave has been added to the Smart Management entitlement on the parent estate; capsules in air gapped enclaves are the most frequent source of unreported managed host counts in distributed Satellite topologies. The cross cluster bridge sits in the defense and DoD Red Hat audit process note, which carries the equivalent reading for classified network enclaves.

The audit reading on a capsule estate walks four artifacts. The Satellite Server inventory of capsules and their managed host attachments, the RHEL subscription manager record for each capsule host, the Smart Management entitlement attached to the managed hosts, and the network topology that names which hosts each capsule actually serves. The reading is internally consistent when every capsule host carries its own RHEL entitlement, every managed host carries the Smart Management entitlement, and the managed host counts roll up correctly across the federated topology.3

The most common audit reading misstep on a capsule estate is the capsule host counted as zero. A procurement register that lists Satellite topology in terms of managed host count alone has not seen the capsule RHEL hosts; the audit walks the host inventory and finds them. The remediation is the inclusion of the capsule host class in the Satellite topology line of the procurement register, with an explicit count of capsule RHEL hosts separate from the managed host count.

The second misstep is the air gapped enclave with managed hosts that have not rolled into the central Smart Management count. The capsule synchronisation hides the enclave hosts from the central inventory walk if the registration record is not consolidated; the buyer who walks only the central Satellite Server inventory misses the enclave count. The discipline is the consolidated walk across every capsule, performed at the Satellite Server but with each capsule's managed host count enumerated separately and totalled. The pattern overlaps with the broader treatment in the counting RHEL systems accurately note.

The renewal economics on a capsule estate sit on three structural decisions.

The first decision is the capsule footprint at each site. A capsule sized for two thousand managed hosts at one branch runs idle when the branch has two hundred; the over sized capsule consumes one or more RHEL entitlements that could be released by consolidating to a smaller footprint. The renewal cycle is the natural review point. The sibling treatment of capsule sizing sits in the Satellite versus Red Hat Cloud Console economics note , which sets out the hosted alternative for shops that are willing to leave the on premises Satellite topology.4

The second decision is the high availability pattern. A capsule HA pair adds a RHEL entitlement; the resilience benefit must be weighed against the cost of the additional host. Some sites genuinely need HA capsules (regulated, mission critical); others run HA capsules from inertia rather than necessity. The discipline overlaps with the broader frame of recoverable over entitlement cost.

The third decision is the consolidation of distributed capsules into fewer regional hubs. A topology with thirty branch capsules can sometimes be consolidated into three regional capsules without material loss of locality benefit; the renewal cycle is the natural point at which the topology design is revisited. The pattern overlaps with the treatment in renewal negotiation.

The renewal posture on capsule licensing has three habits.

The first habit is the dual line read. Every capsule is listed in the procurement register twice: once as a RHEL host class entry, once as a content delivery node attached to the Smart Management entitlement on the managed estate. The register is checked at every cycle. The discipline sits inside the broader frame of the 90 day subscription assessment.

The second habit is the consolidated managed host walk. The Satellite Server walk enumerates managed host counts capsule by capsule, totals them across the topology, and reconciles the total to the Smart Management entitlement. Any drift between the walk and the entitlement is investigated at the renewal cycle. The discipline overlaps with the treatment in subscription assessment.

The third habit is the topology review at the renewal cycle. The capsule count is reviewed against the actual managed load at each site; over sized capsules are flagged for consolidation; HA capsules are reviewed against the actual resilience requirement. The discipline keeps the capsule footprint inside the economic frontier rather than drifting with site provisioning history. The broader treatment of cycle discipline sits in the Satellite practice hub. For an engagement against the desk, see the contact form.

Preparing a response? The practice keeps a one-page Red Hat audit response checklist — what to acknowledge, what to preserve, and what not to volunteer in the first fourteen days after the letter arrives.