From zero
to the cloud.
Left Türkiye at 17. Built a life in a new country through technology. Then started building the cloud itself.
Where it all began.
I was fascinated by computers — by creating something with nothing more than an idea and a keyboard.
I chose a technical high school and studied database systems. At 16 I was interning at Metro Istanbul, writing C# for the ERP team and tuning SQL queries.
I didn't know where the path would lead. I knew I wanted to build things.
17. A different world.
At 17, I made a decision that changed the direction of my life. I left.
A different country, a different culture, a different language. Everything familiar was suddenly somewhere behind me.
I began with preparatory studies at Warsaw University of Technology. That move was more than a change of location. It was the beginning of independence.
Learning to create.
Programming became a way of thinking.
I studied Computer Science at the Polish-Japanese Academy of Information Technology. But I wanted more than assignments — I wanted to make things people could actually use.
Databases, backends, web apps, mobile apps, datacenter floors. Every problem became something I could break down.
From code to business.
I co-founded Technox, a hosting and datacenter services platform.
I was no longer just writing code. I built the customer-facing site, WHMCS plugins and the automation behind them — and learned what it means to own a product.
The professional journey.
Five years of enterprise software, from IT analyst to Software Engineer.
SaaS products, frontend engineering, performance work, codebase modernization across teams.
These years taught me how software is built at scale.
Building something of my own.
I didn't only want to work with existing platforms. I wanted to build one.
TheyCloud is a private-first cloud: compute, networking, storage, hosting and billing behind one control plane, hosted in the EU. Designed and built from the ground up. Here is a tour.
Inside the perimeter.
Every workload starts inside the perimeter.
Compute launches into a private VPC by default. No public address is assigned, so public access is something you add on purpose, not something you subtract with firewall rules.
Cells and Cloudlets.
Light containers or full virtual machines, one API.
A Cell is an LXC container: quick to start, sharing the host kernel. A Cloudlet is a VM with its own kernel and full isolation. Both boot into the same private network, and snapshots make a rebuild routine.
Open one route.
Publish exactly one service, on one hostname.
Public access is additive. A named TAP endpoint opens a single route to a single service, with a certificate on a hostname you own. To close it, delete the endpoint.
Blocks and vaults.
Disks for running services, vaults for everything that outlives them.
Block volumes attach to instances. Object vaults speak the S3 API, so existing tools work unchanged. Snapshots and backup policies attach to the resource and restore into new ones.
Ship an app.
Deploy from the same account that holds your infrastructure.
Certificates are issued and renewed for you, and edge delivery sits in front of the same origins. A site that outgrows hosting adds compute or storage instead of migrating. This page runs on it.
See what you run.
An alert points at the resource you would act on.
Health and utilisation are reported against the same identifiers the API uses. Team roles scope who can create, change or destroy infrastructure.
One ledger. One API.
Finance and engineering read the same ledger.
Usage is attributed per resource, on hourly or monthly terms. Everything in the console is the same REST API you can script, plus a CLI.
The story continues.
Today I work as a DevOps Engineer at Pegasystems.
AWS, Terraform, Kubernetes, developer platforms. And the same curiosity that started in a database class in Istanbul.
I still want to understand how things work. I still want to build better systems.