agent-landing-zone vs openai-chat-app-quickstart
Two of the top cloud reference architectures, side by side: score, setup, license, activity and what each review found.
agent-landing-zone
Azure infrastructure templates for deploying enterprise agent apps on Microsoft Foundry
openai-chat-app-quickstart
Minimal Quart chat app on Azure OpenAI with managed identity
| What we compare | agent-landing-zone | openai-chat-app-quickstart |
|---|---|---|
| Score parts, out of 100 | ||
| Adoption | 59, popular | 23, niche |
| Freshness | 100, active | 100, active |
| Maintenance | 98, healthy | 10, weak |
| Easy to run | 33, some setup | 33, some setup |
| Agent-ready | 30, minimal | 0, none |
| Facts from GitHub and the README | ||
| Stars | 1.2k | 254 |
| License | MIT (permissive) | MIT (permissive) |
| Last commit | Oct 2026 | Sep 2026 |
| Last release | Oct 2026 | None published |
| Language | Python | Bicep |
| Docker | No | Yes |
| GPU | Not stated | Not needed |
| arm64 or Apple Silicon | Not stated | Not 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
openai-chat-app-quickstart
Python Quart backend using the openai package with a plain HTML/JS frontend that streams JSON Lines over a ReadableStream, plus Bicep for Azure OpenAI, Container Apps, Container Registry, Log Analytics and RBAC roles, deployed with azd up. Authenticates to Azure OpenAI with managed identity, so no API key; the local dev server runs on port 50505 after a first azd deploy. For teams starting a chat service on Azure.
Who it is for: Python teams starting a chat service on Azure
Strengths
- Managed identity auth; no OpenAI key in config
- Bicep provisions the full Container Apps stack
- Codespaces and Dev Container configs included
- IaC security scan GitHub Action included
Weaknesses
- Local run depends on a prior Azure deployment for the endpoint
- No user auth; sibling repos add Entra ID
- Frontend is minimal HTML/JS, not a component framework
- Azure Container Registry has a fixed daily cost
- Bicep, Azure OpenAI (openai package)
- Needs Azure subscription with Azure OpenAI access, azd CLI
- GitHub template
- env example file
More in Cloud reference architectures
- agent-landing-zone vs fullstack-solution-template-for-agentcore
- agent-landing-zone vs azurechat
- fullstack-solution-template-for-agentcore vs azurechat
- fullstack-solution-template-for-agentcore vs openai-chat-app-quickstart
- azurechat vs openai-chat-app-quickstart
- The full Cloud reference architectures ranking with reviews