AI Landing Zone

A ready-made, secured AI environment in your own cloud on AWS or Microsoft, with your rules built in and your first agents already running. Typically within two days.

Problem

A policy on paper doesn't stop anything

Your governance model says which data may reach which model, what must stay in the EU and what a human has to approve. Until the platform enforces it, those are good intentions. The AI Landing Zone is a governed home for AI inside your existing cloud, with the controls your governance model called for actually switched on.

  • • Teams calling public model APIs with company data
  • • No way to prove where prompts and outputs are processed
  • • Nobody can say what AI costs, or who spent it

Approach

Ready-made, so it is quick

Typically two days from kick-off to handover. That is possible because the building blocks are already written and tested, and the security settings come straight from your governance model. Your first agents are deployed into the environment as part of the handover. Everything lands in your own cloud and your own code repository.

AWS Bedrock

For AWS-first estates with an EU residency requirement. Pairs with Claude on Bedrock if you want Anthropic models.

Azure AI Foundry

For Microsoft-first estates where Entra ID and M365 are already central. Azure Policy does the enforcement your governance model asked for.

Isolated accounts

Dev and prod for AI workloads, kept apart from general workloads. Least-privilege roles for consumers, builders and operators, federated to your identity provider.

Private and pinned

Private connectivity to model endpoints with no public egress. Customer-managed keys. EU region pinning enforced by policy.

Guardrails

Content safety, prompt-attack defence, PII detection, grounding checks and model allow-lists. Anchored to the OWASP Top 10 for LLM Applications.

Cost and audit

AI workload tagging, budgets and anomaly alerts. Model invocation and control-plane audit logging with retention configured.

What It Costs

Known price, known timeline

The engagement ends with a qualified next step, not a thank-you email: design document and as-built, guardrail test evidence mapped to your governance model, an operations runbook, a two-hour handover, and the top three use cases the platform now unblocks.

€3,000

Fixed price

Per platform, AWS or Microsoft.

2 days

Calendar time

From kick-off to handover, typically.

A few hours

From your people

Your security and platform contacts, for the decisions only you can make.

Every Control Has a Reason

Driven by your own decisions

Each guardrail points back to the clause in your governance model that required it. When an auditor asks why a control exists, the answer is already written down.

Acceptable use

Drives content safety filters and denied topics.

Risk tiering

Drives prompt-attack defences and human approval gates.

Residency rules

Drive region pinning and private endpoints.

Model register

Drives the model allow-list, enforced by policy.

FAQ

Common questions

What do we need in place first?
An AWS Organization or Azure tenant with a working landing zone (or a Cloud² Foundation), a federatable identity provider, Terraform accepted, and a signed-off governance model. Ours, or yours if it is good enough.
Does this build our AI use cases?
No. Use-case and agent development, RAG pipelines, fine-tuning, data platform work and migrations are separate services. So is running the platform afterwards: that is Managed AI, and the agents on it are Managed Agents.
Can we have both Bedrock and Foundry?
Yes. A second platform adds a second landing zone, priced the same way.

Explore More

What comes next

Ready to Get Started?

Let's discuss how Cloud2's AI Landing Zone service can help you achieve your goals.

Cloud Infrastructure