Architecture

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

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

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 touches sensitive information: the physical image of your infrastructure, and the inventory that can be deduced from it. Our starting choice is simple: everything runs on your premises. This page describes how the platform is divided, what each component does and what exchanges exist between them.

RackIntelligence architectureYour servers · containersBrowsercomputer or phoneInterfaceaccounts, screensAnalysis enginephoto → detectionsLabelsread on siteLicensechecked by eachInventory toolnever queriedHTTPSphotophotono connectionInternetno flow neededYour serversBrowsercomputer or phoneInterfaceaccounts, screensAnalysis enginephoto → detectionsLabelsread on siteNo connection to your inventory toolNo flow to the Internet needed
Everything runs on your servers. The platform does not query any of your systems and needs no flow 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, analysis results, diagrams and exports are produced and stored on your infrastructure. The analysis engine and label reading also run on site. No online service is required to analyze a photo, and the platform works without Internet access.

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 at the office and from a phone: photo import, projects, results, exports; authentication and accounts.
Analysis engineLocates equipment in the photo: family, model when legible, U position, confidence level.
Label readingReads the text of labels visible in the photo, locally, on the server.
ComparisonMatches the detected devices against the inventory file (CSV or Excel) the user uploads to an analysis.
LicenseChecked by each component; without a valid license, nothing starts.

The analysis engine only knows the photo it is given: it receives an image and returns detections. Your inventory is never queried remotely: it is the user who drops, whenever they wish, an export of your inventory onto an analysis. The platform does not write to any of your systems.

What talks to what

Exchanges follow a short, predictable path:

  1. The browser talks to the interface

    A signed-in user uploads photos from their workstation, or photographs the rack from their phone. They do not reach any other component directly. Photos can also be dropped into the server’s input folder.

  2. The interface hands the photo to the engine

    The analysis engine returns the equipment it located, and label reading returns the text it read. These exchanges stay internal to your installation.

  3. The result stays on the platform

    Boxed devices, U positions, rack diagram and, where applicable, comparison with your inventory file: everything is saved on your servers, in the site project.

  4. Exports leave when you download them

    PowerPoint report, CSV or Excel inventory, SVG or draw.io diagram: these are files the user downloads. Nothing is sent elsewhere.

The platform’s System page shows the services actually reached and their status, the acceleration used (graphics card or processor), local label reading and the installed version. 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
FlowsWhat forStatus
Computers and phones → InterfaceSign in, send photos, drop an inventory file, download exports.Required
Interface → Analysis engineHand over the photo, receive the detections. Network internal to the containers.Internal
Interface → Label readingRead the text visible on the photo, on the server.Internal
Drop → Input folderDrop photos directly on the server.Restricted access
Installation → InternetNo use: no analysis, no license, no automatic update.Block
  • Expose only the interface to users’ workstations and phones; keep the analysis engine and label reading on a network internal to the containers.
  • Block all outbound flows from the installation: the platform does not need them to operate.
  • Restrict access to the server’s input folder to the people and tools that need to drop photos there.
  • 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. The temporary password must be changed at first sign-in.
  • Sign-in attempts are throttled, per account and per address, and sessions expire.
  • Passwords are stored as hashes, never in plain text.
  • Received photos are checked before analysis: limited size, content that is actually an image (JPEG, PNG or WebP), not just the extension.
  • 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 releases and the license are described 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.