Modal logo
IntroductionCustom container images Custom containersPrivate registriesGPUs and other resources GPU accelerationReserving CPU and memoryScaling out Scaling outDicts and queuesJob processingConcurrent inputs on a single container (beta)Secrets and environment variables SecretsEnvironment variablesDeployment Managing deploymentsInvoke deployed functionsContinuous deploymentScheduling and cron jobsWeb endpoints Web endpointsStreaming endpointsWeb endpoint URLsRequest timeoutsTunnels (beta)Data sharing and storage Passing local dataVolumesMounting local files and directoriesStoring model weightsCloud bucket mounts (Beta)Network file systems (superseded)Dynamic sandboxes (beta)Reliability and robustness Failures and retriesPreemptionTimeoutsTroubleshootingSecurity and privacyIntegrations Connecting Modal to your Vercel accountOkta SSOOther topics File and project structureDeveloping and debuggingCold start performanceMemory Snapshot (beta)Modal user account setupWorkspacesEnvironmentsJupyter notebooksAsynchronous API usageGlobal variablesContainer lifecycle and parametersApps, Stubs, and entrypoints

Modal user account setup

To run and deploy applications on Modal you’ll need to sign up and create a user account.

You can visit the signup page to begin the process or execute modal setup on the command line.

Users can also be provisoned through Okta SSO, which is an enterprise feature that you can request. For the typical user you’ll sign-up using an existing GitHub account. If you’re interested in authenticating with other identity providers let us know at support@modal.com.

What GitHub permissions does signing up require?

  • user:email — gives us the emails associated with the GitHub account.
  • read:org (invites only) — needed for Modal workspace invites. Note: this only allows us to see what organization memberships you have (GitHub docs). We won’t be able to access any code repositories or other details.

How can I change my email?

You can change your email on the settings page.