Modal logo
IntroductionCustom container images Defining ImagesUsing existing container imagesNamed imagesFast pull from registryGPUs and other resources GPU accelerationUsing CUDA on ModalConfiguring CPU, memory, and diskScaling out Scaling outInput concurrencyBatch processingJob queuesDynamic batchingMulti-node clusters (Beta)Deployment Apps, Functions, and entrypointsManaging deploymentsInvoking deployed functionsContinuous deploymentRunning untrusted code in FunctionsModal Sandboxes SandboxesRunning commandsNetworking and securityFile accessSnapshotsPricing and resourcesVM Sandboxes (Alpha)Modal NotebooksSecrets and environment variables SecretsEnvironment variablesScheduling and cron jobsHTTP Applications ServersWeb FunctionsStreaming endpointsWeb Function URLsRequest timeoutsProxy TokensModal Auto Endpoints EndpointsEndpoint metricsBenchmark an endpointNetworking TunnelsProxies (Beta)Cluster networkingData sharing and storage Passing local dataVolumesStoring model weightsCloud bucket mountsDictsQueuesDataset ingestionPerformance Cold start performanceMemory SnapshotsHigh-performance LLM inferenceReliability and robustness Failures and retriesPreemptionTimeoutsGPU healthTroubleshootingSecurity and privacy Security and privacyCustomer-supplied encryption keysAudit logsIntegrations Using OIDC to authenticate with external servicesConnecting Modal to your Datadog accountConnecting Modal to your OpenTelemetry providerOkta SSOCustom SAML SSOSlack notifications (Beta)Workspace & account settings WorkspacesEnvironmentsModal user account setupService usersRole-Based Access Control (RBAC)BillingOther topics Feature maturityJavaScript/Go SDKsModal 1.0 migration guideFile and project structureDeveloping and debuggingDeveloping Modal code with LLMsJupyter notebooksAsynchronous API usageGlobal variablesRegion selectionContainer lifecycle hooksParametrized functionsDynamic function configurationS3 Gateway endpointsGPU Metrics

Budgets

Modal budgets let you cap spend at both the workspace and environment level:

  • Workspace budget: a monthly cap for total workspace spend across the workspace.
  • Environment budget: a monthly cap for compute spend in a specific environment.

Only Workspace Owners and Managers can set, edit, or remove budgets. See Workspace roles for role details.

When to use each budget 

  • Use a workspace budget when you want one overall monthly cap for the workspace.
  • Add environment budgets when multiple teams or workloads share a workspace and need independent spend guardrails.
  • Keep both enabled when you want per-environment isolation without losing a workspace-wide hard cap.

How limits apply 

Workspace and environment budgets are enforced together:

  • The workspace budget is the hard outer cap for the entire workspace.
  • If an environment has no explicit budget, it inherits the workspace effective limit.
  • You cannot set an environment budget to a value that exceeds the workspace effective cap.
  • Environment budgets do not need to sum to the workspace budget.

Example: if your workspace budget is $50, setting environment budgets of $30 and $40 does not raise the workspace cap. The workspace can still hit $50 first, without hitting either environment budget.

Workspace budgets 

Workspace budgets cap total spend for the workspace during the current billing cycle.

You can set, edit, or remove a workspace budget on the Usage & Billing page.

The maximum budget you can set depends on prior successful charges for the workspace. If incremental usage charges succeed, that maximum can increase.

Environment budgets 

Environment budgets cap compute usage for a single environment within the same billing cycle. Note that this means it does not include all workspace-level charges (for example, storage and reservations), so environment budget usage is not a full invoice total by itself.

You can set, edit, or remove environment budgets on the Workspace Management → Environments page.