DevOps / Linux / Automation

I keep Linux systems
reliable in production.

I help teams ship changes safely and keep the infrastructure behind them understandable. DevOps and Linux engineering from Brno, backed by nine years of hands-on experience.

Available for selected projects

DevOps and Linux engineer based in Brno.

Portrait of Martin Baránek

I'm a DevOps engineer and Linux system administrator in Brno. I design, automate and operate infrastructure with Docker, Kubernetes and modern cloud platforms.

The aim is straightforward: a reliable route to production, systems people can understand, and fewer surprises after handover.

Experience
9+ years
Location
Brno, CZ
Languages
CS / EN / DE
Focus
DevOps / Linux

“Stay hungry. Stay foolish.”

Steve Jobs

“The biggest risk is not taking any risk.”

Mark Zuckerberg

DevOps, Linux
and automation.

I help teams build, ship and operate systems across four connected areas. The tools change; the goal stays the same: reliable production.

Cloud & Containers

Design and operate workloads from a hardened VM to production Kubernetes across cloud and on-prem environments.

AWS · Azure · GCP · Kubernetes · Docker · Proxmox

CI/CD & Automation

Create a repeatable route from commit to production with pipelines, infrastructure-as-code and GitOps.

GitLab CI · Terraform · Ansible · Argo CD · GitOps

Linux Operations

Harden, monitor and maintain Linux systems, databases, networking and the everyday operational reality around them.

Linux · Bash · MySQL · PostgreSQL · Monitoring · Security

Practical AI

Use AI where it removes real friction: internal workflows, useful context, retrieval and focused agents.

Claude · MCP · RAG · Agents · Anthropic SDK

My goal is simple:
make production
predictable.

I want teams to ship changes with confidence and understand the Linux systems they own. That means clear CI/CD automation, useful monitoring, practical security and documentation that survives the handover.

Automate the repeatable

I use CI/CD and infrastructure-as-code to turn deployments into a clear process, not a collection of manual steps.

See problems early

Monitoring, hardening and practical defaults make risk visible before it becomes an outage.

Keep knowledge with the team

I document decisions and ownership so the system remains understandable and maintainable after I hand it over.

Exploded processor assembly A motherboard, processor substrate, silicon die and heat spreader separated into layers. Each working principle activates one layer. MB / CORE REV 09