Integration approach

Know the depth.
Not just the vendor name.

A connection is useful only when you know what it can actually observe or operate. Yerokom’s support model distinguishes discovery, inventory, observation and validated change.

Verified scope

What can you inspect today?

Available evidence, by exact scope — reviewed 10 September 2026
TechnologyVersion / methodWhat is evidencedBoundary
Red Hat Enterprise Linux10.2, x86_64
SSH + existing Python
Actual read-only OS and hardware collection
10 Sep 2026, 19:42 UTC
One lab host. No agent, writes or platform admission.
Inspect the real record ↗
RedfishHTTPS adapter source
No vendor/version lab certification
Source and synthetic/local TLS test scopeNot represented as a released, vendor-qualified integration
Firmware / arbitrary OS executionNo released runtime matrix verifiedValidation model and requirementsRuntime, licensing and hardware validation must be confirmed; not a blanket execution service
Open the machine-readable scope record ↗
Three collection paths

Use the strongest supported source.

Native protocols

Server and network collection through appropriate native protocols, including SSH, WinRM, SNMPv3 and vendor interfaces. Availability is confirmed per release.

Provider APIs

Cloud, SaaS, virtualization and identity interfaces can supply authoritative context where supported and permissioned.

Existing enterprise tools

Customer-owned endpoint, security, observability and ITSM tools can remain authoritative for their existing capability.

Support depth

A support level is not a blanket compatibility claim.

Yerokom support-level definitions, not a released compatibility catalog
LevelMeaningEvidence required
L0SeenPresence detected.
L1IdentifiedVendor, product or model identified with stated confidence.
L2InventoriedDetailed hardware, software or configuration collected.
L3ObservedHealth, performance or configuration state collected.
L4ManagedA specific write operation has been tested and authorized.
L5Validated changePrecheck, execution, verification and recovery behavior established.
L6Lab certifiedTested against an actual vendor-supported environment and version matrix.

No technology is asserted to be L6 on this page. Request the exact vendor, version, capability and evidence matrix for your proposed evaluation.

Talk to Yerokom

Confirm the integration you need.

Include the vendor, product, version and intended read or write workflow in your enquiry. The reply should distinguish delivered capability, limitations and prerequisites.

Talk to sales