Summary: High-level topology of 7Mind’s infrastructure after the 2026-09-14 migration to the Gymondo platform: Cloudflare for DNS and the marketing website, AWS (Gymondo) for every API and the web checkout, and a shrinking legacy footprint on Google Cloud that still carries the app’s analytics traffic. Sources: Gymondo-git/terraform (service-cloudfront, apps), Gymondo-git/function-sevenmind-legacy-gateway README, sevenmind/infrastructure (foundation/domains.tf, cloudflare/), sevenmind/website-next-js DEPLOY.md, sevenmind/backend k8s/base/values-production.yaml; Slack 7mind-7nxt-platform-unification; default branches re-read on 2026-11-09 (infrastructure foundation/rudderstack.tf and modules/rudderstack-proxy, backend terraform/environment/staging/RETIRED.md, gateway commit 8905d51, app rudderstack_analytics.dart and products_api_client.dart) Last updated: 2026-11-09


System topology

Three hosting areas, owned by different teams:

  1. Cloudflare (7Mind): DNS for all 7Mind zones, and Cloudflare Pages for the marketing website website-next-js. See cloudflare.
  2. AWS, Gymondo platform (7NXT platform team): everything a 7Mind user talks to besides the marketing pages. CloudFront and Kong in front of Lambdas and EKS services in eu-central-1. See gymondo-platform.
  3. Google Cloud (7Mind, legacy): the old GKE cluster with elixir-backend and its satellites. One piece is still client-facing: the rs.7mind.de proxy that carries every RudderStack event the app sends. See google-cloud.

Request flows

Mobile app

app -> magic.7mind.de -> CloudFront -> Kong (token check and rotation) -> function-sevenmind-legacy-gateway (Lambda) -> Gymondo services
                                                                                        \-> content: S3 catalogue artifact (no fallback)
app -> magic.7mind.de/api/... -> CloudFront -> Kong -> Gymondo services directly (store products, receipt sync)
app -> app.7mind.de/api/v2/users/reset-password -> Gymondo SSO (password reset)
app -> rs.7mind.de (proxy on GKE) -> RudderStack data plane -> service-event-broker -> SNS -> SQS -> function-statistic (practice history)

The store calls are /api/v3/sevenmind/products/{platform}, /api/v4/sevenmind/receipts/google/sync and /api/v1/sevenmind/receipts/transactions. They use the magic.* host but are not answered by the legacy gateway.

Website

browser -> www.7mind.* -> Cloudflare Pages (static Next.js export, Storyblok content baked in)
        -> magic.7mind.* -> legacy gateway (identity, subscription status, insurance, Mondia)
        -> app.7mind.*   -> frontend-public-pages (login, signup, checkout with Adyen) and Gymondo APIs (/api, /train/api)

Hostnames

HostServesWhere
www.7mind.* (.de, .fr, .it, .es, .ca, .co.uk, .app)Marketing website website-next-jsCloudflare Pages
magic.7mind.* / magic.6mind.*Legacy 7Mind API, answered by function-sevenmind-legacy-gatewayAWS (Gymondo CloudFront), since 2026-09-14
app.7mind.* / app.6mind.*frontend-public-pages (login, signup, checkout, password pages) and Gymondo APIs (/api, /api/v2/oauth, /train/api). Until 2026-07-31 this was the 7Mind web playerAWS (Gymondo CloudFront)
gateway.7mind.deElixir content channel, the reference for the gateway’s parity tests. Not called at runtime since 2026-10-07. The staging host gateway.6mind.de went with the Elixir staging plane on 2026-10-07GKE
backend.7mind.de, magic.7sleep.de7Sleep backend (product sunset); answers 410 Gone except the Chargebee webhook since 2026-10-06GKE
panel.backend.7mind.deOld 7Mind admin panel, read-only useGKE, behind Cloudflare Access
zpp-certs.7mind.deZPP prevention certificatesGoogle Cloud Storage
rs.7mind.de / rs.6mind.deLive: proxy for every RudderStack event the app sends, forwarded to RudderStack’s hosted data planeGKE (Traefik on application-cluster)
next.6mind.*Website staging and previewsCloudflare Pages
mobile.6mind.deMobile engineering docsGoogle Cloud Storage

Environments

ProductionStaging / test
7Mind APImagic.7mind.*magic.6mind.*
Gymondo app hostapp.7mind.*app.6mind.*
Websitewww.7mind.*next.6mind.*
Gymondo environmentprodtest

Secret and config management

  • Gymondo platform: AWS Secrets Manager per service; non-secret config in Gymondo-git/terraform tfvars.
  • Website: Cloudflare Pages environment variables.
  • Legacy GCP: Kubernetes secrets created by Terraform in sevenmind/infrastructure and in the backend repo’s own terraform/ (see terraform).
  • Mobile: CI secrets in Codemagic and GitHub Actions. See mobile-build-pipeline.

Observability

  • Gymondo platform: New Relic, CloudWatch alarms, Prometheus.
  • Legacy Elixir backend: Datadog (alerts still post to 7m_backend_health).
  • Clients: Sentry for app and web errors.

Decommissioning status

No shutdown date for the GKE clusters or the GCP project is recorded as of 2026-11-09. Content no longer depends on GKE: the catalogue moved to S3 on 2026-10-05, and the gateway’s fallback to Elixir was removed on 2026-10-07. The Elixir staging plane was destroyed the same day.

Remaining blockers for switching off GKE:

  • rs.7mind.de, the live RudderStack proxy for the app. It must move off the cluster first, or app analytics and practice history stop.
  • ZPP certificates.
  • The 7Sleep hosts (already answering 410 Gone).
  • The parity checks against gateway.7mind.de.

See platform-unification and google-cloud.