Publish
The Publish button in the editor toolbar gives you a single place to deploy your app, set a custom URL slug, toggle public access, and get AI help with deployment errors. When your app is published, a Copy link button appears, allowing you to quickly copy your deployment URL to share with users.Share
The Share button lets you manage access to your app with granular role-based permissions (Admin, Editor, Viewer). Add team members by email and control what they can do.Public and Private Apps
Deploy apps publicly (no authentication required) or privately (auth-gated). Public apps are accessible to anyone with the URL. Private apps require users to sign in and have the appropriate permissions.Disabling public apps
Available on the Enterprise plan. Only organization admins can change this setting.
- Go to Organization Settings > Organization.
- Turn on Disable public apps.
- Review the list of apps that will be made private, then click Disable public apps to confirm.
- No app can be made public. The Public access toggle is hidden from the app’s share panel, and the Access filter is hidden from the apps library.
- Requests to make an app public fail with the error “Your organization has disabled public apps.”
Login Redirects
When a user visits a private app while logged out, Major redirects them to sign in. After they log in, they’re redirected back to the app they originally visited. This works with both custom slug-based hostnames (e.g.,my-app.apps.prod.major.build) and hash-based hostnames.
Custom URL Slugs
When deploying for the first time, you can choose a custom subdomain for your app (e.g.,my-app.apps.prod.major.build). Existing apps can update their URL slug in application settings.
Per-User OAuth in Deployed Apps
If your app uses resources configured for per-user authentication, Major automatically enforces an OAuth gate. When a user accesses the app without a connected OAuth account, they’re redirected to the/connect page to authorize access.
Users can manage their connected accounts from Settings > Connected Accounts.
See Per-User OAuth for details on how this works.
Stop When Idle
Apps built on the Vite-Hono template can stop their backend while nobody is using them. Open the app’s Scaling tab and use the Stop when idle switch on the deployed app.- When it’s on, the backend stops after 15 minutes without traffic. While it’s stopped, it costs nothing.
- The next request starts it again. That first request takes a few seconds; requests after it are served as normal.
- New Vite-Hono apps have it on by default. Turn it off to keep the backend always running.
- Changing the switch redeploys the app.