Security
Installed on your servers: the photos stay on your premises
Room photos, analysis results, reports: the platform is installed on your infrastructure, in containers, and analyzes photos on site. What this implies, and how installation works.

Contents
A photo of a technical room is not a harmless image. It shows how a site is organized, the type of equipment, sometimes labels and internal markings. An inventory, for its part, describes an entire network. This data belongs with you, and nowhere else.
That is why the platform does not work like an online service. It is installed on your servers, and that is where it analyzes the photos.
What stays with you
Once installed, the platform keeps all the data it produces or receives on your infrastructure. Nothing is copied elsewhere for it to work:
- the photos of racks, imported at the office or taken from a phone;
- the analyses : detections, U positions, confidence levels, comparisons with the inventory files you upload;
- the inventory of projects and the site reports;
- the user accounts of users.
Analyzing a photo requires no online service. The engine runs on the same server as the rest of the platform: the photo does not leave your network to be analyzed.
Why not an online service?
An online service is easy to try, but it requires sending your photos and your inventory outside your network. For an operator, a hosting provider or a large company, this raises legitimate questions: where the images are stored, who can access them, how long they are kept, which law applies to them.
By installing the platform on your premises, these questions have a simple answer: the data stays under your control and follows your own security, backup and retention rules. Your teams apply the same policies to the platform as to their other internal applications. The topic is covered in Sovereign and on-site hosting.
A container-based installation
The platform is delivered as containers. This format has two advantages for your operations teams: it isolates the platform from the rest of the system, and it installs the same way whatever Linux distribution runs on your servers.
Precise server sizing, the choice between a physical and a virtual machine, and integration with your monitoring are defined with you, as part of the project, based on the number of sites, racks and users. Analysis can run on a CPU or be accelerated by a graphics card.
Prepare the server
Your teams provide a server, physical or virtual, with a container engine, following the procedure supplied as part of the project.
Verify the release
The delivered release is signed. Its signature is verified at installation, before any startup: a modified release does not install.
Install the license
A single license is verified by every component. Without a valid license, the platform does not start.
Adjust the settings
The administrator chooses the analysis engine offered by default and the confidence threshold below which a device is marked “to check”.
Create the accounts
The administrator creates the user accounts, with a temporary password to change at first sign-in. There is no open sign-up.
Delivered compiled, under license
The platform is delivered compiled. You install a finished product, not source code to maintain. Each new release follows the same path: delivery, signature verification at installation, then startup if the license is valid.
This also protects your installation: a release that was altered between its publication and its installation is rejected. Details are in Signed updates and license.
What the platform calls, and nothing else
A platform installed on your premises must not depend on external services behind the scenes. The System page shows the services the platform actually reaches and their status: the analysis engine and label reading, both installed on your server. It also shows the acceleration used, graphics card or processor, and the installed version.
Your network teams can thus check what is expected, and compare it with what they observe on their firewalls: analyzing a photo requires no internet access. See also Subprocessors and network flows.
Access and control
Access to the platform is restricted to accounts created by an administrator, with a username and password. Each new account receives a temporary password, to change at first sign-in. Sessions expire after a limited time, and repeated sign-in attempts are throttled, per account and per address.
These rules also apply from a phone: a phone does not open any special access, it uses an account like any other.
On the data side, you stay in control: an analysis can be deleted from the history, and a project can be deleted too.
FAQ
Is an internet connection needed to analyze a photo?
No. The analysis engine runs on your server, and no online service is required to analyze a photo.
Can technicians survey from a phone?
Yes. From the phone’s browser, the platform opens the camera directly. The phone connects to the platform installed on your premises, according to the network access you define: the photo is sent to your server, not to a third-party service.
Do we need to connect the platform to our inventory tool?
No. The platform works on its own: projects, analysis, reports and exports. To compare a survey with your inventory, simply upload a CSV or Excel export of your CMDB to the analysis. There is no direct connection, and nothing is written to your inventory.
Can we try it before installing?
Yes. Before any installation, you can see the platform on our demo data, or on a few of your photos analyzed on an isolated instance. Request a demo, or describe your estate to get a quote.


