Skip to content
cirlume.
Menu

Cloud & infrastructure / 7 technologies

Infrastructure you can read, review and rebuild.

Which cloud a product runs on matters less than whether anyone can explain how it was set up. We work on AWS, Azure, Google Cloud, Cloudflare, Vercel and Hostinger, and define environments in Terraform so changes go through review like application code. The accounts stay in your name.

Start a project

What we use

Cloud & infrastructure technologies we know well.

Why us

What we bring to cloud & infrastructure work.

  • AWS in production

    Our products use Lambda, API Gateway, Cognito and AppSync, so we design for those services as they really behave.

  • Terraform from day one

    Our own infrastructure is defined in Terraform, so environments can be reviewed, repeated and rebuilt.

  • Accounts in your name

    Cloud accounts are yours from the first day, not something to transfer at the end of a project.

What you get

What a well-chosen stack gives you.

  • Environments that match

    Development, staging and production built from the same definitions.

  • Access kept tight

    Least-privilege roles, and no passwords shared between people or services.

  • Costs you can see

    Tags, budgets and alerts, so spending shows up before the invoice does.

  • Recovery planned

    Backups, monitoring and written steps for when something fails.

Where AI fits

AI in cloud & infrastructure work.

  • Models inside your cloud account

    Amazon Bedrock, Azure and Google’s Gemini Enterprise Agent Platform give model access under your own account’s access, logging and billing controls.

    AI workflow automation ↗

  • Region and residency checks

    Model availability differs by region, so we check where prompts and documents will be processed before choosing a service.

    Cloud architecture ↗

Where it stops: Turning on a model service does not make a use compliant. Data protection and sector rules still apply to every prompt and output.

Choosing between them

Which one, and when.

AWS has the widest range of managed services and is where SoulCare runs. Azure suits organisations built on Microsoft 365 and Entra ID. Google Cloud is strong for data and container workloads. Cloudflare puts DNS, caching and security in front of any of them, and can host lightweight apps at the edge. Vercel hosts web front ends with a preview for every change. Hostinger covers domains, email and small servers. For smaller apps, Firebase or Supabase replace much of this setup with a managed back end. Terraform describes the infrastructure behind them.

What’s changing

Shifts to plan for.

Dates that affect cloud & infrastructure technologies, checked against the official sources.

  1. June 2026

    Amazon Linux 2 reaches end of life

    Amazon Linux 2 reached end of life on 30 June 2026. Lambda runtimes built on it get limited patches until their own deprecation dates.

  2. April 2026

    Lambda deprecates Node.js 20

    Lambda stopped patching nodejs20.x on 30 April 2026. Creating functions on it is blocked from 29 July 2027 and updating them from 31 August 2027.

  3. April 2026

    Vertex AI becomes Agent Platform

    Google renamed Vertex AI to Gemini Enterprise Agent Platform. Existing workloads carry on, but console names and documentation changed.

Common questions

Cloud & infrastructure questions.

Can you work in our existing cloud account?

Yes. We review what is running, who has access and how it was created, then bring it into code step by step.

Will you lock us into one provider?

No more than the product needs. Managed services save work but tie you closer to a provider, and we explain that trade-off when we choose them.