Skip to main content

AI/Run CodeMie Deployment Architecture

This page provides an overview of the AI/Run CodeMie deployment architecture on Microsoft Azure, including infrastructure components, network design, and resource requirements.

Architecture Overview

AI/Run CodeMie is deployed on Azure Kubernetes Service (AKS) with supporting Azure services for networking, storage, and identity management.

High-Level Architecture Diagram

The diagram below illustrates the complete AI/Run CodeMie infrastructure deployment on Azure:

Azure Architecture Diagram

Architecture Customization

The architecture can be customized based on your organization's security policies, compliance requirements, and operational preferences. Consult with your deployment team to discuss specific requirements.

Resource Requirements

Container Resource Requirements

The table below specifies resource requirements for AI/Run CodeMie components sized for high-scale production deployments supporting 500+ concurrent users.

ComponentPodsRAMvCPUStorage
CodeMie API28Gi4.0
CodeMie UI1128Mi0.1
Elasticsearch216Gi4.0200 GB per pod
Kibana11Gi1.0
Mermaid-server1512Mi1.0
PostgreSQLManaged service in cloud30-50 GB
Keycloak + DB1 + 14Gi2.01 GB
Oauth2-proxy1128Mi0.1
NATS + Auth Callout1 + 1512Mi1.0
MCP Connect11Gi0.5
Fluent BitDaemonSet128Mi0.1
LLM Proxy11Gi1.0
Scaling Considerations

The listed requirements are designed for high-scale production deployments. For smaller teams and lower concurrency, some resources can be scaled down:

  • User Concurrency: API replicas can be scaled depending on the load
  • Data Volume: Elasticsearch stores vector datasources, user metrics and container logs, therefore storage grows with datasources amount and size and log retention policies
  • Database Sizing: PostgreSQL managed service tier depends on user count, the amount of resources they create in CodeMie, and additional extensions connected to CodeMie that share the same database instance
  • LLM Proxy: Resource requirements depend on the exact LLM proxy type being used

Next Steps

After understanding the architecture, proceed to: