Summary: The 7NXT platform (the Gymondo backend) that has served 7Mind since 2026-09-14: Go microservices and a Java monolith on AWS, behind CloudFront and Kong, multi-tenant by vendor (GYMONDO, BUDDYFIT, SEVENMIND). Sources: Gymondo-git/terraform (workspaces apps, service-cloudfront, app-sevenmind-catalogue-builder), Gymondo-git/kubernetes-apps (docs/kong-migration.md), Gymondo-git/actions, READMEs of the function-* and service-* repos, Gymondo-git/function-sevenmind-legacy-gateway README; apps service-prod.tfvars (favorite, statistic and subscription entries) and the archive status of the service-* repos, read on 2026-11-09 Last updated: 2026-11-09
Where it lives
- GitHub org:
Gymondo-git. 7Mind’s own orgsevenmindis a separate organization in the same 7NXT GitHub Enterprise. App and website repos stay insevenmind; platform code (gateway, frontends, terraform) is inGymondo-git. - Cloud: AWS, region
eu-central-1. Separate accounts for prod (service) and test. - Environments:
prodandtest(some repos also havestage). 7Mind staging maps to Gymondo test:app.6mind.de,magic.6mind.de,*.service.test.nvmind.io.
Request path
client -> CloudFront -> ALB -> Kong -> Lambda (function-*) or EKS service (service-*, Gymondo-2.0, frontends)
- CloudFront carries the 7Mind hostnames (
app.7mind.*andmagic.7mind.*for .de, .es, .fr, .it, .app, .ca, .co.uk) on the default distribution. Path behaviours (sevenmind_gateway_path_patterns, TP-537) send the legacy 7Mind API paths (/user_identity/*,/user/password/*,/user/signout,/content/*,/practice/*,/prevention/*,/monetization/*,/ai_companion/*,/config/search,/insurances/*,/analytics/*) to Kong with TTL 0. Defined in Gymondo-git/terraform workspaceservice-cloudfront. - Kong Enterprise 3.9, DB-less, managed by the Kong Ingress Controller and connected to Kong Konnect (EU). There is a public and a private gateway (
private-gateway.service.prod.gymondo.io). On protected routes Kong validatesx-access-tokenwith the openid-connect plugin, rotates tokens fromx-refresh-token, and injectsx-userinfo. Kong also answers CORS; the 7Mind origins are allow-listed in Gymondo-git/kubernetes-apps. - Kong invokes Lambdas with API Gateway v1 events. Some READMEs still say “API Gateway”; that is legacy wording.
Compute
- Lambdas (
function-*): Go,provided.al2023, arm64, container images in ECR. They hold no infrastructure of their own: every Lambda, its Kong routes and its SNS/SQS wiring are declared in Gymondo-git/terraformworkspaces/apps/*.tfvars(about 188 apps in prod). - EKS (
resource-kubernetes): long-running services such asGymondo-2.0(Java/Spring monolith,service-rest-apiandgpscheduler),service-event-broker,service-searchand frontend-public-pages.
Multi-tenancy
Every service resolves a vendor: GYMONDO, BUDDYFIT or SEVENMIND. Sources, in order: the /api/vX/{vendor}/ path prefix, x-forwarded-host, and the User-Agent. Host aliases 7mind, 6mind and nvmind all resolve to SEVENMIND. Roles and premium status are computed per vendor from subscription plans whose product vendor matches. When adding a 7Mind feature to a Gymondo service, the vendor scoping is usually the first thing to check.
Services that serve 7Mind
| Service | What it does for 7Mind |
|---|---|
| function-sevenmind-legacy-gateway | Answers the old 7Mind API on magic.7mind.* by calling the services below |
function-sso | Cognito-backed sign-in, sign-up, social login (Apple, Google, Facebook), magic link, password reset, user migration trigger, 7Mind-branded reset emails in five languages. See gymondo-sso-auth |
function-user | User records (MySQL), per-vendor roles, scheduled account deletion |
function-subscription (Kong prefix /service-subscription) | Subscription state; mirrors cancellations back to Chargebee and FastSpring for legacy subscriptions. The service-subscription repo is archived, though terraform still declares a subscription-legacy service next to the Lambda |
function-payment | Adyen web payments, keyed by vendor; ingests legacy Chargebee and FastSpring webhooks as shadow transactions |
function-app-store-receipt | Apple, Google and Amazon receipt sync; bundle ids de.7mind*, de.sevenmind*, de.seven_mind* map to SEVENMIND |
function-voucher, function-partner | Voucher redemption (insurance and partner activations), partner registration, Mondia notifications |
Gymondo-2.0 | Store products, partner subscriptions by voucher, prevention rewards, onboarding and preferences, cancellation reasons |
service-event-broker | Receives 7Mind Rudderstack events on /api/v1/{vendor}/events/sevenmind and publishes them to SNS |
function-statistic (Kong prefix /service-statistic), function-target | Meditation history and stats; daily meditation target that powers streaks |
function-favorite (Kong prefix /service-favorite) | Favourite meditations and, since 2026-11-06, whole courses as programs (DynamoDB). The service-favorite repo is archived |
function-braze-event-handler | Braze events, one API key per vendor |
terraform-workspace-service-gateway | BFF “gateway” Lambdas on /train/api; 7Mind store SKUs (multi.7mind.sub.*) |
static-webapp-backoffice | Multi-vendor customer-service backoffice |
frontend-public-pages, frontend-core | 7Mind login, signup, checkout, password pages and the 7Mind theme |
app-sevenmind-catalogue-builder (terraform workspace) | Elixir Lambda that renders the 7Mind Contentful catalogue to S3 every 30 minutes and reindexes Algolia daily |
Several Kong route prefixes keep the names of retired service-* repos (/service-subscription, /service-statistic, /service-favorite). Look up the code by the terraform app entry, not by the prefix.
Not 7Mind, despite the names: frontend-seven-nature-app is the separate Oja Balance app, and frontend-prevention-program is Gymondo’s own ZPP fitness courses.
Event bus
service-event-broker publishes to an SNS “messages” topic. Each consumer function has its own SQS queue with an SNS filter policy on service, resource and action, declared as queue and dispatcher blocks in the terraform tfvars. This replaces Google Pub/Sub and Broadway from the old stack (backend-event-bus).
Data stores
MySQL on RDS (users, subscriptions), MongoDB/DocumentDB (payment), DynamoDB (SSO user info, partner, favourites), Elasticsearch (Gymondo search), ElastiCache, S3, Secrets Manager. 7Mind keeps Algolia for search and its own Contentful space.
CI/CD
- Lambdas: GitHub Actions with the shared reusable workflow
Gymondo-git/actions/.github/workflows/function.yaml(build, push to ECR,aws lambda update-function-code, Slack notification). Usually triggered by manual dispatch. - EKS workloads: Argo CD (app of apps) syncs Gymondo-git/kubernetes-apps; image bumps arrive as automated “update config” PRs.
- Terraform: applied by hand per workspace with
make. - Some older repos (for example frontend-public-pages) still build through Jenkins.
Observability
New Relic (log ingestion and APM), CloudWatch alarms, Prometheus. Datadog, which the old 7Mind stack used, does not cover the Gymondo side.
Related
- platform-unification — how and when 7Mind moved here
- function-sevenmind-legacy-gateway — the entry point for 7Mind traffic
- gymondo-sso-auth — identity on this platform
- subscription-billing — payments and subscriptions on this platform
- infra-overview — how this fits with the remaining Cloudflare and GCP pieces