Service · Software development

Hire a DevOps developer with team backup.

A DevOps engineer or consultant who gets your CI/CD, infrastructure as code and cloud platform in order, with a fellow senior behind the scenes for review and continuity. A dedicated specialist from our Dutch team, not a loose freelancer you have to hope hands over the pipeline keys properly.

Not a freelance script kiddie. A DevOps consultant with a safety net.

When you're looking for a DevOps engineer or consultant, the first reflex is often a freelancer via a platform or recruiter. Quickly available, experienced on paper, done. Until you discover that the pipeline runs on a personal GitHub account, the Terraform state sits in a Dropbox folder, and nobody knows what happens if that one engineer becomes unreachable. At that point, the cloud bill explodes, the deployment breaks, or worse: the production database is only accessible via a personal SSH key that nobody can rotate.

We provide a DevOps developer as part of our software development team: full-time on your project, but with peer review on every infrastructure change, a replaceable position within the team, and a contract that clearly settles ownership of pipelines, IaC and keys. What we build is transferable by design — all infrastructure in Terraform or similar IaC, all pipelines in code, all secrets in a vault, and no "Frank-only knowledge" buried in a runbook inside someone's head.

We work in the Netherlands, in the Dutch time zone, and you can choose to communicate in Dutch or English. When a production incident hits at four in the afternoon, you're not stuck in a ticket queue in another time zone — someone from our team is on standby. For on-call rotations and incident response, we set up structures that keep working even once we're gone.

The types of projects we're strongest in: cloud platforms on AWS, GCP and Azure, container platforms on Kubernetes or ECS, CI/CD pipelines for teams of five to fifty developers, observability stacks with Prometheus, Grafana and Datadog, and migration projects from on-prem or a legacy stack to a modern cloud environment. For pure security research or compliance-only projects, other specialists are a better fit — but for anything that runs, keeps running and changes in production, we're in our comfort zone.

What our DevOps engineers do.

Three main areas where a DevOps developer adds the most value for you — depending on where your organisation currently stands.

Area 01

CI/CD pipelines and automation

Building or redesigning the software delivery pipeline: from git push to production deploy, with automated tests, build caching, security scans and zero-downtime releases. We work with GitHub Actions, GitLab CI, Jenkins, CircleCI and ArgoCD for GitOps. This includes an environment strategy (dev, staging, production), feature flags, and rollback procedures that have actually been tested. Many teams bring us in because their current pipeline is slow, often red, or something nobody dares to touch any more. Often intertwined with a legacy software replacement project where the old release flow simply no longer fits the new architecture.

GitHub ActionsGitLab CIJenkinsCircleCIArgoCD
Area 02

Infrastructure as code and cloud platforms

The entire cloud infrastructure in code: VPCs, IAM, databases, queues, container clusters, secrets management. We work with Terraform, Pulumi, OpenTofu and CloudFormation, and where it makes sense we build a cloud-native platform on which your own developers can deploy services themselves. This includes a multi-environment setup, drift detection, and modules your team can reuse. For teams that want their own internal developer platform (IDP) — often because manually setting up new services is becoming too slow — we deliver platform engineering work based on Backstage, Crossplane or a custom abstraction.

TerraformPulumiOpenTofuAWS & GCP & AzureBackstage
Area 03

Containers, Kubernetes and observability

Container platforms on Docker, Kubernetes (EKS, GKE, AKS), ECS or a lighter option such as Nomad or Fly.io. This includes Helm charts, ingress configuration, a service mesh where it makes sense, and networking that will still be easy to explain in a few years' time. On top of that, the observability layer — logging, metrics, traces — with Prometheus, Grafana, Loki, Tempo, Datadog or New Relic. As standard, with SLOs per service, alert routing to the right on-call engineer, and dashboards that won't be forgotten in six months. For mid-market organisations, we often combine this with our Python or Node.js developers in a broader app development project.

KubernetesHelmPrometheusGrafanaDatadog

What you get at the end.

Not just an engineer for the duration of the project, but an infrastructure that can carry on independently — manageable by your own team or a successor.

IaC codebase

Infrastructure in Terraform or Pulumi, in your own Git repository, with state in a remote backend that you control.

Pipeline as code

All CI/CD flows as code in your repository, with secrets kept in a vault — no one-off configurations in a UI.

Runbook + on-call

Incident response procedures, alert routing, a post-mortem template and an on-call rotation your team can take over.

Architecture document

A document that explains the choices — why EKS and not ECS, why Loki and not Elasticsearch — and is useful for onboarding.

Optional management

Ongoing platform management, security patches, cost monitoring and minor further development through our application management service.

Three ways of working: choose what suits you.

How you engage a DevOps developer depends on what your team can do itself and how large the scope is.

Engagement model 01

Dedicated DevOps engineer

Our DevOps engineer works full-time on your project and integrates with your stand-ups, sprint rituals and product owner, while drawing on our team for reviews, sparring and knowledge sharing. You steer on output; we take care of continuity. Suitable when you don't yet have in-house DevOps capacity, or need extra firepower temporarily for a large migration or platform build.

Engagement model 02

DevOps consultant

When you mainly want advice and an initial setup — strategy, platform choice, a first IaC setup, first pipelines — and then want your own team to take over the work. Our consultant delivers an advisory document, the setup and knowledge transfer, with an open door for follow-up when you run into issues. If you are searching for a "DevOps consultant to hire", this is exactly what we deliver.

Engagement model 03

Team augmentation

Your own developers lead the project; our DevOps specialist works alongside them on the areas where your team has less experience — Kubernetes internals, a complex cloud migration, a service mesh implementation. We work in your repository, your rituals and your tooling, and build up the knowledge so your team can carry it on its own afterwards.

Engagement model 04

Senior lead or platform architect

A senior DevOps engineer or platform architect who also thinks along at a strategic level: cloud strategy, cost model, governance, security baseline and platform roadmap. Suitable for organisations that want to move from loose cloud resources to a structured platform, or where an earlier freelance route has left infrastructure that nobody dares to touch any more. We bring structure without rewriting the entire platform.

How an engagement works.

01Introduction→ 02Audit & match→ 03Build→ 04Handover

Introduction

A short session to pin down scope, your current cloud setup and the preferred way of working. We share examples of previous work and discuss seniority level.

Audit & engineer match

We carry out a short review of your current pipelines and infrastructure, and match a DevOps engineer to your project based on your cloud mix. You speak to the engineer yourself beforehand.

Sprints with reviews

Sprints with demos and reviews. Every infrastructure change or pipeline adjustment goes through peer review by a second senior — no pull request reaches main without a second pair of eyes.

Handover

At the end of the engagement, a structured handover to your own team or a successor, with a runbook, an architecture document and live walkthrough sessions.

Stack expertise of our DevOps team.

We work at mid-level to senior-lead level. No junior-only assignments — every engagement has at least one senior behind the review. The stack mix you choose depends on your project and existing cloud choice; the pills below are what we build with in practice.

CI/CD & automation
GitHub ActionsGitLab CIJenkinsCircleCIArgoCDFlux
IaC & cloud
TerraformPulumiOpenTofuCloudFormationAWSGCPAzure
Containers & observability
DockerKubernetesHelmIstioPrometheusGrafanaLokiDatadogNew Relic

When to choose DevOps, SRE or platform engineering.

In practice, these roles overlap. We have overlap with all three and choose based on what your situation needs — the breakdown below helps with that choice.

Discipline 01

DevOps engineer

Focus on CI/CD, build and deployment automation, infrastructure as code and the pipeline from git commit to production. Often the first role teams hire when release frequency needs to go up and manual steps need to go. We provide this role as a dedicated engineer or team augmentation.

Discipline 02

Site reliability engineer

Focus on reliability, SLOs, on-call, incident response and post-mortems. An SRE usually comes into the picture when a platform is already in place that needs to keep running and the business is complaining about outages or slow response times. We build SRE practices into our engagements as standard — no separate role needed for the mid-market.

Discipline 03

Platform engineer

Focus on developer experience: building an internal platform-as-a-product on which your own developers can deploy services without DevOps help. Often with Backstage, Crossplane or a custom abstraction. Suits growing organisations (10+ developers) where the DevOps bottleneck is becoming visible.

Discipline 04

Cloud architect

Focus on high-level cloud strategy: multi-region, cost model, vendor choice, governance, compliance. Often a shorter advisory engagement than a dedicated engineering role. Suitable when you are still at the bottom of the cloud learning curve or are considering a major migration.

In practice

Overlap is the norm

Most of our DevOps engineers touch all four disciplines during an engagement. What you need depends on your team size, cloud maturity and specific pain points — tell us in an initial conversation what you are looking for and we will match on what fits, not on job title.

When to hire full-time rather than a consultant

A permanent in-house DevOps hire

For organisations with daily production operations and a growing cloud footprint, a permanent in-house DevOps engineer usually pays off more than an ongoing consultant. We often help with the initial setup, a working baseline and knowledge transfer to your first own hire — after that we can stay on call for advice or peaks.

Why a DevOps team beats a lone freelancer.

For a short-running project with limited scope and little risk, a freelance DevOps engineer is perfectly fine. For anything that touches production, integrates with other systems or runs longer than a few sprints, we advise against it. The reasons are not abstract — we see them every month when a new client calls us in to clean up a freelance legacy.

Peer review on every infrastructure change. Every Terraform PR or pipeline change goes through review by a second senior engineer. A freelancer reviews themselves, or at best a developer on your team who knows just enough cloud to click "approve". The difference in reliability and cost control after six months is significant.

Replaceable within the team. When our engineer is ill or moves on to another assignment, they actively hand over to a colleague who already knows the codebase from reviews. With a freelancer, "two weeks of holiday" means "no deployments possible" — or worse, a second freelancer who has to reinvent everything.

Contractual certainty. You sign an agreement with Appfront B.V., not with an individual. That means IP rights are properly arranged, NDAs are enforceable, ownership of pipelines and IaC is contractually yours, and there is a liable party when something goes wrong. For projects involving production data or customer data, that is not a luxury.

Transferable infrastructure. We know the engagement will end at some point, so we set up the infrastructure with that handover in mind. Everything is in code, all keys sit in a vault, all accounts are held at organisation level, and there are no personal SSH keys in production. When the contract ends, nothing changes in who can do what, and you can start managing the platform independently straight away. For ongoing management, we often combine this with our enterprise software service or a clearly scoped application management contract.

Frequently asked questions.

What is the difference between a DevOps engineer, an SRE and a platform engineer?
In theory, these are three different roles: DevOps focuses on the delivery pipeline and automation, SRE on reliability and on-call, and platform engineering on developer experience and an internal platform-as-a-product. In practice, they overlap considerably at mid-market organisations, and our engineers touch on all three disciplines. Tell us about your pain points in an initial conversation and we'll match on substance, not on job title.
Do you work with a Dutch team or an EU team?
The DevOps team works from the Netherlands in the Dutch time zone. We can communicate in Dutch or English, whichever you prefer. There is no offshore handover, no half-day handover cycle during a production incident, and no language barriers in code reviews or stand-ups. For incidents during office hours, you won't be waiting in a ticket queue in another time zone.
Contract: fixed or flexible?
Both. For a dedicated engineer and team augmentation, we work with an hourly rate and a minimum weekly commitment, cancellable monthly. For consultancy engagements involving scoping and advice, we often agree a fixed-price arrangement based on deliverables. No long lock-ins and no mandatory minimum contract term of several years.
What happens if the DevOps engineer leaves halfway through?
That is exactly why we work with peer review and team backup. When someone on our team drops out or moves on, a second senior engineer is already familiar with the codebase through earlier reviews and can take over after a short handover. So you don't come to a standstill. With a freelancer in the same situation, you would, and we see this come up every month in new takeover projects.
How is knowledge transferred at the end?
A standard part of every engagement: a runbook with operational instructions, an architecture document explaining the choices and trade-offs, and walkthrough sessions with your own team or successor. Ideally these take place in the final sprints of the engagement, not on the very last day, otherwise there are always questions left that only our engineer can answer.
Do you help with choosing between AWS, GCP and Azure?
Yes. We have production experience with all three. The choice rarely depends on technical features, which have largely converged, and far more often on your existing contracts, audit requirements, regional requirements and which cloud your own team already knows. We give honest advice, even when that means you stay with your current cloud and we don't get to carry out a migration.
Do you also handle migrations from on-premises to the cloud, or between clouds?
Yes. A considerable share of our engagements are migrations: from on-premises to AWS or GCP, from a legacy PaaS to Kubernetes, or cross-cloud when a vendor choice no longer fits. We work in phases with a rollback plan at every stage, rather than a big-bang cutover. This is often combined with a broader legacy replacement project.
How is the price determined?
For team augmentation and a dedicated engineer, we charge an hourly rate depending on seniority (mid-level, senior, senior lead). For consultancy and project-based scope, we charge per sprint or a fixed total budget based on deliverables. We share rates openly during the introductory call, with no hidden sliding scales or penalty clauses. We give indicative amounts verbally based on your scope rather than on a pricing page, because that rarely matches what an engagement actually requires.
Do you also build an internal developer platform (IDP)?
Yes, often based on Backstage or a custom abstraction layer on top of Kubernetes and cloud resources. It usually suits organisations with 10+ developers where the DevOps bottleneck has become visible — manual service onboarding then takes up too much time. We build a minimal IDP with a few self-service flows and expand it based on what your own developers actually use.

Talk to us about your DevOps project.

A no-obligation, half-hour introduction. We listen to your cloud setup, ask follow-up questions where needed, and are honest about whether a DevOps engineer is the right step for you — or whether a shorter consultancy engagement will do. No sales pitch.

Edit content