DevOps consultancy for speed, stability and scale

Ship faster and get predictable production. As a freelance senior DevOps consultant, I help teams deploy with confidence — from Kubernetes to CI/CD, Terraform (IaC) and observability. Enterprise experience, without enterprise overhead.

Scroll

The problems I solve

DevOps is rarely a single tool. It’s the whole system: process, platform and automation. These are the situations I’m often brought in for:

  • Every release feels risky: deployments are partly manual or fragile; rollbacks take time.
  • Slow time-to-market: pipelines, tests and environments slow engineers down.
  • No (or late) visibility: monitoring/logging is fragmented; you hear issues from customers.
  • Scaling & cost surprises: growth creates bottlenecks or unpredictable cloud bills.
  • Security & compliance pressure: access, secrets and audits feel like guesswork.

What you get

  • Stable infrastructure: a robust cloud/server foundation with a focus on high availability.
  • Automated CI/CD pipeline: from commit to deploy as automated as possible — faster releases with less manual work and fewer mistakes.
  • Visibility & monitoring: monitoring, logging and alerting (e.g., Grafana/Prometheus) so you see what’s happening and why.
  • Security built in: DevSecOps where it makes sense — security checks in the pipeline, solid IAM and safe secrets handling.
  • Team enablement: I work with your team and help improvements stick — through explanations, demos and coaching.
  • Documentation & handover: clear documentation and a handover so your team can keep running without depending on me.

How I help teams

CI/CD & release automation

I build pipelines that fit your team: build, test, security checks and deploy. Think GitHub Actions, GitLab CI or Jenkins, and GitOps with Argo CD or Flux. Less manual work, faster feedback, and a release process you can trust.

Kubernetes & platform engineering

From first cluster to production platform: architecture, networking, RBAC and policies (like Pod Security and network policies). I also help with Helm/Kustomize, autoscaling, and building an internal developer platform so engineers can work more self-service. CKAD certified; CKA/CKS in progress.

Observability & reliability (SRE)

I set up monitoring, logging and alerting (e.g., Prometheus/VictoriaMetrics, Grafana, Loki/ELK) and help with runbooks and incident practices. Goal: faster root cause analysis and fewer recurring fires.

Cloud & infrastructure as code

On AWS, Azure, GCP or on-prem: I help migrate, standardize and manage with IaC (Terraform/Ansible). Including cost control, secure access and a setup that stays reproducible and extensible.

My approach

Before I pick tools or architecture, I want to understand the goal: what the business needs, where things break technically, and what your team can realistically maintain.

I work with short feedback loops and no black boxes. Kubernetes is powerful, but it’s not always the answer — I make choices that fit your context and long-term maintainability.

A typical engagement looks like this:

  • Discovery & roadmap: identify bottlenecks, ship quick wins, and create a plan aligned with your goals.
  • Implementation in sprints: iterate, measure and adjust — no big-bang changes unless necessary.
  • Collaboration & knowledge sharing: I work embedded with your team and explain what I’m doing and why.
  • Handover & continuity: documentation, handover and (if you want) a periodic health check afterwards.

I’m direct — even when it’s not what you want to hear. Quality takes time, and I won’t cut corners for an arbitrary deadline.

Tech stack & tools

Tools are a means, not a goal. But if you want a quick scan of what I often work with:

  • Cloud: AWS, Azure, GCP, DigitalOcean, Hetzner, on-prem/private cloud.
  • Containers: Kubernetes, Docker, OpenShift, Helm/Kustomize, Talos Linux.
  • IaC & automation: Terraform, Ansible.
  • CI/CD & GitOps: GitLab CI, GitHub Actions, Jenkins, Argo CD, Flux CD.
  • Observability: Prometheus/VictoriaMetrics, Grafana, Alertmanager, Loki/VictoriaLogs.
  • Identity & security: IAM/RBAC, Keycloak/DEX, secrets handling (vault/secret stores).

Where I've worked

I've built and managed infrastructure for organizations including the Dutch National Police, Schiphol Airport, and Logius — often in environments with high requirements for availability, security and change control.

See my LinkedIn for a complete overview, or view Work & Results for concrete examples.

Detailed overview & CV

Want a full overview of my skills, project experience and certifications? Download my CV (PDF), or check LinkedIn for recommendations.

What clients say

  1. Jorijn combines thorough, in-depth technical knowledge with a clear understanding of project goals and what working Cloud Native truly means. That makes him the senior in the team on multiple fronts. We can rely on him: even when we provide little information, the result is good, or we get exactly the feedback we need. One of the important applications in our service portfolio used to cause a fair amount of maintenance overhead and didn't always run well. Since he took on the deployment including the CI/CD pipeline, the application runs stably and its management — including life-cycle management — is almost fully automated and barely takes any time anymore.
    Albert Witteveen IT Architect & Product Manager IDDI Platforms, Dutch National Police
  2. Having someone like Jorijn on your team makes things easier on every level. He has a natural authority among colleagues — rooted in both his skills and his calm personality. Refinements, reviews and plannings were always thoroughly prepared. Another standout quality: his ability to make complex topics understandable for people from other disciplines.
    Richard Slot Scrum Master, Logius (MijnOverheid)
  3. An extremely pleasant collaboration on all fronts. Jorijn is exceptionally skilled and works in a well-organized manner. What stands out is that whenever an answer was needed, he was often the one with a well-substantiated response backed by documentation. At one point there was an outage between an API and a service managed by another department. He was the one who demonstrated that the issue was at the network level, not in the API under our management — which ultimately led to the problem being traced and resolved.
    Sander Krause Senior PHP Developer, Schiphol
  4. Jorijn and I have collaborated on multiple projects, and his seniority and eagerness to learn impress me every time. He readily takes end-to-end ownership of the entire technology stack, which quickly makes him the obvious point of contact — for both the business and colleagues. Technology is truly his passion: I've often seen him pick up and apply new techniques in a short time, and that's directly reflected in both the breadth and depth of his knowledge.
    Alex Vernikov Developer & DevOps Engineer, Kieskeurig.nl & Logius (MijnOverheid)

Is this a fit?

This is a good fit if:

  • You want structural improvements (not just quick patches).
  • Your team is open to better ways of working and I can collaborate closely with them.
  • You’re building a platform that needs to scale and you want to lay a solid foundation now.
  • You want a pragmatic expert who can think strategically and also build.
  • Quality, collaboration and calm operations matter more than the lowest price.

This is probably not a fit if:

  • You primarily need a feature developer (my focus is platform, infra and delivery).
  • You expect a large consultancy team — you work with me as an independent consultant embedded in your team.
  • You don’t want to involve your team in change or handover.
  • You only want a quick emergency fix without addressing root causes.

FAQ about DevOps consultancy

What’s the scope of a DevOps engagement?

It depends on your situation. Sometimes it’s one concrete issue (e.g., unstable deployments); sometimes it’s a broader track (CI/CD + infra + observability). I often start with a short assessment and quick wins, then we align on scope. I always make it explicit: what we do, what we don’t, and what the outcome is.

How do we collaborate and communicate?

I prefer working embedded with your team: short lines, transparent, no surprises. Typically that means a kickoff, regular updates (e.g., weekly), and coordination in your tools (Slack/Teams/Jira). You can always see what I’m doing and why.

How do you handle security and access to our systems?

Security is a baseline requirement. I work with least privilege, separate accounts where possible, and temporary access when feasible. I don’t share secrets via email or chat; we use a password manager or a secret store. I document changes so you can always audit what happened.

What happens after the project ends?

My goal is for your team to run independently. I deliver documentation, do a handover (and training if needed), and make sure knowledge doesn’t live only in my head. If you want, I can stay available for periodic health checks or on-demand support.

What about rates and budget control?

I work at a market-rate senior freelance rate. Upfront we align on scope, priorities and communication so you stay in control of costs. That can be hour/day based, and for well-scoped work also fixed price. If budget is a hard constraint, we adjust scope accordingly.