Services Builds About Writing Contact
home/builds/itguy
BUILD 01 · OPERATIONAL

ITGuy.
AI Infrastructure Agent.

A dedicated AI agent that manages a production VPS entirely through Telegram. Deploy websites, monitor server health, manage DNS, run backups. No SSH session, no terminal, no login screen. Just a chat.

See the proof How it's built
ITGuy Agent
ITGuy
Infrastructure agent · ayebee.xyz
10 minIdea to live site
24/7Monitoring
0Terminals opened
100%Audit-logged
CONTEXT // PROBLEM

The problem this solves.

BEFORE

Server management requires a terminal and your full attention

Every deployment means SSH-ing in, writing Docker Compose files, configuring Traefik labels, setting up databases, managing SSL, checking DNS propagation. You need a laptop, a stable connection, and 30–60 minutes of focused terminal time. Want to deploy something while commuting? Forget it. Want to check if your server is healthy at 2 AM? Open a terminal.

→
AFTER

Send a Telegram message. The agent handles the rest.

Describe what you want in plain language. ITGuy inspects the server, writes a plan, waits for your approval (an exact phrase, not a vague "ok"), executes through vetted scripts, verifies the outcome independently, and logs everything to a git-tracked audit trail. I deployed three production websites from the back seat of a car, on mobile, in 10–12 minutes each.

PROCESS // 7_STEP_LOOP

The 7-step workflow.

Every state-changing action follows this sequence. No exceptions, no shortcuts.

01
👁️

Observe

Read-only server inspection. Verify actual state.

02
📋

Plan

Write concrete steps with exact commands. No vague proposals.

03
🔐

Approve

Human sends an exact approval phrase. "Ok" won't work.

04
⚡

Execute

One step at a time through vetted, root-owned scripts only.

05
✅

Verify

Independently confirm: site responds, HTTPS valid, logs clean.

06
📨

Notify

Report outcome on Telegram. Plain language, including partial failures.

07
📝

Record

Audit log committed to git. Full detail, timestamped, reviewable.

ARCHITECTURE // TRUST_MODEL

The container is the brain. The VPS is the hands. The scripts are the only bridge.

The core security principle: the AI reasons inside a Docker container with zero host privileges. Every action on the server flows through a narrow layer of root-owned, human-reviewed scripts that the agent can execute but never edit. No Docker socket, no raw sudo, no shell access. The agent earns trust one vetted script at a time.

system architecture
Telegram human in the loop ITGuy container Hermes agent · the brain zero host privileges no docker socket · no sudo Vetted scripts root-owned bridge VPS the hands chat execute act
READ-ONLY

Health Dashboard

Uptime, load average, disk, RAM, top processes. Runs automatically, no approval needed.

READ-ONLY

Container Inventory

All containers, status, restart counts, health checks, resource usage, images, volumes.

READ-ONLY

Security Posture

Firewall status, Fail2Ban jails, failed logins, pending patches. Weekly report to Telegram.

APPROVAL-GATED

Deploy Ghost / WordPress / Static

Full deployment: container, database, Traefik routing, SSL. Exact approval phrase required.

APPROVAL-GATED

Container Management

Restart, stop, backup containers. Pre/post state verification baked into every script.

APPROVAL-GATED

SSL Renewal + WordPress Updates

Force ACME re-check, WP-CLI update with pre-update DB backup. Medium risk, scoped execution.

PROOF // FIELD_EVIDENCE

Real deployments, from a Telegram chat.

These sites were built and deployed while I was in a car, heading to a friend's place. No laptop, no terminal, no SSH. Just Telegram messages on a phone.

Telegram: requesting a website build
the starting point — one message, one reference, one PDF. ITGuy parsed the brief, chose the simplest deployment option (static), asked clarifying questions, and started building. Entirely on mobile, in transit.
Telegram: plan and approval flow
plan → exact approval phrase. No fuzzy "ok" accepted — you send the exact phrase or nothing happens.
Telegram: execution and verification
execute → verify → audit. Action taken, DNS verified, audit entry committed to git.
Telegram: site is live confirmation
site is live — URL confirmed, SSL valid, full deployment summary of what was deployed and how.
🌐
LIVE

codeshow.ayebee.xyz

Static portfolio site. Built from a PDF and a reference URL in a single Telegram session.

Visit site
🌐
LIVE

wpshow.ayebee.xyz

WordPress deployment. Container + MySQL + Traefik + SSL, all provisioned through chat.

Visit site
🌐
LIVE

agnishwarbanerjee.info

This portfolio site. Static deployment to nginx:alpine, managed and maintained by ITGuy.

You are here
ALWAYS_WATCHING // CRON

Automated monitoring, delivered to Telegram.

Three cron jobs run continuously with zero human intervention. Every morning: a full health report (load, disk, memory, all containers, SSL expiry). Daily: a dedicated SSL certificate watch that flags anything under 14 days. Sundays: a security and backup summary covering firewall state, Fail2Ban activity, failed logins, and pending patches. Pure observation. No risk, no approval required. Just visibility, delivered where I already am.

Daily health report on Telegram
daily health report — load, disk, memory, containers, SSL expiry
10 min
Idea to live site

Including DNS, SSL, and deployment verification

0
SSH sessions needed

All management via Telegram on mobile

3
Auto-monitoring jobs

Health, SSL, security reports on schedule

100%
Actions audit-logged

Git-tracked with pre/post state verification

SECURITY_MODEL // DELIBERATE_LIMITS

What the agent deliberately cannot do.

The most interesting part of the design is what's missing.

Prohibited by design

  • Run arbitrary shell commands
  • Edit SSH config or firewall rules
  • Use sudo outside vetted scripts
  • Reboot the VPS automatically
  • Delete containers or backups
  • Access the Docker socket

Enforced by architecture

  • SSH restricted to internal Docker bridge
  • Each script individually whitelisted in sudoers
  • Scripts root-owned — agent can execute, not edit
  • Exact-phrase approval (no fuzzy matching)
  • Input validation via regex before execution
  • Every action git-committed to audit trail
INTERESTED? // OPEN_CHANNEL

Ask me to walk you through it.

I can show you the live Telegram interface, the audit trail, and the full security model. If you're thinking about how AI agents should interact with production infrastructure, this is a working answer.

Get in touch ← All builds