Twee kolommen tegenover elkaar: zonder landing zone groeien rechten met elke uitzondering en merk je het budget pas aan het eind van de maand; met landing zone zijn rollen vastgelegd en staan grenzen en alarm per omgeving ingesteld.

Cloudconsultancy

To the cloud without downtime, and without surprises on the bill.

The cloud is rarely the goal. The goal is that you can deliver faster, that it does not fall over when it gets busy, and that you know what it costs. We are a certified Google Cloud Partner and work just as well on AWS: we guide the migration, set up the foundation, and keep running it afterwards.

Wherecloudmigrationsbreakdown

Almost never on the technology. Four things keep coming back:

  • The bill. You pay for what you switch on, not for what you use. Without budget limits and without someone looking at it monthly, it quietly climbs.
  • A lift-and-shift that stays. The machines move unchanged and then there is no time for the second step. You get the downsides of both worlds.
  • Permissions nobody oversees any more. IAM grows with every exception, until nobody can say who can reach what.
  • One person who knows. Works fine until that person goes on holiday.

Thelandingzone:fourlayers

A landing zone is the environment your applications land in: set up before anything moves, instead of built around it after things went wrong. Our reference architecture has four layers, each with its own development cycle.

Everything is delivered as code: environments, permissions, network, policy. Not tidy for the sake of tidy; it is what gets you through an audit and what lets you rebuild the whole environment if you have to. See the ZEN Cloud Landing Zone.

Een stapel van vier lagen, van boven naar beneden: applicaties, platform, landing zone en organisatie. De onderste lagen zijn het breedst omdat ze de rest dragen.

Migratingisthestart,nottheend

The months after the migration decide whether it succeeded. That is our work just as much: CI/CD that does not fall over every Friday, observability so you see an outage before a customer calls, and a look at the bill every month.

Next to this is the GitLab profile of our own bot: on 8 September, 112 actions in one day. Dependency updates, a security bump of cryptography, a branch for the next Kubernetes version. Work nobody did by hand, and that would all have been left lying without this automation.

We work with the vendors' own frameworks, AWS Well-Architected and the Google Cloud Architecture Framework, because then you can measure where you stand instead of arguing about it. Want only this part, without a migration? That works too.

GitLab-profiel van de ZEN Software Bot met 112 bijdragen op 8 september 2026, en de activiteitenfeed eronder: een Next.js-update, een nieuwe branch voor Kubernetes 1.30, een goedgekeurde auto-merge en een security-bump van cryptography naar v42.

Alreadyinthecloud,butitcouldbebetter?

Many companies have run in the cloud for years and are not happy with it: the bill keeps growing, deployments stay nerve-racking, and when something falls over nobody knows where to look. We do that work too, without a migration:

  • Kubernetes and GKE. Clean up clusters, autoscaling that works, upgrades without downtime.
  • Deployments and CI/CD. From "no deploys on Friday" to several a day, with a rollback you trust.
  • Observability and SRE. Logging, metrics and alerting that show the cause, not just the symptom.
  • Cost (FinOps). What you pay against what you use, and what you can switch off without risk.

Want to know where you stand first? The Cloud & DevOps scan gives you a prioritised list of improvements in 5 days, for €4,000 excluding VAT.

Managedcloud:from€950permonth

Once it runs, we keep it running. Managed cloud costs from €950 per month, or 10% of your cloud spend if that is higher. Excluding VAT, cancellable monthly. Included:

  • Monitoring and alerting. We see an outage before your customer calls.
  • Cost control. A monthly look at the bill, with budget limits that raise an alarm.
  • Updates and patches. Kubernetes versions, libraries, security fixes.
  • Agreed response times. How fast we respond to an outage and to a question is in the agreement, so you know where you stand.

That is during office hours. 24/7 on-call is available on request, as a separate agreement on top of the base fee. Unplanned work and outages fall under managed cloud; planned improvement work on infrastructure and CI/CD goes in sprints.

GoogleCloudPartner

We are a certified Google Cloud Partner. That means Google has assessed our engineers and our projects, and that for environments on Google Cloud we can apply to the partner programmes: sometimes a scan or a migration is partly funded from them. And we work just as well on AWS; which cloud it becomes depends on what you already have.

Google Cloud Partner badge

Orwereinforceyourownteam

Already have people on cloud and operations, but something is missing? Then we join in instead of taking over. On this ground that is our usual form: senior engineers in your rhythm, responsible for the result.

How project reinforcement works · Cloud migration and DevOps coaching at ANWB

Frequently asked questions about cloud

  • AWS or Google Cloud?

    That depends on what you already have and what your people know, not on which one we like best. We work on both and are a certified Google Cloud Partner. A readiness assessment usually surfaces that choice within a few days.

  • What does a cloud migration cost?

    +

  • Do we have to move everything at once?

    +

  • Can you do just the managed cloud?

    +

  • Can infrastructure work be done as a sprint?

    +

  • What do cloud consultancy or project reinforcement cost per hour?

    +

Onze contactgegevens

Oosterweezenstraat 6E
1823CN Alkmaar

What runs now, and where do you want to go?

Send us what runs at the moment and what is not going well. You get back whether it is a migration question, a foundation question or a managed cloud question, and what the first step would be.