Projects
Case studies from production infrastructure, security, and platform work — each with the problem, approach, and measured outcome.
2026
-
A resume and brag document template built using Typst
Tech- Typst
- GitHub
-
VPS Benchmarking
YABS + nws.sh benchmark harness across multiple VPS to answer which VPS for which workload?
- HostDzire 8GB and 16GB VPS benchmarked
Tech- Debian 12
- YABS
- nws.sh
- iperf3
Case study — problem, approach, outcome
Problem
Picking a VPS tier on price alone leads to surprises. Needed measured compute, disk, and global network data to place production vs. dev workloads correctly.
Approach
- Standardized harness: YABS (
curl -sL https://yabs.sh | bash -s -- -9 -6) plus nws.sh global speedtest, iperf3, and ping/routing suites. - Ran the full matrix on HostDzire 8GB and 16GB tiers in Mumbai, same OS (Debian 12), same flags.
- Published raw output verbatim so anyone can audit the numbers.
Outcome
- 16GB tier: 8 vCPU / 15.6 GiB / 196.8 GiB measured — production candidate.
- 8GB tier: 4 vCPU / 7.7 GiB / 78.7 GiB measured — dev/non-prod sweet spot.
- Links to the benchmarks:
Stack
- Debian 12
- YABS
- nws.sh
- speedtest
- iperf3.
-
A modified fork of astro-erudite theme
Tech- Astro
- GitHub
2025
-
M365 Business Premium Security Rollout
Opinionated M365 lockdown — break-glass, MFA + Conditional Access, Intune, Defender, DLP — written up as a no-BS field guide
- MFA enforced for every user on every cloud app
- Legacy auth blocked. Intune + Defender baselines on all devices
- Repeatable lockdown path published as a field guide
Tech- M365
- Entra ID
- Intune
Case study — problem, approach, outcome
Problem
Small teams need enterprise-grade security without enterprise headcount. Default M365 tenants leave legacy auth on, MFA optional, and DLP/Defender unconfigured.
Approach
- Break-glass Global Admin with offline credentials, excluded from MFA enforcement by design.
- Conditional Access MFA enforcement for all users and all cloud apps.
- Legacy auth blocked; Intune compliance + Defender baselines rolled out per device.
- DLP policies for the data that actually leaks in SMBs, documented as a repeatable runbook.
Outcome
- Repeatable lockdown path for teams up to 300 users.
- Full write-up published as the M365 Security Architecture Guide so others can follow the same steps.
- Baseline that maps cleanly to ongoing ITIL incident/change practice.
Stack
- Microsoft 365 Business Premium
- Entra ID, Intune
- Defender
-
IT/OT Network — Purdue Model
First formal IT department at TopSolid India + Purdue-model implementation for India's first Industry 4.0 experience center with SmartPM
- Formal IT/OT operations established where none existed
- Plant network segmented into auditable Purdue zones
- India's first Industry 4.0 experience center delivered with partners
Tech- Networking
- Purdue Model
- IT/OT
- Industry 4.0
Case study — problem, approach, outcome
Problem
No formal IT department, no segmentation between corporate IT and plant-floor OT. Any change risked production disruption, and there was no clean path to onboard international partners.
Approach
- Stood up the organization’s first formal IT department: SLAs, SOPs, incident/change ownership.
- Engineered network infrastructure on the Purdue model — enterprise, DMZ, supervisory, and control zones with controlled conduits.
- Separated IT/OT operations end-to-end across production environments.
- Co-built India’s first Industry 4.0 experience center with international partners on top of that foundation.
Outcome
- Formal IT/OT operations where none existed.
- Segmented, auditable plant network that keeps production traffic isolated.
- Partner-ready platform for Industry 4.0 demos and deployments.
Stack
- Network segmentation
- Purdue model
- ITIL operations
- Vendor management.