Möbius
Launch
What Möbius Launch Stores
The launcher is a bridge between your Möbius account and your Railway-owned deployments. It keeps the minimum state needed to reconnect, resume, and delete what it created.
Stored
- Your Möbius 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, environment, volume, public URL, recovery URL, and selected resource caps.
- Short provisioning events and errors so failed launches are debuggable.
Fetched live
- Railway workspace choices and deployment status are refreshed from Railway when the page needs them.
- CPU, RAM, disk, volume, and network metrics are read on demand and not persisted as history.
- Exact billing and usage limits stay in Railway; the launcher links you to the Railway project for spend details.
Never stored
- Your Möbius conversations, files, apps, databases, or agent activity.
- Your Railway password or Google password.
- Product analytics or telemetry from inside your Möbius instance.
Backend Surface
The backend is intentionally small: OAuth callbacks, encrypted token storage, a deploy worker, and a deployment registry.