Skip to content
Back to skills

Coreweave Reference Architecture

ASecurity

Reference architecture for CoreWeave GPU cloud deployments. Use when designing ML infrastructure, planning multi-model serving, or establishing CoreWeave deployment standards. Trigger with phrases like "coreweave architecture", "coreweave design", "coreweave infrastructure", "coreweave best practices".

  • 65 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added May 30, 2026
ai-agentsdockerkubernetesgitperformancedocumentation

Security analysis

A100/100

Scanned May 30, 2026

npx -y skills add ComeOnOliver/skillshub --skill coreweave-reference-architecture --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Coreweave Reference Architecture?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Coreweave Reference Architecture
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/comeonoliver-coreweave-reference-architecture/badge)](https://www.skillsdirectory.com/skills/comeonoliver-coreweave-reference-architecture)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: coreweave-reference-architecture
description: |
  Reference architecture for CoreWeave GPU cloud deployments.
  Use when designing ML infrastructure, planning multi-model serving,
  or establishing CoreWeave deployment standards.
  Trigger with phrases like "coreweave architecture", "coreweave design",
  "coreweave infrastructure", "coreweave best practices".
allowed-tools: Read, Write, Edit, Grep
version: 1.0.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags: [saas, gpu-cloud, kubernetes, inference, coreweave]
compatible-with: claude-code
---

# CoreWeave Reference Architecture

## Architecture Diagram

```
                    ┌─────────────────────┐
                    │   Load Balancer     │
                    │   (Ingress/LB)      │
                    └──────────┬──────────┘
                               │
              ┌────────────────┼────────────────┐
              │                │                │
     ┌────────▼──────┐ ┌──────▼────────┐ ┌─────▼───────┐
     │ Model A       │ │ Model B       │ │ Model C     │
     │ (vLLM, A100)  │ │ (TGI, H100)  │ │ (SD, L40)   │
     │ 2 replicas    │ │ 1 replica     │ │ 3 replicas  │
     └───────────────┘ └───────────────┘ └─────────────┘
              │                │                │
     ┌────────▼────────────────▼────────────────▼───────┐
     │              Shared Storage (PVC)                │
     │         Models / Checkpoints / Data              │
     └──────────────────────────────────────────────────┘
```

## Project Structure

```
ml-platform/
├── k8s/
│   ├── base/                    # Shared templates
│   ├── models/
│   │   ├── llama-8b/           # Per-model manifests
│   │   ├── llama-70b/
│   │   └── stable-diffusion/
│   └── infra/
│       ├── storage.yaml         # PVCs
│       ├── secrets.yaml         # Model tokens
│       └── monitoring.yaml      # Prometheus rules
├── containers/
│   ├── vllm/Dockerfile
│   └── custom-server/Dockerfile
├── scripts/
│   ├── deploy.sh
│   └── benchmark.sh
└── monitoring/
    ├── grafana-dashboards/
    └── alert-rules.yaml
```

## Key Design Decisions

| Decision | Choice | Rationale |
|----------|--------|-----------|
| Serving framework | vLLM | Continuous batching, PagedAttention |
| GPU type (production) | A100 80GB | Best price/performance for inference |
| Storage | Shared PVC (SSD) | Fast model loading across replicas |
| Autoscaling | KServe + Knative | Native scale-to-zero support |
| Container registry | GHCR | GitHub integration, free for public |

## Resources

- [CoreWeave Documentation](https://docs.coreweave.com)
- [CoreWeave Examples](https://github.com/coreweave/kubernetes-cloud)

## Next Steps

For multi-environment setup, see `coreweave-multi-env-setup`.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.