Are you an official AWS Partner?
No. We are an independent builder agency that works extensively with AWS, but we don't present ourselves as an AWS Partner or Premier Tier. For some clients, that's actually an advantage: our advice carries no channel pressure, no quotas and no "we have to mention this service because we're a partner". Our value lies in hands-on experience building and running production workloads on AWS, not in a logo. If you explicitly need a partner relationship, for example because of a particular procurement requirement, we'll say so honestly and help you find the right party.
Do you also work with Azure or Google Cloud?
Yes. We have hands-on experience with all three major hyperscalers and see no reason to be dogmatic about choosing just one. For each client and each workload, we look at what fits best. AWS is often a strong choice because of the breadth of its services and the maturity of its ecosystem, but for organisations already heavily invested in a Microsoft stack, Azure may make more sense, and for data- and AI-heavy workloads, Google Cloud can be attractive. We also advise on where a hybrid setup or a multi-cloud strategy makes sense, and where it simply adds unnecessary complexity.
How do you handle vendor lock-in on AWS?
Deliberately. Not by avoiding all managed services, which often costs more in build and maintenance effort than it saves, but by explicitly naming the dependency with every significant service choice. For some workloads, deep AWS integration via Lambda, DynamoDB and EventBridge is perfectly fine; for others, a container approach on ECS is the wiser choice precisely because it could run on Kubernetes elsewhere with limited changes. We weigh this up case by case, and you decide with us, so there are no hidden dependencies that catch you out years later.
Which AWS services do you typically work with?
For compute: EC2 for classic workloads, Fargate and ECS for managed containers, EKS where the team has Kubernetes expertise, and Lambda for event-driven or short-running functions. For data: RDS and Aurora for relational databases, DynamoDB for key-value, and S3 for object storage. For the edge: CloudFront and API Gateway. For identity: Cognito and IAM Identity Center. For AI: Bedrock and SageMaker; see also our
AI development page for the broader AI context. For events: EventBridge and Step Functions. For observability: CloudWatch, with additional tooling where needed. That's the core; around it, we work with countless other services when the situation calls for it.
Where do we store data, and in which AWS region?
For European clients, usually Frankfurt (eu-central-1) or Stockholm (eu-north-1), depending on latency requirements and service availability for your stack. For clients with specific connectivity needs to the UK, Ireland (eu-west-1) can be a good choice. What choosing a region does not automatically solve is data leakage via logging, AI or management services that run outside the EU. That needs to be set up separately, for example through specific service policies, correct KMS key allocation and deliberate choices around cross-region features. We do this setup as part of a security baseline.
How do you differ from an AWS-only consultancy?
An AWS-only firm often knows the platform inside out, and that is where they are strong. We differ in three ways. First, we are vendor-independent, so for us choosing AWS is the outcome of the analysis, not the starting point. Second, we build applications as well as infrastructure, which brings the two worlds together in our hands and avoids handovers. Third, our pricing suits mid-market budgets, not just large corporates. For an organisation that has already chosen AWS and only wants platform-specific optimisation, an AWS-only firm can be a perfectly good fit. If you want to keep advice and build connected, or you are still unsure about the platform choice, we occupy a different niche.
What determines the cost of an AWS consulting engagement?
Mainly the scope and the complexity of the existing environment. A Well-Architected review for a small, straightforward AWS account is a different engagement from an assessment of a multi-account environment with dozens of workloads and complex network integrations. Depth also plays a part: a quick scan to get the board up to speed is something else than a fully developed restructuring proposal for the cloud team to work from. We work with a fixed sprint budget per phase, so you know where you stand, and we only extend if you decide to continue 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 is already running, which decisions were made historically and which sensitivities are at play. During delivery we work with mixed teams wherever possible: your people plus ours, with clear ownership. Knowledge transfer is not an afterthought but an ongoing responsibility. When we leave, your team must be able to manage and develop the environment independently.
How does a programme start in practice?
With an introductory conversation, no obligation and no sales pressure. We listen to your situation, ask questions about your current AWS practice and suggest which form (review, architecture design or guided implementation) would suit you. If that resonates, a short proposal follows with scope, lead time and investment. For a review or audit, we first get read access to your AWS environment so we can base the proposal on facts, not assumptions.