aalgo.

Your cluster is installed.
Now someone has to run it.

Creating a Kubernetes cluster takes an afternoon. Keeping it upgraded, secure, observable and affordable is the hard part, and most teams have nobody who owns it. aalgo takes care of that day-2 work, on the cloud you already use or a European one.

See the services What day-2 covers
24/7 supportUpgradesSecurity & complianceObservability CostGitOpsArgo CD · FluxPrometheus · Grafana KyvernoVeleroOpenCostLLMs on Kubernetes

Three ways to work together

Most clients start with an audit. You get a clear report either way, and you decide what happens next.

02 · Remediation or migration

Project, fixed price

Fix what the audit found, or move your workloads onto a clean, GitOps-managed setup.

  • Hardening: policies, RBAC, secrets management
  • Catch-up upgrades, one supported version at a time
  • GitOps with Argo CD or Flux, standard deployment patterns
  • Migration to OVHcloud, Scaleway, Hetzner or IONOS

03 · Monthly operations

Retainer, per cluster or environment

We keep the platform current and healthy, so your engineers ship product.

  • Kubernetes and add-on upgrades, node patching
  • Monitoring and alerting, tuned to your services
  • Monthly cost and health report
  • 24/7 support and incident response, with defined response times

Support runs 24/7, every day of the year, with written response times by severity. When something breaks at 3 a.m., someone who knows your cluster answers.

What day-2 means

The work that starts after kubectl get nodes works, and never really stops.

Upgrades

Kubernetes ships about three minor releases a year, each supported for roughly a year. Fall behind and every upgrade gets riskier.

  • Planned upgrade calendar per cluster
  • Deprecated-API and add-on compatibility checks before each step
  • Rehearsed on a non-production environment first

Security & compliance

Controls that hold up, and the evidence your auditor asks for.

  • RBAC, network policies, Kyverno admission policies
  • Image scanning, secrets management, audit logs
  • Evidence supporting ISO 27001, SOC 2, NIS2 and DORA work

Observability & incidents

Know before your users do, and learn something from every incident.

  • Prometheus, Grafana and centralised logs
  • Alerts tuned to fire when it matters, with runbooks
  • Incident summaries and written postmortems

Cost

Over-provisioned nodes and forgotten clusters are common. The savings often cover the fee.

  • Per-team and per-service cost with OpenCost
  • Right-sized requests, autoscaling with Karpenter or Cluster Autoscaler
  • Idle environments found and switched off

GitOps & delivery

One standard way to deploy, so developers stop asking how.

  • Argo CD or Flux, every change reviewed in git
  • Helm charts and CI pipelines with security gates
  • Pipelines that never hold cluster credentials

Backup & recovery

A restore you have tested is the only backup that counts.

  • Velero backups of resources and volumes
  • Restore drills on a schedule, with results written down
  • Clusters rebuildable from git if the worst happens

Who it's for

Teams that adopted Kubernetes but don't have someone who truly owns it.

Regulated & sovereignty-minded

European companies that need clusters on European providers such as OVHcloud, Scaleway, Hetzner or IONOS, with compliance evidence to match.

Scale-ups without a platform team

Roughly 20 to 200 engineers, growing fast, with infrastructure handled "by whoever has time".

On-prem & hybrid

Clusters in your own data centre, or split between it and the cloud. Harder work, and we like it.

How we work

Standard, open tooling and a lot of automation, so you get senior attention without paying for busywork.

Open source, no lock-in

Argo CD, Flux, Prometheus, Grafana, Kyverno, Velero, OpenCost. If we part ways, everything stays yours and keeps working.

One standard setup

Every client runs on the same tested templates, adapted to you. Fewer surprises, faster fixes.

AI-assisted operations

Automated analysis of manifests and cluster config, upgrade-impact checks, incident summaries from logs, draft postmortems. Always reviewed by a human.

Honest advice

Some workloads don't need Kubernetes. If a simpler managed platform fits you better, we'll tell you.

LLMs on your platform

The same discipline applied to language models: they run as first-class, observable services of your cluster.

Self-hosted models

Open models on your own GPUs when data must stay in-house or volume makes APIs expensive.

  • vLLM or Ollama, deployed with Helm and GitOps
  • GPU node pools, scheduling and quotas
  • OpenAI-compatible endpoints your apps already speak

API-based models

Claude, OpenAI and others, behind your own interfaces so you can switch.

  • Translation, classification and moderation pipelines
  • Queues and workers, so a slow model never blocks a request
  • Budgets, caching and rate limits so the bill stays predictable

Measured

Latency, throughput, token cost and errors on the same dashboards as everything else.

  • Evaluation sets and regression checks before each change
  • Guardrails and human review where it matters

Recent work

A multilingual marketplace, built from scratch and run on Kubernetes, with LLM workers at its core.

  • Kubernetes on DigitalOcean, Istio gateway, Helm charts published as OCI packages
  • Argo CD GitOps across separate app, staff and platform projects; infrastructure in OpenTofu
  • RabbitMQ workers calling an LLM to translate content into seven languages and classify listings
  • N-replica services with rolling releases, durable queues and idempotent consumers
  • CI with tests, IaC security scans and image checks; delivery with AI coding agents under review

Start with an audit

A fixed-price review of your clusters, with a prioritised report you keep whatever you decide next. aalgo works with in-house teams, scale-ups and regulated companies across Europe.