Cloud, security and access
I configure GCP, accounts, permissions, email, DNS, basic security policies and access hygiene.
> ./start_session.sh --profile cloudvance
You run the business. I make sure hardware, email, cloud and the web do their job without drama.
> section.load
I operate as an independent IT contractor. Through Cloudvance I deliver projects around Google Cloud Platform, Terraform and infrastructure automation.
Alongside larger contracts, I also take on focused work for companies that need reliable IT, a website, or a rescue job after a previous vendor.
I work project by project: define the scope, deliver the result and leave behind something maintainable. No extra systems just to make things look more complicated.
> section.load
This is not a package shop. These are the areas where I can actually help after a short conversation and a sane scope.
I configure GCP, accounts, permissions, email, DNS, basic security policies and access hygiene.
I build fast websites and landing pages on clean code. No heavy builders when a light, stable site is enough.
I fix old websites, domains, servers, SSL, forms, performance problems and half-finished work.
I select hardware, set up networks, backups and basic work environments so the team does not lose time.
I write pipelines, organize repositories, CI/CD migrations and small automations that remove manual work.
I help decide what to buy, remove, fix, or leave alone because it still works.
> section.load
Cloudvance is the business layer of this site: contracts, invoices, responsibility and a clear point of contact. You still talk to the person who does the work.
> section.load
Not every project is public, but these examples show the range: web, infrastructure, real-time data and internal tools.

Real-time air traffic visualization system: ADS-B data, flight track rendering, backend and presentation layer.

Modern implementation of an air traffic tracking application based on .NET 10 and a newer service architecture.
> section.load
Client work is less about fireworks and more about readability, contact, reliability and search visibility.
> section.load
Short and practical. First diagnosis, then a concrete decision, then implementation and handover.
step.01
I check what actually hurts and what is only a symptom. Without that, budget burns fast.
step.02
We decide what gets done now, what does not, and what “working” means.
step.03
I ship a concrete change: website, configuration, migration, fix or recovery plan.
step.04
I leave access, short notes and order behind, so the topic is not trapped in one person’s memory.
> section.load
The easiest way is to send a short email with the problem. If it is urgent, call.