Skip to content

Infrastructure / DevOps

AWS

Cloud primitives when managed services beat self-hosting.

Layer

Infrastructure / DevOps

Same layer

7 technologies

How we use AWS

We use AWS where your team already operates, with cost and residency constraints written into the design.

Where we reach for it

  • Managed databases and queues

    RDS, SQS, SNS and similar services where handing patching, failover and backups to the provider is worth the price.

  • Object storage and CDN

    S3 with CloudFront for uploads, media and static assets, with lifecycle rules and access policies.

  • Existing AWS organisations

    Delivering into accounts and landing zones a client already runs, following their IAM, tagging and network conventions.

  • Serverless pieces

    Lambda functions and event triggers for spiky or scheduled workloads that do not justify an always-on server.

When we pick something else

For a steady workload on a few servers, a Swiss or EU VPS often costs less and is simpler to reason about. Where Swiss data residency is a hard requirement, we look at Swiss providers first, or at AWS regions with a clear legal assessment.

What we watch for

  • Cost visibility

    Bills grow quietly through data transfer, idle resources and over-sized instances. We set budgets, alerts and tags from the start.

  • IAM and least privilege

    Broad permissions are the usual cause of incidents. We scope roles tightly, avoid long-lived keys and review access periodically.

  • Region and data residency

    Pick the region deliberately, document where data and backups live, and check nDSG and GDPR implications with your legal advisers.

Common questions

Is AWS suitable for Swiss companies with data protection requirements?

It can be, with the right region, encryption, access control and contracts. Residency and legal questions should be assessed per project, and we do not make compliance claims for you.

AWS or a VPS?

A VPS is cheaper and simpler for predictable workloads. AWS makes sense when managed services, elastic scaling or integration with an existing AWS setup matter more than cost simplicity.

Can you take over or clean up our AWS account?

Yes. We inventory resources, map costs and permissions, remove unused items and document the setup, ideally as infrastructure code so changes become reviewable.

Next step

What is costing you time, money or customers today?

You get an honest assessment of whether and how we can help, followed by a written plan with a cost estimate and timeline.

Tell us what you're building

We reply within 1–3 working days, by email, call or video. Your choice.