# Andrey Lesnikov — Selected Projects Flagship open-source repositories and architecture cases from https://justrunme.com/. ## Flagship GitHub repositories ## architecture-rehearsal - URL: https://github.com/justrunme/architecture-rehearsal - Summary: Deterministic pre-deployment failure simulation and post-deployment verification control plane: causal architecture graph, policy gate, evidence chain, Helm CRDs, Kind operator E2E. ## twinops-control-plane - URL: https://github.com/justrunme/twinops-control-plane - Summary: GitOps control plane for industrial digital twins: OpenUSD composition, drift, reconciliation, telemetry persistence, and incident replay. ## ai-runtime-platform - URL: https://github.com/justrunme/ai-runtime-platform - Summary: AI Infrastructure OS execution plane: OpenAI-compatible gateway, MCP tool governance, intent proxy, vLLM/KServe/KEDA, OIDC, Redis, and OpenTelemetry. ## ai-infra-control-plane - URL: https://github.com/justrunme/ai-infra-control-plane - Summary: Control plane for governed private AI: policy, identity, audit, intent, MCP, FinOps, SLOs, Redis, Prometheus, and OIDC on Kubernetes. ## self-healing-infrastructure-chaos-engineering - URL: https://github.com/justrunme/self-healing-infrastructure-chaos-engineering - Summary: Self-healing infrastructure experiments: failure injection, automated recovery loops, and chaos-driven validation. ## gitops-duel-argocd-vs-flux - URL: https://github.com/justrunme/gitops-duel-argocd-vs-flux - Summary: Interactive duel between Argo CD and Flux — drift, reconciliation, and delivery tradeoffs. ## zero-trust-istio-opa - URL: https://github.com/justrunme/zero-trust-istio-opa - Summary: Istio mesh with OPA policy: mTLS posture, authZ at the edge, and declarative in-cluster guardrails. ## insurance-platform-infrastructure - URL: https://github.com/justrunme/insurance-platform-infrastructure - Summary: Multi-account platform foundation: networking, EKS, identity, and environment-scoped Terraform modules. ## Architecture case studies ### Automatic SaaS Restore System - Case: https://justrunme.com/cases/automatic-saas-restore-system/ - Problem: Restores are high-pressure, manual, and easy to execute inconsistently. - Result: Recovery becomes a platform capability instead of an emergency script. ### Cloud-Native AI Gateway · Flagship - Case: https://justrunme.com/cases/cloud-native-ai-gateway/ - Problem: AI usage needs routing, policy, budget awareness, and provider resilience. - Result: AI becomes operable infrastructure, not an opaque API call. ### Kanister Backup & Restore · Flagship - Case: https://justrunme.com/cases/kanister-backup-restore/ - Problem: Application-aware Kubernetes restores need more than volume snapshots and manual runbooks. - Result: Restore behavior becomes repeatable, reviewable, and easier to exercise before an incident. ### GitOps: Argo CD & Flux · Flagship - Case: https://justrunme.com/cases/gitops-argocd-flux/ - Problem: Teams need a clear delivery model before GitOps becomes another layer of operational confusion. - Result: GitOps decisions become explicit platform contracts instead of tool preference debates. ### SBOM Integration - Case: https://justrunme.com/cases/sbom-integration/ - Problem: Software supply-chain data is often generated late, stored separately, and disconnected from deployment decisions. - Result: Supply-chain visibility becomes part of the delivery system, not a quarterly compliance export. ### LLM Infrastructure Runtime - Case: https://justrunme.com/cases/llm-infrastructure-runtime/ - Problem: LLM workloads move faster than traditional platform controls and can quickly become expensive, opaque, and hard to operate. - Result: LLM usage becomes a controlled platform capability with observability and operating contracts instead of isolated API calls. ### RAG Knowledge Platform · Flagship - Case: https://justrunme.com/cases/rag-knowledge-platform/ - Problem: Engineering knowledge is spread across repositories, runbooks, tickets, architecture notes, and project history. - Result: The AI assistant can answer infrastructure questions with project context, sources, and a safer boundary around what it knows. ### EKS Platform Foundation - Case: https://justrunme.com/cases/eks-platform-foundation/ - Problem: Kubernetes clusters become inconsistent when networking, identity, ingress, storage, and observability are assembled per project. - Result: Clusters become a repeatable platform product rather than a one-off infrastructure build. ### OpenTelemetry Observability Mesh - Case: https://justrunme.com/cases/opentelemetry-observability-mesh/ - Problem: Metrics, logs, and traces often exist separately, making incidents slower and ownership unclear. - Result: Production behavior becomes easier to understand from request path to workload to infrastructure signal. ### SLO-Driven Monitoring - Case: https://justrunme.com/cases/slo-driven-monitoring/ - Problem: Dashboards can look healthy while users experience latency, errors, or degraded workflows. - Result: Monitoring shifts from raw infrastructure charts to reliability decisions teams can act on. ### Multi-Region GitOps - Case: https://justrunme.com/cases/multi-region-gitops/ - Problem: Multi-region systems need repeatable promotion and rollback without turning every deployment into manual coordination. - Result: Regional delivery becomes auditable and reversible while keeping infrastructure state understandable. ### Terraform Platform Modules - Case: https://justrunme.com/cases/terraform-platform-modules/ - Problem: Cloud platforms drift when teams copy infrastructure snippets and adjust them under delivery pressure. - Result: Infrastructure changes become reviewable product changes instead of undocumented console state. ### Argo CD App of Apps - Case: https://justrunme.com/cases/argocd-app-of-apps/ - Problem: As platforms grow, application onboarding, add-ons, and environment drift become hard to reason about. - Result: Platform state becomes visible in Git and easier to bootstrap, audit, and recover. ### Policy as Code Guardrails - Case: https://justrunme.com/cases/policy-as-code-guardrails/ - Problem: Security and platform rules are often discovered only after deployment or during reviews. - Result: Teams get fast feedback while platform standards are enforced consistently across environments. ### Secrets and Certificate Automation - Case: https://justrunme.com/cases/secrets-certificate-automation/ - Problem: Manual secret rotation and certificate handling create outage risk and hidden operational debt. - Result: Sensitive material becomes lifecycle-managed infrastructure instead of scattered manual state. ### Incident Runbook Automation - Case: https://justrunme.com/cases/incident-runbook-automation/ - Problem: Incidents are slower when context, dashboards, logs, and recovery steps live in different places. - Result: Incident response becomes calmer, more repeatable, and easier to improve after the event. ### Self-Healing Infrastructure - Case: https://justrunme.com/cases/self-healing-infrastructure/ - Problem: Transient infrastructure failures can become user-facing incidents when recovery depends on manual detection. - Result: Common failure modes can recover faster while preserving control over high-risk actions. ### AI Runtime Execution Plane · Flagship - Case: https://justrunme.com/cases/ai-runtime-execution-plane/ - Problem: AI workloads often start as API calls but become production systems that need identity, policy, scaling, telemetry, and clear ownership. - Result: AI execution becomes a governed platform surface instead of scattered application code and unmanaged provider calls. ### Developer Platform Interface - Case: https://justrunme.com/cases/developer-platform-interface/ - Problem: Developers lose time when every deployment, environment, and infrastructure request requires platform team translation. - Result: Teams can ship through clear platform paths while platform engineers keep control of the underlying system. ### Cost and Token Observability - Case: https://justrunme.com/cases/cost-token-observability/ - Problem: AI and cloud costs can grow quietly when usage is disconnected from teams, services, and deployment changes. - Result: Cost becomes an operational signal teams can understand before it becomes a finance surprise. ### FleetDM Endpoint Visibility - Case: https://justrunme.com/cases/fleetdm-endpoint-visibility/ - Problem: Endpoint visibility is often separate from cloud and Kubernetes operations, leaving security context incomplete. - Result: Endpoint state becomes part of the broader infrastructure picture instead of a separate security island. ### Zero Trust Service Mesh · Flagship - Case: https://justrunme.com/cases/zero-trust-service-mesh/ - Problem: Internal traffic is often trusted by default, making lateral movement and policy gaps hard to see. - Result: East-west traffic becomes governed, observable, and easier to reason about during security reviews and incidents. ### Architecture Rehearsal · Flagship - Case: https://justrunme.com/cases/architecture-rehearsal/ - Problem: Teams discover architectural blast radius only after a change lands in production. - Result: Operators know what breaks before they deploy — and can prove whether the prediction was right after the change lands. ### TwinOps Control Plane · Flagship - Case: https://justrunme.com/cases/twinops-control-plane/ - Problem: Industrial digital twins are often demos, not operable infrastructure with drift, reconciliation, and incident replay. - Result: Digital twins behave like platform products — reviewable, recoverable, and demonstrable without treating the twin as a one-off notebook. ### AI Infra Control Plane · Flagship - Case: https://justrunme.com/cases/ai-infra-control-plane/ - Problem: Private AI platforms need shared governance across identity, policy, audit, cost, and SLO signals — not scattered service configs. - Result: Governed private AI becomes operable as a platform product with explicit contracts instead of ad-hoc service wiring.