PL EN

DevOps · Backend · Automation

Infrastructure that won’t wake you up at 3 a.m.

I design, automate and run the environments your product lives on — from the first Dockerfile to production monitoring. I also write the code that ties it all together.

Describe your project Code on GitHub
pipeline — productionlive
  1. $ git push origin main
  2. → pipeline #482 started
  3. ✓ lint & test12.4s
  4. ✓ build image41.0s
  5. ✓ trivy scan0 critical
  6. ✓ push ghcr.iosha256:9f2c…
  7. ✓ deploy (rolling)3/3 healthy
  8. ✓ smoke testspassed
  9. ● production @ v2.14.0 — 0 downtime
Model
one-person lab
Location
Poland · remote
Reply
usually within 1 business day
Status
taking on work

01 / Services

What I do

Five areas, one rule: everything I build can be recreated from a repository and understood without me.

01 CI/CD Pipelines you can trust

Tests, builds and deployments in GitHub Actions or GitLab CI. Every merge reaches production predictably, and a rollback is one command, not a midnight rescue mission.

  • GitHub Actions
  • GitLab CI
  • Argo CD
02 Containers Docker and Kubernetes, no magic

Minimal multi-stage images, running as non-root, scanned for vulnerabilities. Compose where it's enough, Kubernetes where it makes sense.

  • Docker
  • Compose
  • Kubernetes
  • Helm
03 Infrastructure Servers as code

VPS, AWS or Hetzner — described in Terraform and Ansible. You rebuild the environment from a repository in minutes, not from one person's memory.

  • Terraform
  • Ansible
  • Linux
  • Nginx
04 Monitoring See the problem before your customer does

Metrics, logs and alerts that actually mean something. Plus server hardening, TLS and backups — with regularly tested restores.

  • Prometheus
  • Grafana
  • Loki
  • Trivy
05 Development Code that holds it together

APIs and backend services, integrations between systems, scripts and internal tools that take repetitive manual work off your team.

  • Node.js
  • Python
  • Go
  • PostgreSQL
DockerKubernetesTerraformAnsibleGitHub ActionsGitLab CINginxPrometheusGrafanaLinuxPostgreSQLNode.jsPythonGo

02 / Protocol

How I work

  1. 01

    Discovery

    A conversation and a review of where things stand. You get a list of risks and priorities — even if we stop there.

  2. 02

    Plan

    Concrete scope, milestones and a quote. You know what you pay for and when you get it.

  3. 03

    Delivery

    Small, reversible steps. Everything in the repository, every change visible in history.

  4. 04

    Handover

    Documentation, runbooks and a short training. The infrastructure stays yours, not mine.

Lab rules

  • R1Everything as code
  • R2Least privilege, always
  • R3Docs are part of the delivery
  • R4No vendor lock-in
  • R5Boring tech wherever possible

03 / Work

Selected work

WL-01 Online store · home furnishing Case study

From manual deploys to a pipeline in six weeks

The app ran on a single server and was deployed by hand over FTP — usually on a Friday evening. No tested backups, no monitoring; every update was a gamble.

Problem

One person knew the server. A deploy took about 40 minutes and ended with manually checking whether it “works”. Customers were the ones reporting outages.

Solution

Containerised the app (multi-stage, non-root images) and built a GitHub Actions pipeline: tests → build → Trivy scan → GHCR registry → deploy with health check and automatic rollback. Staging and production described in Terraform and Ansible. Prometheus, Grafana and chat alerts. Nightly database backups with a weekly restore test.

Outcome

Deployments became a routine daytime task, and the team got documentation and runbooks to run the environment on their own.

deploy time
40 → 6 min
deploys per week
1 → 15+
rollback
< 2 min
  • Docker
  • GitHub Actions
  • Trivy
  • Terraform
  • Ansible
  • Prometheus
  • Grafana
WL-02 Reserved slot

The next project lands here

Work in progress. The write-up will appear once it's finished and the client agrees.

04 / FAQ

Frequently asked questions

Q1

How much does setting up CI/CD or containerising an app cost?

It depends on the starting point and scope. After a short call and a review of your current setup you get a quote for a specific milestone — with a clearly defined outcome — or a rate for ongoing support. You can indicate a budget range in the form.

Q2

Do you work remotely?

Yes. I work remotely with companies in Poland and abroad. Access to servers and repositories goes through accounts you can revoke at any time — nothing stays tied to me.

Q3

What infrastructure do you work with?

Linux VPS and dedicated servers (e.g. Hetzner, OVH), AWS, Docker and Docker Compose, Kubernetes, GitHub Actions and GitLab CI, Terraform and Ansible, nginx, Prometheus and Grafana.

Q4

Can you take over maintenance of existing systems?

Yes. I start by reviewing and documenting the current state, then clean things up in small, reversible steps — no downtime and no rewrite from scratch.

Q5

What do I get when the project is finished?

All configuration as code in your repository, documentation, runbooks for common incidents and a short training for your team. The infrastructure is fully yours — no dependency on a single person or vendor.

Q6

Do you also build applications, not just infrastructure?

Yes — APIs and backend services (Node.js, Python, Go), integrations between systems and internal tools. Often it is the code that ties the automation together.

05 / Contact

Tell me what needs building.

A few sentences are enough. I'll reply with questions or a proposal for a short call.

Rather see the code first? Repositories, tools and experiments from the lab. github.com/Pioti2252

OFFLINE The contact form is temporarily disabled — it will be back soon. In the meantime, have a look at my GitHub. github.com/Pioti2252

What is it about
0 / 5000

The data controller is whiteitlab. Your data is used only to reply to your inquiry and is not shared with anyone. You can request access, correction or deletion at any time.