ProductVisit project

AIceberg

Monitoring, agents and log analysis.

Identified technologies

GoPHP / Yii2Flutter

The problem

Monitoring software means connecting device signals to central processing and operation screens.

The solution

AIceberg brings device agents, server processing, web screens and a mobile app into one monitoring platform.

What makes up the solution

PHP/Yii2 system with administration, client areas and APIs.
View technical details →
Go runtime with separate API, task and scheduling processes. MySQL and Redis Streams have different roles.
View technical details →
Go agent for collecting signals in the monitored environment, separate from the Flutter monitoring app.
View technical details →

Project scope The architecture is evolving. PHP and Go work together as processing moves to the Go runtime in stages.

Download the app

Availability and requirements are set by each store.

My contribution

I designed AIceberg and developed its architecture and collection, processing and monitoring components. The work connects agents, the web system, Go runtime and mobile app.

Architecture overview

Agents collect data. The web app, APIs, workers and schedulers manage processing and operations.

Technical structure

Technology by module.

Four components with separate roles: web platform, processing, mobile access and collection in monitored environments.

What each part does and which technologies support it. A module in the code does not mean all its features are complete or published.

01 / Existing code

System

PHPYii2JavaScriptBootstrap

Platform web application and APIs.

The admin, cliente, api, console and common modules organize screens, access, commands and shared services. The public website is a separate surface.

02 / Existing code

Runtime/API

GoMySQLRedis StreamsHTTP / JSON

Processing and operation services.

Separate API, worker, scheduler and observer entry points. Domain code and adapters stay outside the PHP screens. Functions move from legacy code in stages.

03 / Existing code

Mobile app

FlutterDartSQLiteFirebase

Mobile access to the platform.

Android/iOS app with HTTP communication, local storage and notification integrations. It does not contain the server processing engine.

04 / Existing code

Agent

GogopsutilHTTP / JSONLinux / Windows

Collection in monitored environments.

Separate from the central runtime: collects signals, prepares data and sends it to the platform. Capabilities and support vary by operating system.

How the parts connect

The agent sends telemetry to the platform. Web and mobile present the operation. The runtime handles processing moved to Go. PHP and Go coexist during this work.

Data and integrations

MySQL is the runtime’s durable source. Redis Streams transports tasks in defined parts of the system. It does not replace durable storage. The app uses SQLite locally.

Quality and operations

GitHub Actions, component checks, artifacts and release/rollback procedures. Each runtime function has its own rollout controls. This overview does not claim a completed migration.