cloudwarrior CloudWarrior, home

EN is the active language PL · Polish version of this page

The practice

Small unit. One standard.

Who does the work, how an engagement runs from first read to handover, and what sits in the toolbox behind it.

Start a conversation Request the 48-hour audit

The practice

A generated print plate: stacked ink bands, a halftone quarter, and a blue registration arc

CloudWarrior is an independent infrastructure and automation practice based in Poland and working across the EU. The work sits between infrastructure and product: the clusters, the pipelines, and the features that ride on them.

Where a project needs more hands or a different specialism, engineers come from a bench that shares one standard of work, or from a wider network built over a decade in the industry. Everyone on it has held production on call. Nobody learns the fundamentals on a client platform, and nothing is handed to whoever happens to be free.

An engagement opens with a written read of what is running and closes with a handover the team can operate from. In between, work arrives weekly and lands in the client repository: infrastructure, pipelines, and runbooks, each one legible to whoever inherits it.

Credentials

  • AWS Solutions Architect Professional
  • Azure Solutions Architect Expert
  • Google Cloud Professional Cloud Architect
  • Certified Kubernetes Administrator
  • HashiCorp Terraform Associate

Over a decade of infrastructure engineering across aviation, media, travel, and commerce.

How the work runs

  1. Remote-first, async by default.

    Written status, recorded demos, and decisions documented in the repository.

  2. Weekly shippable increments.

    Working software arrives every week, not as one handover at the end.

  3. Everything as code.

    Infrastructure, pipelines, and runbooks live in your repository, never in someone's head.

  4. Clean exit by design.

    CI green, deploys documented, handover complete. Your team operates without CloudWarrior afterwards.

Stack

Infrastructure as code

  • Terraform
  • Pulumi
  • Ansible

Delivery

  • GitHub Actions
  • GitLab CI
  • Azure DevOps

Containers

  • Kubernetes
  • AKS
  • EKS
  • GKE
  • Docker
  • Helm

Observability

  • Grafana
  • Prometheus
  • Loki
  • Alertmanager

Cloud

  • AWS
  • Azure
  • Google Cloud
  • DigitalOcean

Security and automation

  • Vault
  • Trivy
  • Falco
  • OPA
  • n8n

Where this goes next

Free 48-hour infrastructure audit

The form takes three answers. What comes back within 48 hours is a written read of the platform: where the spend concentrates, what fails first, and the order to fix it in. No call is required to receive it.

What comes back

  • Where the cloud spend concentrates, by service and by cause.
  • The failure modes that would bite first under load or on call.
  • A remediation order: what to fix now, what can wait, what to leave alone.
  • A straight no when the fit is wrong, with a name from the wider network instead.
Turnaround
Within 48 hours
Format
Written findings
Charge
None
Next step
Only if asked for

Request the audit

Where the findings land.

Used to place the platform in context.

Cost, reliability, release speed, on-call load. Two sentences is enough.

Answers are used to reply to this request and nothing else. No list, no sequence. Privacy.

Scripts are off, so this form cannot hand the request on. The same three answers work as plain mail: address, company, and what is going wrong right now. Write to pat@cloudwarrior.io.

Or write straight to pat@cloudwarrior.io.

Contact

Bench open · Remote across the EU