CASE STUDIES

Concrete results.
Not promises.

Every project is a real challenge solved with measurable impact.

Vertical:

Technology:

DEVOPS & CLOUD

01 SOFTWARE HOUSE · POLAND · 60 APPLICATIONS

APACHE DOCKER → KUBERNETES GITOPS

BEFORE

~50% Docker, ~50% Apache2
Manual and semi-automated deploys
Rollback via SSH + backup
Scattered configuration
No environment separation

AFTER

RKE2: separate cluster per environment
GitOps with ArgoCD
Rollback with a single Git commit
Universal Helm Chart
Full DEV/RC/PROD repeatability

READ ARTICLE →

60 APPLICATIONS
MIGRATED

-87% DOCKER IMAGE
SIZE REDUCTION

~30s BUILD TIME
(FROM ~6 MINUTES)

02 SOFTWARE HOUSE · POLAND · 200 vCPU · 320 GB RAM

GITLAB DOCKER → KUBERNETES EXECUTOR

BEFORE

5 Docker runner hosts
Pipeline saturates 100% CPU: 8-9x/week
Runner crash: ~3x/week
Job slowdown: daily
cgroups limits don't isolate

AFTER

Kubernetes executor (RKE2)
ResourceQuota per project
Shell-operator for per-service limits
0 runner crashes/month
40-60% faster pipelines

READ ARTICLE →

40-60% FASTER
PIPELINES

0 RUNNER CRASHES
PER MONTH

0 MANUAL
INTERVENTIONS

03 VEEAM · BACKUP · DISASTER RECOVERY

SCENTRALIZOWANY BACKUP & DR → MULTI-HYPERVISOR

Single Veeam ecosystem for three hypervisors (VMware, Hyper-V, oVirt) with Azure offsite and ransomware protection.

BEFORE

Three different backup approaches
RPO >24h, no consistency
No offsite (3-2-1 rule ✗)
No ransomware protection
Recovery: hours

AFTER

Single Veeam ecosystem
RPO from 1h to 4h per workload
Azure Blob + Object Lock
Immutable backups
Instant Recovery: minutes

READ CASE STUDY →

3-2-1 RULE
FULFILLED

<15 min INSTANT
RECOVERY

100% IMMUTABILITY

Have a similar challenge?

BOOK A FREE CALL →