Not a Startup Experiment. A Personal Survival Tool.
SQLOZ did not emerge from a boardroom asking how to "disrupt" developer tooling. It came from the raw, unglamorous reality of living with production databases for 30 years - typing DELETE with trembling hands at 3:00 AM on a customer-facing cluster, struggling to untangle complex deadlock graphs from a flat, monochrome processlist, and jumping between four different half-baked database clients just to complete a single day's work.
An Unlikely Origin: Forestry Engineering and Holistic Systems
This engineering journey began in an unconventional discipline: Forestry Engineering.
It was there that the foundational mindset took root - learning to see large-scale systems not as isolated trees, but as complex living ecosystems.
Decades later, that same ecological intuition proved invaluable when diagnosing high-concurrency database clusters. A stalled connection or an escalating lock is never an isolated symptom.
The Fusion of Engineering and Visual Craftsmanship
Following systems ecology, the path returned to deep software roots at Anadolu University, completing rigorous curricula in Computer Programming followed by Web Design & Coding.
"Three universities, three perspectives: one taught systemic thinking, the others imparted technical rigor and visual craftsmanship."
The Frustration with Fragmented Tools
- Heavy Java/Electron memory hogs: Tools consuming 2GB of RAM just to view a single table.
- Fragmented enterprise lock-ins: Schema comparison locked in one expensive tool, live PII masking behind enterprise sales quotes.
- Alien user experiences: Cross-platform UI toolkits that ignore macOS human interface conventions.
Peace of Mind for Fellow Database Engineers
The true purpose was deeply human: to ensure no fellow DBA ever endures the sleepless panic attacks, the terrifying unconstrained queries, or the dread of locked production tables.