MFMaycon FerreiraAutomation · Applied AI
← Back to portfolio

DISTRIBUTED SYSTEMS · WINDOWS · IT OPERATIONS

INTERNAL USE

Belarc Inventory

Continuous inventory, Windows agent and contextual service desk

I co-developed an internal system that keeps inventory, technical health, ownership and tickets attached to the right workstation, reducing manual checks during support, maintenance and audits.

View repository
Sanitized Belarc Inventory dashboard with a fictitious device fleet and IT indicators.
FICTITIOUS DATAFleet management and operational context.Public screens were sanitized to avoid exposing company information.
ArchitectureRust · Axum · Tokio · SQLite
Windows agentPowerShell · CIM/WMI · local cache · heartbeat
CollaborationCo-developed with Diogo Rodrigues

SYSTEM SCREENS

From technical collection to support with context

The publication uses only fictitious data and sanitized images from the real internal system.
Detailed Windows workstation inventory in Belarc Inventory.
INVENTORYHardware, software, network and security.
Belarc Inventory ticket Kanban.
SERVICE DESKTicket linked to workstation and requester.
Sanitized Belarc Inventory BI dashboard.
BIVolume, priorities and operational follow-up.
Simplified portal for opening a support ticket.
REQUESTERSimple portal to open and follow requests.
Department ticket queue in Belarc Inventory.
ROUTINGQueues only for configured departments.

Real use

The system is running at my current company; public material replaces names, addresses and internal data with fictitious scenarios.

Not an AI agent

The “agent” is a Rust Windows service that collects and synchronizes data. The project is not presented as an LLM or RAG agent.

01

Problem

During support and audits, discovering hardware, software, ownership, risks, certificates and history required checking multiple sources or relying on operational memory.

02

Architecture

The Rust agent runs PowerShell/CIM collectors, maintains a local cache and sends changes to the Axum/SQLite server over internal HTTP with an agent token. IT, requesters and departments receive different interfaces by role.

03

Continuity and security

The agent uses store-and-forward when the server is unavailable, temporary enrollment for new agents and a LAN/VPN-only model that keeps inventory away from the public internet.

04

Current result

  • Technical inventory and administrative context in the same workstation record.
  • Tickets preserve workstation context throughout support.
  • Dashboards, alerts and compliance indicators help prioritize IT operations.
  • Co-developed and supported in internal use.

Intentional boundary

The server is designed for private LAN/VPN use. Real tokens, databases, logs, attachments and collected company data are not published.

Public quality

The repository includes an isolated smoke test, cargo fmt, clippy, cargo test and a public-tree validation gate.

This case presents a sanitized public version of the real system, with fictitious data and without credentials, internal addresses or corporate inventory.

View code and documentation
Next projectPostagem Redes
Contact