ArchestackGitHub ↗ (opens in a new tab)

agent-landing-zone vs azurechat

Two of the top cloud reference architectures, side by side: score, setup, license, activity and what each review found.

11st of 7 in Cloud reference architectures

agent-landing-zone

Azure infrastructure templates for deploying enterprise agent apps on Microsoft Foundry

64 out of 100
33rd of 7 in Cloud reference architectures

azurechat

Private enterprise chat on Azure OpenAI with document chat and personas

42 out of 100
agent-landing-zone vs azurechat: score parts and facts
What we compareagent-landing-zoneazurechat
Score parts, out of 100
Adoption59, popular69, popular
Freshness100, active100, active
Maintenance98, healthy16, weak
Easy to run33, some setup0, hard
Agent-ready30, minimal0, none
Facts from GitHub and the README
Stars1.2k1.4k
LicenseMIT (permissive)MIT (permissive)
Last commitOct 2026Aug 2026
Last releaseOct 2026None published
LanguagePythonTypeScript
DockerNoNo
GPUNot statedNot needed
arm64 or Apple SiliconNot statedNot stated

agent-landing-zone

Agent Landing Zone is an azd and Bicep template that provisions a Zero-Trust Azure environment for agent applications on Microsoft Foundry. `azd up` deploys the infrastructure plus UI, orchestrator and ingestion apps, each from its own Azure repository. `azd provision` deploys the infrastructure alone. It was previously named GPT-RAG.

Who it is for: Azure teams deploying network-isolated enterprise agent apps with IaC

Strengths

  • Infrastructure-only mode via `azd provision`, with apps deployed later using `azd deploy`
  • Component versions pinned in manifest.json for reproducible releases
  • Custom apps can replace the defaults through app-definition.json
  • MIT license; docs cover network-isolated deployment

Weaknesses

  • Tied to Azure and Microsoft Foundry; no other cloud is mentioned
  • Default UI, orchestrator and ingestion code live in three separate repositories
  • README gives no cost, quota or resource sizing figures
  • Prerequisites and configuration are only in external docs, not the README
  • Python
  • Needs Azure, Microsoft Foundry, Azure OpenAI, Azure AI Search, Azure Developer CLI
  • GitHub template
Documentation ↗ (opens in a new tab)Repository on GitHub ↗ (opens in a new tab)

azurechat

Microsoft solution accelerator: a Next.js chat app deployed into your own Azure subscription with azd up or a Deploy to Azure button, protected by an identity provider (Entra ID setup scripted), with chat over uploaded files, personas, extensions and managed-identity RBAC instead of keys. Supports private endpoints and ESLZ-compliant deployment. For organizations wanting a ChatGPT-like tenant on Azure OpenAI.

Who it is for: Enterprises deploying a private chat tenant on Azure

Strengths

  • Managed identity removes almost all keys and secrets
  • Chat over files, personas and extensions documented in docs/
  • Private endpoints and ESLZ-compliant deployment supported
  • azd template plus GitHub Actions deploy path

Weaknesses

  • Azure only; provisions several paid services
  • Identity provider setup is mandatory before first use
  • Contributions require a Microsoft CLA
  • README defers most detail to docs/; no tests mentioned
  • TypeScript, Azure OpenAI
  • Needs Azure subscription, Azure OpenAI, Entra ID or another identity provider
Repository on GitHub ↗ (opens in a new tab)

More in Cloud reference architectures