Case study · AI and SaaS

Server Agent

My own product, in development: an AI system administrator for servers and sites

Server Agent is my own AI system administrator, in development: it checks cPanel, Plesk, DirectAdmin and Linux servers and fixes problems in four levels with approvals.

Client

Own product

Period

In development

Server Agent

What I built

Disclosure: Server Agent is my own product, and it is still in development.

WP Agent and WHMCS Agent look after one kind of system each. Server Agent goes a level down, to the servers themselves: cPanel/WHM, Plesk, DirectAdmin, CyberPanel or plain Linux, and the WordPress, Laravel, Node, PHP and static sites on them. The screenshots show it with demo servers and made-up company names.

Fixes come in four levels: restarts and cache clears; PHP limits, versions and runaway processes; malware quarantine, blocking attacking IPs and closing known PHP holes; and reboots, database restores and rebuilds, which always ask. Every fix runs as check, do, verify and undo. Admins write Do and Don't rules in plain words, enforced rules decide what is denied or always asks, a connection to one account cannot run server-wide actions, and destructive shell commands are blocked.

It shares its engine with my other agents. It can be ordered built to order: Server Agent.

The challenge

Give an AI enough access to fix servers while keeping serious actions in human hands.

How I solved it

Four fix levels with check, do, verify and undo, written rules and a block list of destructive commands.

The outcome

In development; demo servers run through the full check and approval flow.

Tech stack

Python SSH cPanel/WHM Plesk DirectAdmin Claude Code

Inside the build