session — infra-console
visitor@web:~$ whoami

Your servers, your DNS, your domain.
Someone should actually be watching them.

I'm Abin Babu — a cybersecurity graduate who now manages live production infrastructure for a real client: AWS, DNS, hosting, and the CMS platforms running on top of it. I keep sites online, secured, and recoverable, so you don't have to learn what a security group is at 2am.

$ systemctl status --all
9 services · monitored
aws-compute
EC2 · Lambda · Amplify — configured & running
storage-backup
S3 automated backups — scheduled
dns-routing
Route 53 · Cloudflare — propagated
hosting-panel
CloudPanel · cPanel · Plesk — online
cms-layer
WordPress · Magento — patched
firewall
AWS SG · Linux/Windows FW — hardened
ssl-certs
auto-renew · expiry watch — monitored
mail-delivery
SES · SPF/DKIM/DMARC — verified
migration-lane
host-to-host · to-cloud — on standby
ls services/

What I actually do

No vague "digital solutions." Here's the exact stack I run for clients today, and can run for you.

Cloud

AWS infrastructure

EC2, Lambda functions, S3, Route 53, SES for transactional mail, and Amplify deployments — set up, configured, and kept running.

Hosting

Server & panel management

CloudPanel, cPanel and Plesk — provisioning, site deployment, SSL, and day-to-day server administration on Linux.

Networking

DNS & domains

Nameserver setup, Cloudflare configuration, DNS records and propagation — three years of hands-on hosting-industry DNS work.

CMS

WordPress & Magento

Installation, configuration, and ongoing management of both platforms for client sites and storefronts.

Security

Firewall & hardening

AWS security groups plus native Linux and Windows firewall configuration, tuned to what's actually exposed.

Resilience

Backups & recovery

Automated S3 backup pipelines, so "the server died" is an inconvenience, not an ending.

Migration

Site & server migrations

When you decide to move — host to host, or onto AWS — it's planned, tested, and switched over with minimal downtime. And if staying put serves you better, I'll say so.

Certificates

SSL — issued & watched

Certificates installed, set to renew automatically, and monitored — so an expired SSL never takes your site down or scares off visitors with browser warnings.

Email

Business email that delivers

Mail setup on your own domain, with SPF, DKIM and DMARC configured properly — so your invoices and replies land in inboxes, not spam folders.

cat onboarding.log

How a new client actually starts

Four steps, in order — because skipping the audit is how people end up hiring someone after the breach, not before it.

01 · audit

Look at what's live

Current hosting, DNS, open ports, backup state — a plain-language report of what's exposed.

02 · configure

Set up the real thing

AWS, DNS, panel, and CMS configured properly — not just "working," but documented and repeatable.

03 · harden

Close what shouldn't be open

Firewall rules, security groups, and access tightened to what the site actually needs.

04 · monitor

Keep watching it

Backups running, uptime checked, and a person to call when something changes.

cat about.log

Background

now
Managing live infrastructure for a client — AWS, Route 53, CloudPanel, and the CMS layer on top, end to end.
3 yrs ago
Hosting industry experience — DNS configuration and nameserver management, Cloudflare setup for external clients, cPanel and Plesk administration.
education
Cybersecurity graduate — the audit-first, least-access mindset behind every setup on this page.
side project
Built a warehouse stock-management demo site, end to end, to keep shipping outside client work.
./contact.sh

Start a conversation

Tell me what's running and what's worrying you about it. Use the live chat bubble for a quick word, or type below to send me an email.

contact — session
system: connected. describe your site, host, or what's currently breaking.

This opens a pre-filled email to admin@thatsgrand.uk, ready to send from your own mail app.