stack --list

Technical skills

From networking and security to virtualization, databases and automation: the tools I use in the engine room of infrastructure.

17 tools01

Network & Security

I decide where the packets go.

  • FortiGate (HA Cluster)
  • OPNsense
  • FortiSwitch
  • Ruijie
  • Cisco IOS (CCNA courses)
  • IPsec
  • WireGuard
  • SSL VPN
  • Cloudflare WAF
  • SafeLine WAF
  • Fail2ban
  • OpenVAS
  • Trivy
  • Semgrep
  • Windows LAPS
  • RBAC
  • MFA / Entra ID
16 tools02

System, Virtualization & Cloud

From physical to virtual, from virtual to containers.

  • Linux Server
  • Windows Server
  • Active Directory
  • GPO
  • VMware ESXi
  • Proxmox VE
  • RKE2 Kubernetes
  • Rancher
  • Longhorn
  • Velero
  • cert-manager
  • MetalLB
  • ArgoCD (GitOps)
  • Docker Compose
  • GitLab CI/CD
  • GitLab Runner
10 tools03

Database & Storage

The goal: replicas in sync, backups tested.

  • PostgreSQL Primary-Replica
  • Patroni
  • wal-g (PITR)
  • pg_stat_statements
  • MariaDB Galera
  • Redis Sentinel
  • OpenSearch
  • MSSQL
  • AWS RDS
  • MinIO S3
18 tools04

Web, Proxy & Automation

Do it twice, and the third time it becomes a script.

  • Nginx
  • Caddy
  • WordOps
  • Plesk
  • HestiaCP
  • Zabbix
  • Uptime Kuma
  • Prometheus · Grafana · Loki
  • PMM
  • Consul DNS
  • Bash
  • PowerShell
  • Python · Flask / FastAPI
  • Next.js
  • Microsoft Graph API
  • Claude Code (AI-assisted dev)
  • Telegram Bot API
  • Exchange Online

Tool list ≠ project experience: not every tool was used to the same depth. For real-world usage, see the projects page.

cat /etc/motd

Architecture principles · Engineering philosophy

rule.01

Single Point of Failure = 0

Every critical layer is designed with redundancy (HA).

rule.02

Automate Everything

Any operation done manually twice becomes a Bash or PowerShell script the third time.

rule.03

Backup != Restore

An untested backup is not a backup (MinIO S3 + automated verification).

rule.04

Zero-Trust & Least Privilege

Packets go only where they need to go, and only as far as they need to.

rule.05

AI accelerates, humans own it

AI speeds things up, but responsibility stays with people: generated code and commands are reviewed first, tested next, and only then go live.

ai --workflow

How I work with AI

prompt → review → test → deploy. The order never changes. Claude writes and refactors, ChatGPT gives a second opinion; a human approves, measures and owns the result.

Between July and October 2026, 19 internal tools were built with Claude Code. Details on the projects page.

chatgpt-memory --summary
İsmail is a technology professional who one day works out from query statistics why PostgreSQL is burning CPU, the next day designs Kubernetes RBAC, another day builds an admin tool in PowerShell, and in between retires unnecessary infrastructure before it is even built by asking "do we really need this?". In his world, a working system is good, an automated system is better, and a secure, documented, automated system is simply how it should be.
— a summary ChatGPT drew from past conversations

Got an infrastructure question, a project or a route tip?

Email is the fastest way. If I'm on the road, I'll reply from the next Wi-Fi.

Send an email