Architecture

Architecture and isolation: what runs on your premises, and what talks to what

The platform is installed as containers on your infrastructure. Here are its components, their role, and the only exchanges they have with each other and with your inventory tool.

Contents
  1. A container installation, on your servers
  2. The components and their role
  3. What talks to what
  4. Network isolation: what we recommend
  5. A reduced exposure surface
  6. What we hand over to you

A platform that reads photos of your rooms and compares what it sees with your inventory touches two sensitive things: the physical image of your infrastructure and your reference inventory. Our starting choice is simple: everything runs on your premises. This page describes how the platform is split up, what each component does and which exchanges exist between them.

RackIntelligence architectureYour servers · containersBrowsercomputer or phoneInterfaceaccounts, screensAnalysis enginephoto → detectionsComparisonphoto vs inventoryLicensechecked by eachConnectordedicated tokenInventory toolyour inventoryHTTPSphotodetectionsAPI, dedicated tokenInternetno flow neededYour serversBrowsercomputer or phoneInterfaceaccounts and screensAnalysis enginephoto → detectionsComparisonphoto vs inventoryConnectordedicated tokenInventory toolyour inventoryNo flow to the Internet needed
Everything runs on your servers. Only the connector talks to your inventory tool, with a dedicated token; nothing goes out to the Internet.

A container installation, on your servers

The platform is delivered as containers that you install on your own servers, in your room or in your usual hosting environment. There is no version hosted by us that your teams would connect to: the platform’s address is an address on your network.

This installation mode has a direct consequence: rack photos, surveys, comparisons and logs are stored on your infrastructure. The analysis engine also runs on site. No online service is required to analyze a photo.

The choice of operating system, sizing and server location is a matter for your infrastructure; the precise prerequisites are provided as part of the project.

The components and their role

Each component has a limited responsibility. This separation makes the whole easier to read for your operations and security teams.

ComponentRole
InterfaceWeb pages used in the office and in the field; authentication and accounts.
Analysis engineLocates equipment in the photo: family, U position, confidence level.
ComparisonRecognizes the rack and checks the photo against the inventory, U by U.
Inventory connectorThe only point of reading and writing to your inventory tool, with a dedicated token.
LicenseChecked by each component; without a valid license, nothing starts.

The analysis engine does not know your inventory: it receives a photo and returns detections. The comparison matches these detections with the inventory, and the connector alone talks to the inventory.

What talks to what

Exchanges follow a short, predictable path:

  1. The browser talks to the interface

    A signed-in user sends a photo from their computer or phone. They do not reach any other component directly.

  2. The interface hands the photo to the engine

    The analysis engine returns the equipment it located. The exchange stays internal to your installation.

  3. The comparison reads the inventory through the connector

    The connector queries your inventory tool with its dedicated token, then the comparison produces the survey: matching, different, missing from the inventory, not seen.

  4. Writing to the inventory waits for human approval

    No change is sent to the inventory without approval. When two-level approval is enabled, one person proposes and another approves.

The platform’s System page shows the services actually reached and their status. Your teams can thus check, from the interface, that the list matches what is expected.

Network isolation: what we recommend

Splitting into components makes it possible to restrict flows to the strict minimum. Network configuration is a matter for your infrastructure, but here are the principles we suggest applying:

Network flows of the installation
FlowWhat forStatus
Computers and phones → InterfaceSign in, send photos, approve discrepancies.Required
Interface → Analysis engineHand over the photo, receive the detections. Network internal to the containers.Internal
Comparison → ConnectorRequest the rack’s inventory, pass on approved writes.Internal
Connector → Your inventory toolRead the inventory; write only what has been approved. Dedicated, non-administrator account.If inventory linked
Installation → InternetNo use: no analysis, no license, no automatic update.Block
  • Expose only the interface to users’ computers; keep the analysis engine and the comparison on a network internal to the containers.
  • Open, outbound, only the flow from the connector to your inventory tool.
  • Give the connector’s token the rights it needs, and nothing more: the installation creates a dedicated, non-administrator account in your inventory tool, which reads the inventory and writes only to the objects the platform updates. If you do not want to write from the platform, its write rights can be removed after installation: the comparison still works, and the inventory tool then refuses writes.
  • Place the installation behind your usual filtering and monitoring equipment.

A reduced exposure surface

Several design choices limit what can be reached from outside the installation:

  • Accounts are created by an administrator: there is no open sign-up.
  • Sign-in attempts are limited and sessions have a limited duration.
  • Pages are served with strict security headers.
  • The platform is delivered compiled and each release is signed; the signature is checked at installation, then at each start launched by the installation script.

Details of accounts and roles are described on the page Accounts, roles and rights; details of releases on the page Signed updates and license.

What we hand over to you

As part of a project, we hand over to your teams the architecture description, the list of flows, the installation prerequisites and the installation procedure. These documents serve as a basis for your own risk analysis and for discussions with your CISO. To obtain them or ask a question, write to us.

Stay in touch

New releases, newly recognized equipment, articles: one email when there is something new, nothing else.