Are you an official Google Cloud Partner?
No. We are an independent software development agency that works a lot with Google Cloud, but we don't present ourselves as a Google Cloud Partner with a specific specialisation. For some customers, that is actually an advantage: no channel pressure, no partner incentives and no "we have to mention this service because we're a partner". Our value lies in hands-on experience with production workloads on GCP — not in a logo. If you explicitly need a partner relationship, for example for a Google-funded migration programme or a marketplace procurement route, we'll say so honestly and help you find the right party.
Do you also work with AWS or Azure?
Yes. We have hands-on experience with all three major hyperscalers and see no reason to be dogmatic about choosing one. Google Cloud is often a strong choice for organisations that rely heavily on data and AI — BigQuery as the warehouse, Vertex AI and Gemini as the AI platform, Cloud Run as a developer-friendly compute layer. If you're deep in a Microsoft stack, Azure may make more sense; if you need the breadth of the AWS ecosystem, AWS. We also advise on where a hybrid or multi-cloud setup makes sense — and where it only adds unnecessary complexity.
How do you handle vendor lock-in on Google Cloud?
Deliberately. Not by avoiding all managed services — that often costs more in build and maintenance than it saves — but by explicitly naming the dependency with every significant service choice. For some workloads, deep GCP integration through Cloud Run, Pub/Sub and Spanner is perfectly fine; for others, a container approach on GKE is the wiser choice precisely because it could run elsewhere on Kubernetes with limited changes. For data, Iceberg support and BigLake play a role in the exit strategy — your data sits in an open format that other engines can read too. We weigh this up case by case.
What is a GCP Landing Zone, and do we need one?
A GCP Landing Zone is a standardised baseline setup following Google's Cloud Adoption Framework and the Enterprise Foundations Blueprint: organisation, folder and project hierarchy, a project-vending approach, a Shared VPC or hub-and-spoke network blueprint, baseline policies via the Organization Policy Service, an identity layer in Cloud Identity, and an approach to logging, monitoring and billing. For organisations that work with Google Cloud on a structural basis, it is almost always the sensible choice — restructuring a messily built GCP organisation after the fact is far more expensive than putting a good landing zone in place up front. For very small organisations with a single GCP project, a full landing zone is overkill; in that case we recommend a lighter baseline that can grow later.
Which Google Cloud services do you typically work with?
Compute: Cloud Run, GKE and Cloud Functions. Data: BigQuery at the core, plus Cloud SQL, Spanner, AlloyDB, Firestore, Cloud Storage and Bigtable. Edge: Cloud CDN and Cloud Load Balancing. Identity: Cloud Identity, Identity Platform or Firebase Authentication, and Workload Identity Federation for machine identity. AI: Vertex AI, the Gemini API, Document AI and Vision AI — see also our
AI development page. Events and APIs: Pub/Sub, Eventarc, Workflows, API Gateway and Apigee. Observability: Cloud Logging, Cloud Monitoring, Cloud Trace, Cloud Profiler and Error Reporting. That's the core; around it we work with countless other services whenever the situation calls for it.
Where do we store data — in which Google Cloud region?
For Dutch customers, usually europe-west4 (Eemshaven, Groningen), with europe-west1 (Belgium) or europe-west3 (Frankfurt) as a secondary region for disaster recovery. For customers with a Scandinavian focus, europe-north1 (Finland) may be a better fit. What choosing a region does not automatically solve is data leakage via logging, AI or management services. The Google EU Data Boundary is a serious commitment that customer and support data stays within the EU for the covered services, but it is no excuse for not checking the configuration. That has to be set up separately through Organization Policies, correct KMS key allocation, VPC Service Controls and deliberate choices around multi-region storage. We do this setup as part of a security baseline.
Do you work with Cloud Build or GitHub Actions?
Either, with a slight preference for GitHub Actions: the developer experience is stronger, the community is larger and the Google Cloud integration through the official google-github-actions is mature. Workload Identity Federation makes it easy to deploy from GitHub Actions to GCP without long-lived service account keys. For organisations that want to keep everything in a single pipeline within GCP, especially when Artifact Registry, Binary Authorization and Cloud Deploy are deeply integrated, Cloud Build is a perfectly good choice. It's not a religion; our preference is for whichever tooling the client's developers are comfortable with.
Why do organisations choose BigQuery over another warehouse?
The combination of serverless pricing (storage and compute billed separately), a mature SQL engine, BigQuery ML for running models directly on the data, BigLake and Iceberg support for open table formats, and tight integration with Vertex AI and Gemini for multi-modal queries. For organisations moving towards an AI-first approach, BigQuery often feels more natural than a classic warehouse. For traditional BI workloads, Snowflake or Databricks may fit just as well or better, depending on your existing tooling and team skills. We're not dogmatic; the choice between warehouses is an open question in every engagement.
How do you differ from a Google Cloud-only consultancy?
A GCP-only firm often knows the platform inside out. We differ in three ways. First, we're vendor-independent, so choosing Google Cloud is an outcome of the analysis, not the starting point. Second, we also build applications, not just infrastructure, which avoids handovers. Third, our pricing suits mid-market budgets. If you've already chosen GCP and only need platform-specific optimisation, a GCP-only firm may suit you well. If you want advice and delivery to stay connected, we occupy a different niche.
What determines the cost of a Google Cloud consulting engagement?
Mainly the scope and the complexity of the existing environment. A Well-Architected review for a small, straightforward Google Cloud project is a different engagement from an assessment of a multi-folder organisation with dozens of workloads, Shared VPCs and complex Cloud Identity federations. We work with a fixed sprint budget per phase, so you know where you stand, and we only extend it if you decide to move on to a next phase.
Do you work with our internal cloud or IT department?
Almost always. In the first phase we actively reach out to your cloud engineers and security officer to understand what's already running and which sensitivities are at play. During delivery we work with mixed teams wherever possible: your people plus ours, with clearly divided ownership. Knowledge transfer isn't an afterthought: when we leave, your team must be able to manage and further develop the Google Cloud environment independently.
How does a programme start in practice?
With an introductory conversation, no obligation. We listen to your situation and advise which format fits: a review, an architecture design or guided implementation. For a review, we first get read-only access so that we can base our proposal on facts.