A Nebula account is the identity you use with the Nebula Launcher itself. It authenticates you against Nebula’s backend services, gives you access to the integrated mod store, and enables the launcher to download supported packages such as NebulaCompat. Without a valid account session, the launcher cannot reach these services. Your Nebula account is completely separate from your Among Us game account — see Among Us Account if you need to link that.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/Nebula-Modmakers/Nebula-Launcher/llms.txt
Use this file to discover all available pages before exploring further.
Creating an account
Open Nebula Launcher
Install and open the Nebula APK on your Android device. The login screen is shown on first run.
Tap Create Account
Select the option to create a new account and enter your email address and a password.
Verify your email
Nebula sends a verification email to the address you provided. Open that email and follow the verification link before signing in.
Signing in
Open Nebula Launcher
Launch the app. If a saved session is still valid, Nebula refreshes it automatically and takes you straight to the launcher home screen.
Enter your credentials
If no valid session exists, enter your email address and password on the login screen.
Session management
Nebula handles your login session automatically so you rarely need to think about it:- Automatic refresh: every time the app launches, Nebula attempts to refresh the saved session token against the server. If the refresh succeeds you go straight to the home screen.
- Offline grace period: if the Nebula server is temporarily unreachable, an existing valid session receives a limited grace period so you can still use the launcher offline for a short time.
- Deactivated or revoked sessions: if your account has been deactivated, or if the current device session was revoked (for example from the Authorized Devices screen on another device), the app will prompt you to sign in again. An expired or revoked session cannot use the offline grace period.
- Session limit: up to 3 device sessions may be authorized at the same time per account. If you reach the limit, sign out of an existing device or remove it from the Authorized Devices screen before adding a new one.
Authorized devices
The Authorized Devices screen lists every device that has an active session associated with your account. Each entry shows the device name and the date it was last active. Removing a device immediately deletes every active session for that device. To open it, navigate to Settings → Authorized Devices inside Nebula. Tap Remove device on any entry you no longer recognise or use. If you remove the device you are currently on, Nebula signs you out and returns you to the login screen.Signing out
Signing out sends a request to the Nebula session API to revoke the current device session, then clears all locally stored credentials and account state. Specifically, Nebula signs out of Firebase Authentication, clears the saved account preferences, and deletes the locally cached NebulaCompat runtime file. The device is deauthorized immediately. What signing out does not do:- It does not delete Among Us from your device.
- It does not remove any mod files, profiles, or BepInEx configuration.
- It does not affect other devices that have their own active sessions.
Logging out removes only the device session and the locally cached credentials. Your mod profiles, installed mod files, and generated IL2CPP assemblies all remain on the device exactly as they were.