Issues that end the debate
Every finding comes with the details and a cause-and-effect chain, so it gets picked up — not argued about in next week’s meeting.
Istanbul, Türkiye · UTC+3 · EN / TR
Senior DevOps Engineer & R&D Team Lead @ Vendor Box
I build CI/CD, Kubernetes platforms and monitoring that run themselves — secure by default, written down as code, and quiet at 3 a.m.
I’d rather describe a system than build it by hand. Infrastructure is code, every change goes through a pull request, and a good system tells you it’s broken before anyone else does — then fixes what it can on its own.
I’ve worked in DevOps and DevSecOps since 2019, including two years of security-focused QA, across Kubernetes operations, cloud platforms, MLOps and RAG systems. Today I’m a Senior DevOps Engineer and the R&D Team Lead at Vendor Box, and I consult for İVEN Bilişim. After hours I build minderhq, a self-hosted AI platform I first imagined in 2023 while working on Monitra. A home lab tests all of it and feeds this site’s lab journal.
I wrote my first website in Notepad for a free 10 MB host while still in primary education, Pascal and cybersecurity forums in high school, assembly at university, where I also ran the department’s lab. A guitar pulled me into sound recording and a studio in Kadıköy; one good-sounding digital processor pulled me back to software. I taught myself Linux, which led me to Hackerspace Istanbul; later I helped found two university labs, Sparkgo and BAU Future Lab, an IoT lab funded with Intel’s support.
Now
Run LLMs, RAG and knowledge graphs on your own hardware. Plugins, a marketplace and one installer.
Infrastructure as codeOne Proxmox node, 11 containers — 8 services and 3 CI runners — nightly self-updates behind snapshots, backups and phone alerts, all from one repo.
This siteBilingual and static, built with Astro. Every morning an n8n workflow at home summarizes the news with GLM and commits it here.
Consulting and hands-on delivery, in whatever shape fits: a one-off audit, a fixed-scope build or ongoing support — held to the same standards as the production systems I run.
How I work
Every finding comes with the details and a cause-and-effect chain, so it gets picked up — not argued about in next week’s meeting.
What I set up is written down as code and reviewed, so you can rebuild it without me.
I take things away before I add: fewer moving parts, easier installs, updates that apply themselves.
Pipelines with security built in: GitLab CI or GitHub Actions on your own runners, signed images, a private registry with vulnerability scans.
K3s or Kubernetes with Argo CD and Helm, on Proxmox or in the cloud — a platform your team can ship to without asking anyone.
Prometheus, Grafana and alerts that matter, straight to your phone — so you hear about problems before your users do.
LLMs and RAG on your own hardware, with answers that cite their sources — plus n8n automations that keep your data in-house.
A server that runs itself: Proxmox, backups, UPS and remote access, defined as code.
Remote
Two roles at once. As Senior DevOps Engineer I take care of the platform’s infrastructure and delivery; as R&D Team Lead I lead the team that decides what we build next.
External · remote · Technoscope, Mersin University Technopark
Alongside Vendor Box: I build software and advise on secure, automated delivery for an R&D company working in software, chemistry and recycling.
Own product · idea since 2023
A self-hosted, local-first AI platform: LLMs, RAG pipelines and knowledge graphs on your own hardware, extended through a public plugin ecosystem. The idea took shape in 2023, while I was working on MLOps and RAG for Monitra; in 2026 it became a product — and an R&D project I lead as its technical architect and RAG core engineer.
Istanbul · hybrid
Took over Monitorpark, a product whose old version had been left unmaintained, and rebuilt it into a much leaner one that is far easier to install and keeps itself up to date.
Informatics Valley, Gebze · hybrid
Built a secure CI/CD platform and the DevSecOps practices around it.
Informatics Valley, Gebze · hybrid
Test automation with Selenium and JMeter, DevSecOps-oriented security testing, and test environments on Jenkins, Docker and Kubernetes.
Istanbul
My first DevOps role, at a time when DevSecOps was barely a job title — which made me the friendly nightmare of the DevOps and R&D teams. My issues came with every detail and a cause-and-effect chain that left nothing to argue about, so teams picked them up instead of debating them in weekly meetings. Product quality and process quality both went up.
Freelance · hybrid
Hardware projects with Arduino, Raspberry Pi, Linux and Python — and the schedules that kept interdisciplinary projects on track.
Long before pipelines and clusters there was Notepad, a guitar and a lot of labs: a vocational high school’s, a university lab I ran, a recording studio, Linux learned from online communities, a hackerspace, and two labs I helped found. They taught me to build, to lead a team, and to explain technical work to people who don’t do it.
Primary education · HTML · Notepad
My first website was hand-written HTML, typed in Notepad and uploaded to the free 10 MB of hosting cjb.net gave away back then.
until 2007 · Electronics · Pascal · security forums
I wrote Pascal, spent hours on cybersecurity forums trying to learn whatever I could, picked up the guitar, and sat in on the senior classes’ lab lessons of my own accord, helping the older students along the way — the earliest training of my R&D instincts and hands-on skills, under my lab teacher Oğuz Kaan Bozkuş.
2007 — 2011 · Electronics & communication · lab lead
I was an evening-programme student, but my days started early in the lab: as assistant to our department coordinator, Uğur Kesen, and the person responsible for the department’s laboratory, I set up the labs and supported the instructors teaching there. This is also where I learned assembly.
2009 — 2011 · Sound recording · repairs
The guitar pulled me into recording technology. In parallel with university — sometimes at the expense of my evening classes — I worked at a music studio in Kadıköy. I helped musicians through both kinds of sessions: multitrack recordings, with a microphone on every instrument, and live takes of the whole band captured by microphones set up in the middle of the room. I also repaired the studio’s gear.
Until then I had lived by Serdar Öztop’s line, “digital should have its limits.” Then a digital processor landed on my bench that simply sounded good — and I realized it was time to leave that line behind and focus on software.
2011 — 2013 · Pardus 2011 · online communities
After the studio I turned to Linux and set out to learn it on my own. It started with a Pardus 2011 DVD, mailed out for the price of shipping — the beginning of my focus on Linux. From there I joined online communities, asked questions and dug through everything I could find. That search is what led me to Hackerspace Istanbul.
2013 — 2015 · Linux · cybersecurity · PCB design
A two-way exchange. The community deepened my Linux and took the security I had picked up on forums much further; in return I helped with PCB design and with improving their hackathon projects. I attended their trainings and later took on roles in running them.
2013 — 2019 · Electrical & electronics · graduate labs
My degree years were lab years. Rather than go home and come back early for lab work before classes, I often just stayed in the lab. At night, to keep busy, I sat in on master’s courses and helped the lecturers run the hands-on sessions of their big data and Linux classes for graduate students. Another lab, another reason to stay.
2015 — 2018 · First lab · funded by the university
The first lab I helped found, funded by Bahçeşehir University. Sparkgo gave student science and technology projects a stage the school could proudly show — and taught me how to tell the story of technical work.
2015 — 2018 · IoT lab · funded with Intel’s support
Next came BAU Future Lab, funded with Intel’s support — and this was the hands-on one. We built real IoT projects on embedded boards, sensors and Linux, and learned what it takes to make connected devices work outside a demo.
Education & training
One Proxmox node, a NAS, a Raspberry Pi and a UPS. Everything is defined as code, updates itself every night and rolls itself back when something breaks.
Inside the lab →A pipeline that needs fixing, a platform to build, or a second pair of eyes on your infrastructure — tell me what you are working on.
hello@usevimli.devBased in Istanbul · UTC+3 · works remotely English · Turkish