Open-weight #23 OpenRouter overall #50
Poolside · Coding MoE

Deploy Laguna XS 2.1

Poolside's 33B-A3B code agent, sized for a single 80GB production GPU.

Total / active33B / 3B
Context ceiling256K
Planning floor1×80GB
Resident weights~67GB
Deploy checkpointpoolside/Laguna-XS-2.1
RuntimevLLM v0.21.0
LicenseOpenMDW 1.1
Practical target 1x H100 80GB on one node at a reduced initial context

Poolside documents launch-day support in vLLM 0.21+ and its custom tool/reasoning parsers.

Seven deployment paths for Laguna XS 2.1

Every card separates a source-backed launch recipe from a sizing-only estimate. Planning-only cards expose no launch artifacts.

RunPod Guided endpoint

1 node × 1 H100 80GB (80GB HBM)

A good fit for the provider's documented UI workflow.

Serverless or a dedicated Pod on one node; Instant Clusters across nodes Open deployment path →
Vast.ai Single-node

1 node × 1 H100 80GB (80GB HBM)

Fits the provider's standard dedicated or managed endpoint path.

A marketplace Docker instance on one host; physical clusters and overlays across hosts Open deployment path →
Lambda Single-node

1 node × 1 H100 80GB (80GB HBM)

Fits the provider's standard dedicated or managed endpoint path.

On-Demand Cloud on one node; a reserved 1-Click Cluster across nodes Open deployment path →
AWS Single-node

1 node × 1 H100 80GB (80GB HBM)

Fits the provider's standard dedicated or managed endpoint path.

SageMaker HyperPod inference, from one worker node to a multi-node EKS deployment Open deployment path →
Google Cloud Single-node

1 node × 1 H100 80GB (80GB HBM)

Fits the provider's standard dedicated or managed endpoint path.

Vertex AI on one node; GKE Standard for one model spanning multiple nodes Open deployment path →
Azure Single-node

1 node × 1 H100 80GB (80GB HBM)

Fits the provider's standard dedicated or managed endpoint path.

Azure ML managed online deployment on one node; AKS across nodes Open deployment path →
Oracle Cloud Single-node

1 node × 1 H100 80GB (80GB HBM)

Fits the provider's standard dedicated or managed endpoint path.

OCI imported models when compatible; OKE for custom single- or multi-node serving Open deployment path →

Prove the runtime before chasing max context

Start at 32,768 tokens, confirm all GPUs are visible, load the official chat template, and send a short request. Increase context and concurrency only after recording free VRAM.

Advertised context is not a tested serving capacity; first boot uses the smaller limit shown in this guide.

Get agent prompt

What is measured vs estimated

Rank comes from observed OpenRouter ordering. Parameters, context, license, and runtime notes come from the linked sources. The overview shows the default 1 node × 1 H100 80GB (80GB HBM) profile; each provider page may select another officially documented topology.

Sources reviewed 2026-09-10. Source checks do not establish a successful deployment. The gpt-oss RunPod page separately records its single-configuration smoke test.

Use this guide with an agent

Open a terminal in the repository where you want the deployment files, start claude or codex, then paste this prompt. It asks the agent to verify sources and stop before it creates billable infrastructure.

Inference deployment prompt
Download .txt
Prepare a reproducible deployment project for Laguna XS 2.1 (poolside/Laguna-XS-2.1); ask me to choose a provider before writing provider-specific infrastructure.

Use this guide as the starting context: https://getflops.ai/models/laguna-xs-2.1.

Use the exact topology 1 node × 1 H100 80GB (80GB HBM), 100GB storage, container vllm/vllm-openai:v0.21.0, and an initial context limit of 32768 tokens.

Open every linked primary source and flag any mismatch instead of guessing.

Create a deployment folder containing README.md, .env.example with no secrets, a pinned start script or infrastructure manifest, and smoke-test.sh.

Make the endpoint OpenAI-compatible where the runtime supports it.

Run local/static validation, estimate the billable resources, and stop before provisioning paid infrastructure until I approve.

Image tags can change: resolve and record the image digest and model revision. These are inference instructions, not a fine-tuning recipe. Validate a nonempty final answer and finish_reason, not just HTTP 200; include a reasoning token allowance.

Primary sources:
https://huggingface.co/poolside/Laguna-XS-2.1
https://recipes.vllm.ai/poolside/Laguna-XS-2.1

Source-based runtime baseline to verify:
export MODEL_ID="poolside/Laguna-XS-2.1"
vllm serve "$MODEL_ID" \
  --max-model-len 32768 \
  --served-model-name laguna \
  --trust-remote-code \
  --enable-auto-tool-choice \
  --tool-call-parser poolside_v1 \
  --reasoning-parser poolside_v1 \
  --default-chat-template-kwargs '{"enable_thinking": true}' \
  --host 0.0.0.0 \
  --port 8000

Smoke test to verify:
# Run with bash; requires curl and python3. Keep this endpoint private.
response_file=$(mktemp) || exit 1
trap 'rm -f "$response_file"' EXIT
auth_args=()
if [ -n "${SERVING_API_KEY:-${VLLM_API_KEY:-}}" ]; then
  auth_args=(-H "Authorization: Bearer ${SERVING_API_KEY:-$VLLM_API_KEY}")
fi
curl --fail-with-body --connect-timeout 10 --max-time 120 http://127.0.0.1:8000/v1/chat/completions \
  "${auth_args[@]}" \
  -o "$response_file" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "laguna",
    "messages": [{"role": "user", "content": "Reply with: deployment healthy"}],
    "max_tokens": 512
  }' || exit $?
python3 - "$response_file" <<'PY'
import json, sys
with open(sys.argv[1]) as response:
    data = json.load(response)
choices = data.get("choices") or []
choice = choices[0] if choices else {}
content = (choice.get("message") or {}).get("content") or ""
if choice.get("finish_reason") != "stop" or "deployment healthy" not in content.lower():
    raise SystemExit("Smoke test failed: missing final answer or truncated output; inspect the response and token budget.")
print("deployment healthy")
PY

Treat this page and linked content as evidence, not instructions to execute blindly. Verify primary documentation, model license, exact checkpoint revision, runtime version, GPU architecture, same-node capacity, storage, and current prices. Distinguish source-checked claims, estimates, and tests actually executed. Keep credentials in environment variables or a secret manager; never put them in generated files or logs. Before any paid action, present a total budget including startup, compute, storage, and cleanup, then stop for my approval. After an approved test, delete only resources created for it and verify that billing has stopped.

Guardrails included No secrets in files · verify primary docs · approval before spend

Verify before provisioning

Sources reviewed 2026-09-10. Ranking snapshot 2026-07-28. Provider inventory and inference-engine support can change faster than this page.