Summary: The 2026 “Platform unification” project that moved 7Mind off its own Elixir backend on Google Cloud onto the 7NXT platform (the Gymondo backend on AWS). Production cutover was Monday 2026-09-14. Read this first when anything about the 7Mind backend looks inconsistent. Sources: Notion “Platform unification” hub, “Project Preface”, “High Level Task Overview”, “Platform unification Q&A”, “Migration Bug Status, Summary for CTO (23 Sep 2026)”, CRM “7Mind Migration”; Slack 7nxt-platform-unification, 7mind-7nxt-platform-unification, 7m_product-team-public, pr_7mind_sunsetting-7sleep-app; code in Gymondo-git/function-sevenmind-legacy-gateway, Gymondo-git/terraform, sevenmind/backend, sevenmind/website-next-js, sevenmind/7mind-mobile-apps-monorepo; default branches re-read on 2026-11-09 (gateway commit 8905d51, backend git log to 2026-10-29 and terraform/environment/staging/RETIRED.md, infrastructure foundation/rudderstack.tf, app rudderstack_analytics.dart and products_api_client.dart, archive status of the Gymondo-git service-* repos) Last updated: 2026-11-09


What happened

7Mind is part of the 7NXT group, together with Gymondo (fitness) and Buddyfit. In 2026 the group folded 7Mind’s backend into the shared 7NXT platform that already powers Gymondo, the same way Buddyfit had been migrated before. The stated goal (Notion “Project Preface”, 2026-04-15) was to “reduce operational complexity, consolidate tooling and infrastructure, and build a single, scalable foundation” while keeping the 7Mind apps and website visually and functionally intact.

Before: one Elixir/Phoenix modulith (elixir-backend) on GKE in Google Cloud served users, auth, subscriptions (Chargebee), content, practice history, insurance flows and 7Sleep.

After: the 7Mind app and website still call the old API paths on magic.7mind.*, but those hosts now point at the Gymondo edge on AWS, where a translation layer (function-sevenmind-legacy-gateway) fulfils each call with Gymondo services. See gymondo-platform for the target architecture.

Timeline

DateEvent
2026-01-22Kickoff, Slack 7nxt-platform-unification created (lead: Matias Olocco)
2026-01-30sevenmind GitHub org joins the 7NXT GitHub Enterprise as a separate organization (date not verified; github-actions dates the 7Mind engineers’ loss of org admin rights to around 2026-07-29, also not verified)
2026-02/03Unrelated to the migration but often confused with it: 7Mind moved its own workloads from the old GKE cluster (project mind-f62c0) to the Terraform-managed application-cluster in sevenmind-infrastructure
2026-06-17First rolling migration round (backoffice mapping, statistics events, backwards compatibility)
2026-07-08function-sevenmind-legacy-gateway repo created; domains go live on test one by one through August
2026-07-317Mind web app (meditation player on app.7mind.de) sunset; the path redirects to www.7mind.de/web-app
2026-08-13Decision to sunset 7Sleep
2026-08-18All 7Mind website domains served by the Next.js site on Cloudflare Pages (website-next-js), replacing nuxt-website
2026-09-09Staging (magic.6mind.de) already on the new backend
2026-09-13App 4.0.0, the migration release: Chargebee removed, store in-app purchases (MIND-663)
2026-09-14Production cutover. All users logged out and all tokens revoked; magic.7mind.* added to the Gymondo CloudFront distribution; login and checkout move to app.7mind.de; 7Sleep customers migrated to 7Mind the same day. Finished around 19:00
2026-09-14 to 16CRM rebuilt Braze automations on the Gymondo event schema
2026-10-05Content catalogue served from an S3 artifact in production (TP-587); anonymous analytics sent straight to Rudderstack (TP-602)
2026-10-06The 7Sleep API on the Elixir backend answers 410 Gone, except its Chargebee webhook (TP-604)
2026-10-07The gateway stops falling back to the Elixir content channel and refuses to start without the artifact (TP-606). The Algolia reindex moves to the catalogue builder. The Elixir staging plane on GKE is destroyed
2026-10-12The Insurances and Mondia Pub/Sub subscribers in the Elixir backend are retired

Ticket prefixes: MIND-* are 7Mind tickets in Linear (project “Backend Migration Bugs”), TP-* are Gymondo platform tickets in Jira.

What moved where

ConcernBeforeNow
API host for app and webmagic.7mind.* on ElixirSame host, now CloudFront, Kong and function-sevenmind-legacy-gateway on AWS
IdentityElixir-native sessions (backend_session cookie, Postgres)Gymondo SSO on AWS Cognito. See gymondo-sso-auth
User id7Mind UUIDNumeric Gymondo id. The old UUID is kept as legacyUuid
SubscriptionsChargebee (web), FastSpring (legacy), store receiptsGymondo subscription service (function-subscription; /service-subscription is its Kong route prefix, the service-subscription repo is archived). Web checkout uses Adyen, the app uses store in-app purchases. Existing Chargebee and FastSpring subscriptions continue as “shadow” records. See subscription-billing
Web login, signup, checkoutNuxt site and Chargebee checkoutfrontend-public-pages on app.7mind.de
Marketing websitenuxt-website on GKEwebsite-next-js on Cloudflare Pages (still Storyblok)
ContentContentful, rendered by ElixirStill 7Mind’s Contentful space, rendered by an Elixir “catalogue builder” Lambda to S3, served by the gateway
SearchAlgoliaStill Algolia; the gateway mints the scoped key
Practice history, stats, streaksElixir practice domainGymondo function-statistic and function-target, fed by Rudderstack events through service-event-broker. The app still sends those events through the rs.7mind.de proxy on GKE
FavouritesElixirGymondo function-favorite (DynamoDB). /service-favorite is its Kong route prefix; the service-favorite repo is archived
Insurance and prevention accessElixir monetization and prevention domainsVoucher redemptions in Gymondo, which is now the entitlement authority
ZPP certificatesElixir prevention domain on GCPNot migrated; still on GCP
Admin panel7Mind admin panel (LiveView, Admin Panel 2)Gymondo backoffice (private-backoffice.service.prod.gymondo.io, AWS VPN). The old admin panel is still readable and used for UUID lookups
BrazeSame account, 7Mind event schemaSame account, Gymondo event schema; external id is now the numeric id
ReportingLooker on BigQueryTableau (7NXT); the BigQuery tables are to be deprecated after validation
7SleepSame Elixir backendProduct sunset; customers moved to 7Mind

What is still on the old stack

The Elixir backend and Google Cloud are not shut down. As of 2026-11-09:

  • rs.7mind.de is a live client-facing dependency on GCP. It is a reverse proxy on the GKE application-cluster that forwards to RudderStack’s hosted data plane. The app sends all its RudderStack events there, including the practice events that feed Gymondo function-statistic (history and streaks). Switching off GKE without moving this host first breaks app analytics and practice history. See google-cloud.
  • elixir-backend still runs on GKE, production only: its staging plane was destroyed on 2026-10-07. The gateway no longer falls back to it for content (TP-606); its channel on gateway.7mind.de is kept as the parity reference until GCP is switched off.
  • ZPP certificate generation (zpp-certs.7mind.de), the old admin panel, Cloud SQL, Pub/Sub, and the 7Sleep hosts (backend.7mind.de, magic.7sleep.de, answering 410 Gone since 2026-10-06) are still on GCP.
  • No shutdown date for the GKE clusters or the GCP project is recorded anywhere.
  • sevenmind/infrastructure (Terraform for Cloudflare DNS and GKE) is drifted: it still declares magic.* as a CNAME to GKE, but the records were repointed to Gymondo outside Terraform. See terraform.

Gotchas for agents

  • Do not derive current behaviour from the Elixir code. For any request the app or website makes to magic.*, the answer comes from the gateway. Check the gateway README’s endpoint table, or curl staging (magic.6mind.de, app.6mind.de/api).
  • The old API contract is frozen. Installed app builds cannot be updated, so the gateway must answer the old paths and payload shapes exactly. New clients may call Gymondo APIs directly. The app already does: password reset on app.7mind.de/api, and store products and receipt sync (/api/v3/sevenmind/products/{platform}, /api/v4/sevenmind/receipts/google/sync, /api/v1/sevenmind/receipts/transactions) on magic.7mind.de, where Kong sends them to Gymondo services, not to the gateway.
  • Two user ids exist. Anything keyed by user id (local storage, analytics identities, consent, Aury) can break across the switch. See gymondo-sso-auth.
  • A migrated user only gets a Cognito record after their first login on the new platform.
  • Changes to checkout are cross-brand now. frontend-public-pages serves Gymondo, Buddyfit and 7Mind, so checkout changes need agreement with the Gymondo web team.
  • Gift vouchers are no longer supported. The decision was to drop them with Chargebee, not to fix them.
  • No per-user locale yet in the new backend (as of 2026-09-14).

Where bugs and decisions live

  • Linear project “Backend Migration Bugs” (linear.app/7mind)
  • Notion “Migration Bug Reports” and the CTO bug status summaries of 21 and 23 Sep 2026
  • Notion “Platform unification” hub and its Q&A database
  • Slack 7mind-7nxt-platform-unification (day-to-day), 7nxt-platform-unification (platform side)