Der Shop ist online

Wir bauen Workstation AI-Maschinen für Websites, KI-Agenten und LLM-Training – online konfigurieren und kaufen.

Händlerpreise erhalten
KI-Produkte
KI-LabsOpenAI-AgentenClaude-AgentenGrok-BotWorkstation AI-natives CRMMarketingAlle Produkte
KI-Lösungen
Angewandte KIKI-AgentenGenerative KIKI-AutomatisierungKI-WeiterbildungKI-Pakete für KMUEnterprise AI LabKI-WorkstationsNVIDIA-Hardware & -SoftwareNVIDIA Accelerated ComputingPrivate KIGPU-Private-CloudGPU-ClusterEdge-KIKI nach Branche
KI-Services
PlattformmodernisierungDigital EngineeringDatengrundlagen & KIAutonomer BetriebKI-BeratungDevOps-AutomatisierungCybersicherheitSoftwareentwicklungAgentenentwicklungMLOps-EinrichtungGPU-LeasingGPU-Private-Cloud
Über uns
UnternehmenUnsere GeschichtePartnerKundengeschichten
KI-Rechenzentren
KI-RechenzentrenGPU-Private-CloudGPU-ClusterGPU-Leasing
KI-EinblickeJev-ReiheBenchmark LabModellauswahl
Technische Hinweise
Dokumentation
Linux-BetriebssystemeUbuntuRed Hat Enterprise LinuxSUSE LinuxAlpine LinuxDebian, Rocky & AlmaLinux
KI-Cloud-PlattformenAWS & Amazon BedrockGoogle Cloud & Vertex AIMicrosoft Azure & AI FoundryGPU-Clouds & Marktplätze
Private KI-RechenzentrenFür AnwaltskanzleienFür Steuer- und WirtschaftsprüfungskanzleienOn-Premises-PlattformenVollständig abgesicherte Cloud
ToolsRing PromoterJobshout
News
Blog
KontaktAnmelden

KI-Workstations, Multi-Agenten-KI-Software, GPU-Infrastruktur und intelligente Agentenlösungen für moderne Unternehmen.

Kontakt

KI-Lösungen

Angewandte KIKI-AgentenGenerative KIKI-AutomatisierungKI-WeiterbildungKI-Pakete für KMUEnterprise AI LabKI nach Branche

Produkte

Alle ProdukteWorkstation AI-natives CRM & ERPMarketingOpenAI-AgentenRing PromoterJobshout

Unternehmen

Über unsUnternehmenKI-RechenzentrenWarum WorkstationPartnerKundengeschichtenPreiseKontaktTenthMatrix

Ressourcen

KI-EinblickeTechnische HinweiseDokumentationLinux-BetriebssystemeKI-Cloud-PlattformenPrivate KI-RechenzentrenBlogSucheSitemap
Büro Belgien
Workstation SRL, Rue Vanderkindere 34, 1180 Uccle, BrusselsBE 0751.518.683Mo – Fr: 9:00 – 18:00 Uhr MEZ
+32 492 45 67 46
Hauptsitz Großbritannien
77-79 Marlowes, Hemel Hempstead HP1 1LFAnfahrt – Ausfahrt 20 der M25 (Outer London)Handelsregisternr.: 11641870Mo – Fr: 9:00 – 18:00 Uhr GMT
+44 7515 356 146
Büro Indien
#159 Sector 9, Pocket 1, DDA Flats, 110077 Dwarka, New Delhi
+91 98881 98841
Büro Taiwan
3F, No. 2-4, Aisi Rd., Ren'ai Dist., Keelung City 200, Taiwan基隆市仁愛區愛四路2之4號3樓Mo – Fr: 9:00 – 18:00 Uhr Taiwan-Zeit (GMT+8)
+886 926 892 701+32 492 45 67 46
Büro Estland
Aleksander Puškini tn 30-25, 20306 Narva, EstoniaMo - Fr: 9:00 - 18:00 Uhr estnischer Zeit (EET)
+32 492 45 67 46

© 2026 Workstation AI. Alle Rechte vorbehalten.

DatenschutzDatenlöschungCookiesNutzungsbedingungenWebsite-Sitemap

NVIDIA, das NVIDIA-Logo, RTX, RTX PRO, Blackwell, CUDA, NVLink, MGX, Omniverse, Spectrum-X, Quantum, BlueField, DGX und HGX sind Marken und/oder eingetragene Marken der NVIDIA Corporation in den USA und anderen Ländern. AMD, das AMD-Arrow-Logo, EPYC, Instinct, Ryzen und Threadripper sind Marken von Advanced Micro Devices, Inc. Dell und PowerEdge sind Marken der Dell Inc. oder ihrer Tochtergesellschaften. Intel und Xeon sind Marken der Intel Corporation oder ihrer Tochtergesellschaften. AMAX, AceleMax und LiquidMax sind Marken der AMAX Engineering Corporation. Alle anderen Produktnamen, Logos und Marken sind Eigentum ihrer jeweiligen Inhaber. Wir verwenden sie ausschließlich, um die Produkte zu kennzeichnen, die wir beschreiben, liefern oder unterstützen; ihre Verwendung bedeutet nicht, dass ihre Inhaber uns empfehlen.

Startseite / Technische Hinweise / Technology
DevOpsCI/CDAI AgentsKubernetesSRE

Workstation AI Shop on Ring Promoter: Orbit, Version-Verified Health and the Path from INT to PROD

Technical guide: shop Helm/CI mapping, Orbit semantics, version-verified health for the AI agent, secrets per ring, promote API, and a production checklist

12. September 2026Technology6 min read

This article is the release-engineering deep dive for Workstation AI Shop — the storefront at shop.workstation.co.uk that sells GPU machines and uses a fully autonomous AI Sales Agent to configure baskets. Companion blog (stakeholder-friendly): Promoting the AI Shop through the rings. Control-plane reference: ringpromoter.com.

Watch on YouTube · Product: ringpromoter.com

Ring Promoter Orbit: Workstation AI Shop deploying at INT with version 7cd70f6, rings int test acc prod, TTFB 71ms London, application list sorted by latency
Production Orbit board during a Workstation AI Shop promotion. App label matches the Ring Promoter registry name; blue node = deploy in progress; Earth = PROD / live users.

1. System under promotion

Workstation AI Shop is a Next.js server app (Helm chart shop-chart) on k3s. The browser talks only to the shop; the shop BFF calls OpsAPI in-cluster (http://workstation-opsapi/). Payments use Stripe Checkout with webhooks on OpsAPI. Catalogue freshness is a CronJob (market/sync.mjs). The AI Sales Agent uses Anthropic (ANTHROPIC_MODEL, typically claude-sonnet-5-5, CHAT_MAX_TURNS capped) — if the key is missing, chat shows offline and the rest of the shop still works.

Public hosts

  • INT: https://int-shop.workstation.co.uk
  • PROD: https://shop.workstation.co.uk

Edge path (prod): Cloudflare DNS (DNS-only) → wslproxy → Traefik on the edge node → shop Ingress. Prod has been pinned to a dedicated edge worker where required for latency and certificate locality.

INT TEST ACC PROD flow for Workstation AI Shop

2. Why Ring Promoter owns the hop, not the build

CI still builds and pushes wsw-shop:<sha7>. Ring Promoter answers a different question: is this exact version healthy in ring N, and is it allowed into ring N+1 right now? That matches the product framing on ringpromoter.com:

  1. One ring at a time — promote always targets the next ring.
  2. Source must prove health before anything deploys.
  3. Target must earn health after deploy (retries, then auto-rollback).
  4. Failure undoes itself to the previous recorded version.
  5. Every seed / promote / rollback is written to history.

Shop-specific risk amplifies those rules: the AI agent, market sync and BFF trust keys must move together. A “green Helm job” that leaves an old chat binary answering is a silent sales failure.

3. Reading the Orbit screenshot (release semantics)

From the console capture used in this article:

  • Application name: Workstation AI Shop (human label on the roster and Orbit node).
  • Version in flight: 7cd70f6 (short git SHA — matches image tag convention).
  • Current ring: INT — status Deploying; copy such as “has reached int, N rings to go.”
  • Pipeline legend: int → test → acc → prod across the top of Orbit.
  • Signals: blue node = deployment in progress; green trail = how far the newest version earned; Earth = PROD / live users.
  • SLO breadcrumbs: TTFB ~71ms, location London, GB — useful in the same pane as promotion state so latency regressions are not a separate tool hop.

Lanes (APP × INT/TEST/ACC/PROD matrix) is the complementary view when you need to see whether PROD lags the SHA that already spans ACC.

4. Mapping rings to shop deploy mechanics

Ring Shop mechanism Gate intent
INTGitHub Actions shop-deploy.yaml on main paths under shop/** / chart → deploys intEngineer smoke: /api/health, agent turns, catalogue read
TESTRing Promoter promote INT→TEST (same image SHA)Automated regression; market sync dry observations
ACCPromote TEST→ACCStakeholder UX on AI basket; quote PDF; optional Stripe test mode
PRODPromote ACC→PROD (+ production password). Chart prod may also be workflow_dispatch with TARGET_ENV=prod — Ring Promoter should remain the ledger of what customers runHuman gate; live secrets from vault path workstation-shop/prod/config

Important: treat Helm/workflow deploy as the deployer implementation detail. Ring Promoter remains the system of record for which SHA is current / previous per ring and whether the hop was rolled back.

5. Version-verified health for an AI storefront

Configure the shop health endpoint (or a dedicated readiness field) so Ring Promoter can assert the deployed SHA — via health_version_field or health_version_header as documented on the product site. That catches:

  • Old ReplicaSets still answering while the new Deployment is stuck.
  • Edge/cache serving a previous HTML shell in front of a mixed API.
  • Agent worker and web process skew (chat binary ≠ storefront SHA).

Also verify the source ring reports the same version before promote — so you never promote a SHA that INT already lost.

6. Secrets and AI agent continuity across rings

Per devops/SHOP-DEPLOY.md:

  • Vault: workstation-shop/<env>/config → ESO → shop-secret-<ns>.
  • CI runtime Secret shop-runtime-<ns> may supply ANTHROPIC_API_KEY, OPSAPI_ADMIN_API_KEY, FIRECRAWL_API_KEY.
  • SHOP_BFF_KEY must match OpsAPI’s key for that env or the BFF is treated as anonymous.
  • Prod uses an isolated vault token / SecretStore so rotating INT cannot touch PROD.

Promotion does not invent secrets — but a ring that is “healthy” while the agent is offline is a business-visible defect. Include agent liveness in the health definition you gate on.

7. CI integration shape

After the image is published and INT is seeded (or after the int workflow lands the SHA), promotion is fail-closed HTTP:

curl --fail -sS -X POST "$RP/api/apps/$APP/seed" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d "{\"ring\":\"int\",\"version\":\"$VERSION\"}"

curl --fail -sS -X POST "$RP/api/apps/$APP/promote" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"from_ring":"int"}'

Non-2xx fails the job. 422 means the operation ran, failed health, and rolled back — evidence is in Ring Promoter history / job steps, not only in GitHub Actions logs. Optional ?async=1 returns a job id for live step polling (lock → source health → deploy → target health → record).

8. Auto-promote policy we recommend for the shop

  • ON for early rings when smoke + version health are strong (e.g. INT→TEST).
  • HOLD on ACC so product can sign off AI basket behaviour.
  • Never config-enable auto-promote into PROD — require production password / human promote.
  • Rollbacks remain exempt from the prod password so incidents are not blocked.

Optional gates (maintenance windows, version-specific Go/No-Go, Jira CR, Grafana panels with max_age) run before deploy so a failed gate leaves every ring untouched.

9. Failure modes this design prevents

Failure Without Ring Promoter With protocol
Skipped stagingHotfix workflow_dispatch to prodCannot skip rings by design
Green job, old chatHTTP 200 from previous ReplicaSetVersion-verified health → rollback
Half-updated prodCI timeout aborts mid-rolloutDetached op context + advisory lock
Secret skew INT vs PRODShared token blast radiusIsolated prod SecretStore + ring-scoped config
Unclear “what’s live?”Slack archaeologyOrbit/Lanes + per-ring history

10. Operational checklist (shop release)

  1. Confirm image wsw-shop:<sha7> published.
  2. INT host healthy; agent completes a basket configuration turn; /api/health reports SHA.
  3. Promote through TEST → ACC; re-run market sync observation if catalogue code changed.
  4. Stakeholder sign-off on ACC (AI copy, quote terms, checkout/quote path).
  5. Promote to PROD with production password; verify shop.workstation.co.uk SHA + TTFB.
  6. Leave Orbit open during soak — blue should clear to healthy green on PROD.

11. Related reading

  • Ring Promoter product · Compare vs Argo CD / Kargo / CI
  • Every release earns production · Protocol deep dive
  • QA gates before production
  • Which tool answers which release question
  • In-repo runbook: devops/SHOP-DEPLOY.md

Published by Workstation — GPU storefronts and agentic sales with a promotion control plane you can show in a release review.

Diesen Artikel teilen

Mehr zu Technology

Laptops für KI-Entwickler: LLMs lokal unter Linux mit GPUs mit 16 GB und 24 GB betreiben (Leitfaden 2026)

Laptops für KI-Entwickler: LLMs lokal unter Linux mit GPUs mit 16 GB und 24 GB betreiben (Leitfaden 2026)

Was auf eine RTX 5080 oder RTX 5090 Laptop GPU passt, die Speicherrechnung, die lohnenden offenen Modelle, die Einrichtung von Ubuntu 26.04 mit dem NVIDIA-Stack, Ollama, llama.cpp und vLLM, Coding-Assistenten, LoRA-Fine-Tuning, Sicherheit und wann Arbeit auf einen Server gehört

Weiterlesen
ML- und LLM-Systeme testen, deren Korrektheit sich nicht beweisen lässt: ein Python-Evidenz-Kit

ML- und LLM-Systeme testen, deren Korrektheit sich nicht beweisen lässt: ein Python-Evidenz-Kit

Evidenz statt Beweise, in etwa 400 Zeilen Python mit echter Ausgabe: Slice-Metriken mit Bootstrap-Intervallen und einem Pass/Fail-Vertrag, Property- und metamorphe Tests mit Hypothesis, Kalibrierung und Conformal Prediction, Pydantic-Verträge und Regressionsevaluierungen für LLM-Ausgaben, Drift-Prüfungen, ein CI-Gate und die exakte Verifikation eines kleinen neuronalen Netzes

Weiterlesen
TorchCurves in der Praxis: lernbare B-Spline- und Legendre-Kurven in PyTorch

TorchCurves in der Praxis: lernbare B-Spline- und Legendre-Kurven in PyTorch

torchcurves installieren, eine Kurve anpassen und dimensionieren, B-Spline oder Legendre und die Eingabeabbildung wählen, eine monotone Kalibrierungskurve und ein additives Modell auf tabellarischen Daten bauen, mit SciPy, scikit-learn, einem KAN und einem MLP vergleichen, Koeffizienten nach JSON exportieren, testen und in der Produktion betreiben, mit echten Ausgaben

Weiterlesen