Mobius

Launch

What Mobius Launch Stores

The launcher is only a bridge between your Mobius account and your Railway-owned deployments.

Stored

  • Your Mobius Launch account email, name, sign-in provider, and avatar URL when available.
  • An encrypted Railway OAuth token so deployments can be created and refreshed.
  • Deployment metadata: Railway project, service, volume, public URL, chosen auth mode, and volume size.
  • Short provisioning events and errors so failed launches are debuggable.

Not stored

  • Your Mobius conversations, files, apps, databases, or agent activity.
  • Your Railway password or Google password.
  • Billing data; Railway owns that relationship directly.
  • Product analytics or telemetry from inside your Mobius instance.

Backend Surface

The minimum backend is an OAuth callback, an encrypted token store, a deploy worker, and a small deployment registry. Open-sourcing this service is the cleanest way to make that claim inspectable.

OAuth callbacks Encrypted tokens Template deploy worker Deployment registry