Available · Lahore
I'm Ameer Hamza, a Linux systems engineer on a team that runs 350+ servers across bare metal, VMs, containers and multiple clouds. I build telecom platforms on Proxmox and VMware, keep their databases replicated and their dashboards honest, and test systems the way an attacker would. I've delivered 67 freelance orders rated 5.0★.
I'm Ameer, a Linux systems engineer from Lahore. I build infrastructure that stays up, I watch it closely, and I test it the way an attacker would.
At Hoboetech I'm part of the infrastructure team that runs and looks after 350+ servers: bare-metal machines, virtual machines, containers and cloud VMs across multiple providers, most of them powering telecom messaging platforms. I install and network physical servers, build Proxmox and VMware environments, put HAProxy and Nginx in front of applications, replicate MySQL and MongoDB, and wire everything into Grafana and Prometheus so a problem pages someone before a customer notices it. On the security side I run a Wazuh SIEM that watches 70+ of those servers.
I came into this field through security. I trained as a penetration tester at Corvit, and the habit stayed with me: whatever I build, I harden it, and I check it from the outside too.
Since 2022 I have also worked with clients directly on Fiverr and Upwork, from one-hour fixes to complete server setups and one-to-one pentest training. My rules are simple: a backup before every change, clear communication while I work, and documentation when I hand over.
Most problems cross these lines. A slow site can be a database, a load balancer or an attack. Working across all of them means I can follow the problem wherever it goes, and hand over something your team can run.
Physical servers from the rack up: OS installs, RAID, networking and routing. Proxmox VE clusters with HA and ZFS replication, VMware Cloud Director environments, and web tiers behind Nginx, Apache2 and HAProxy.
Automation that removes manual, error-prone steps: Ansible playbooks for server builds and configuration, Docker and Docker Compose deployments, CI/CD pipelines with GitHub Actions and Jenkins, Bash and Python tooling, PM2 and cron for long-running jobs, and AWS deployments (EC2, ELB, Auto Scaling, Route 53). Working knowledge of Kubernetes and Terraform.
Replicated and clustered data tiers that survive a failed node: MySQL master–slave and master–master, MongoDB replica sets, Redis and Dragonfly, plus the backups, disaster-recovery plans and runbooks behind them.
Prometheus exporters, Grafana dashboards and alert rules, and centralised logs with Loki, Graylog or ELK. I run Kannel and SMPP messaging platforms day to day, and I troubleshoot SIP/VoIP signalling at a working level.
Security monitoring with a Wazuh SIEM: service-aware log collection, detection rules, active response, file-integrity monitoring and vulnerability detection. Web application and Active Directory penetration tests with written reports, and server hardening. I configure firewalls (iptables, pfSense, Cisco ASA, Huawei NGFW) and teach penetration testing one to one.
You hand over the code; I handle everything that turns it into a public project people trust and find. That means auditing the git history for secrets, choosing the licence, structuring the repository, and naming it with a description and topics that rank in GitHub search. It also covers commit and merge conventions, branch rulesets, Dependabot, secret scanning and private vulnerability reporting, CI and release workflows, community files and the launch itself.
We agree what “done” looks like, what I can touch, and how I get access, ideally a separate sudo user with an SSH key.
Before any change I take a snapshot or backup and write down how to roll back.
I make the change, test it, and keep you updated in plain language while I work.
You get a short report: what changed, why, how to check it and how to undo it.
Real production work, written up as problem → decisions → outcome. Client and server names are anonymised, and screenshots use dummy values.
A 4-node production cluster where every critical service has a failover partner and storage replicates every 15 minutes, upgraded from Proxmox VE 8 to 9 one node at a time.
Prometheus exporters, Grafana dashboards and alert rules for Kannel, smppbox and KSMPPD. Built for production, then open-sourced under Apache-2.0.
A 3-node Wazuh cluster watching 70+ Linux servers: log collection matched to each server's services, detection rules, active response, file-integrity monitoring with YARA, vulnerability detection and WhatsApp alerts.
Infrastructure for a six-application enterprise messaging platform across 20+ servers: OS builds, HAProxy, replicated MySQL and MongoDB, monitoring and disaster recovery.
An 18+ server environment for a telecom communications platform across availability zones, with edge firewalls, NAT, IPsec tunnels between zones and cross-zone replication.
One place to search every log (Apache, syslog, SSH sessions, network devices, Kannel and custom apps) with retention rules, dashboards and alerts on critical patterns.
A replica set with a tuned primary/secondary layout and an arbiter, read preferences for query distribution, replication-lag monitoring and documented recovery procedures.
Production infrastructure for a field-operations application across 6+ servers: Apache2 load balancing, MySQL master–slave replication, Grafana monitoring and a documented disaster-recovery path.
Freelance project: one Grafana platform for a client's servers and databases, with MySQL and MongoDB data sources, custom dashboards, threshold alerts, Loki log aggregation and Tempo tracing.
A production website on AWS: Red Hat Enterprise Linux on EC2 behind an Elastic Load Balancer, DNS in Route 53, and Cloudflare SSL for encrypted traffic end to end.
A segmented lab with pfSense, an Active Directory domain, Linux and Windows clients and OpenVAS, where I practise the attacks I test for. Plus my method for client web and AD assessments.
A US AI-infrastructure startup handed me the code of three projects. I did everything else to take them public: repository structure, GitHub SEO, history audit, licensing, commit and merge rules, rulesets, security, workflows and releases.
Hoboetech Pvt. Ltd. · Lahore
Fiverr & Upwork · Remote
The Dev Corporate (TDC) · Lahore
Corvit Systems · Lahore
A computer science degree, plus 14 certifications in security, networking and cloud. 10 of them can be checked on the issuer's own site: press Verify.
Government College University (GCU), Lahore
A four-year computer science degree with a strong systems core: operating systems, computer networks, databases and algorithms, the foundations I now use every day on production servers.
Multi-course programme covering security tools and attacks, roles and OS security, network and database vulnerabilities, incident response and forensics, threat intelligence and a breach-response capstone.
Six-month Government of Pakistan (PM Youth Skills) programme delivered by Corvit Networks. Firewalls, penetration testing and Linux. Grade A+.
Analysed real breaches and the response to each: attack vectors, timelines and lessons for defenders.
TCP/IP and network security basics, plus database security and common vulnerabilities such as SQL injection.
Security roles and processes, access management, and Windows, Linux and macOS security.
Threat actors, attack types, and the key security tools and concepts (CIA triad, firewalls, antivirus, cryptography).
Networking from the physical layer to the application layer: TCP/IP, DNS, DHCP, NAT and troubleshooting.
Huawei associate certification in cloud computing: virtualisation, cloud infrastructure and FusionCompute.
Huawei associate certification in network security: firewalls, VPNs, NAT and security policies.
CCNA prep: network fundamentals, switching, VLANs and network access.
Advanced penetration testing with Kali: exploitation, password attacks, web testing and post-exploitation.
Foundations of ethical hacking: reconnaissance, scanning, exploitation and the legal side of testing.
Images, containers, volumes, networking and Docker Compose.
Two-month course on Amazon seller operations (Jun – Aug 2022).
Ameer helped our company handle a very important and business critical open source effort. Ameer's knowledge about the open source strategy including licensing, workflows, issues, discussions, etc. is very thorough and deep. He is also very meticulous and committed to the delivery timelines. All this without any reservations about his technical abilities as it was needed throughout the project. Very please with the delivery.
One of the greatest teacher of all time. He is very patient with me every time we have a lesson and he makes sure I understood the topic well before he moved on the next topic. I definitely recommend him, You will have no regrets if you choose him!
Thank you, Ameer for doing a very meticulous job to make our material ready for open source. Your expertise in this area is instrumental and we look forward to working with you as we go to market and acquire our initial clients.
Thank you, Ameer for going above and beyond. Your expertise in OSS implementation is very unique and key in the go-to-market strategy. Look forward to working with you in the future as well. All the best.
Got a wine dock, container working on unraid that I wasn’t even sure if it was possible because he did a lot of troubleshooting behind the scenes and it only took two sessions to get it working very glad he did
Ameer is always great to work with. He knows what he is doing and goes above and beyond to make sure the work is done the way you want it to be.
Amazing and quick service. Excellent communication and revisions. Slightly expensive but worth it.
Great to work with. Goes the extra mile to get the job done well.
Quoted word for word from my Fiverr and Upwork profiles. Usernames shortened for privacy.
Practical write-ups from real work: clusters, monitoring, hardening, open source and client work.
View all postsThe client hands me the code; this is everything I do after that: history audit, structure, GitHub SEO, licensing, commit rules, rulesets, security, workflows and launch.
Quorum maths, fencing, affinity rules, replication schedules and a calm 8 → 9 upgrade: the things I wish I'd known before I started.
Kannel, smppbox and KSMPPD only show a status page. Here's how I turned them into metrics, and the counter-reset bug that nearly made the graphs useless.
After 67 freelance orders, this is my routine for working on servers I didn't build and can't afford to break.
The steps I take on every fresh server before it serves a single request: users, SSH, firewall, updates, time and logs.
