Business application2026-08-16

One place for day-to-day web infrastructure operations

Daily website operations were spread across several tools. This panel brings them into one controlled workflow with clear permissions and an audit trail.

Infrastructure control panel system overview with test CPU, memory, disk and service data
System health and core service status in one overview
Project
D. Svilenković internal tool
Type
Operations web application
Scope
Domains, databases, certificates, backups and monitoring
Technology
PHP 8.3 · MariaDB · system integrations
Status
In active internal use
Technology
PHP 8.3 · MariaDB · SSH · systemd
01

Problem and context

The problem it solves

Domains, databases, certificates, backups and monitoring often live in separate tools. The panel provides a unified view and a shorter route to common operations while keeping each service and responsibility visible.

Service status table with test processes, PIDs, memory usage and uptime
Per-service status with a reload action in the same row
02

Day-to-day operations

One workspace shows domains and DNS records, certificate status, databases, backup jobs, users and core system health. Critical actions return a clear result so the operator knows whether the task actually completed.

Backup overview with test paths, dates and sizes
Recent backups and the latest run result
03

Access control and records

Features are shown according to the user role. Changes leave a time-stamped record, while credentials and executable commands stay outside the public case study.

Mobile system health view with test metrics
Core system metrics on a phone
04

Outcome

Technical delivery

The server side uses PHP 8.3 and MariaDB. The panel connects existing system services through controlled operations and exposes only the data required for the task at hand.

Mobile service status view with test processes
Service status in a table that scrolls on a narrow screen

FAQ

Frequently asked questions

Does it replace every server tool?

It unifies frequent operations and system status. Specialist tools remain available for work that requires deeper administration.

Can it be adapted to another infrastructure stack?

Yes. Modules and permissions are selected around the services, team roles and existing operating process.

Does the public case study reveal credentials?

No. It describes product behavior while credentials, commands and the internal topology remain private.

Next step

Have a project that needs to work better?

Send me your goal and current situation. I will reply with a concrete scope proposal.

Start a project