Skip to main content
Vantage integrates with your Modal account using a token ID and token secret to ingest cost data through Modal’s billing report. Vantage retrieves workspace billing data broken down by Modal object (for example, Apps), environment, compute resource (such as CPU, Memory, or a GPU type), and any tags associated with those objects. Vantage uses your Modal token ID and token secret to read workspace billing data only. Vantage cannot deploy functions, trigger executions, or perform any actions that incur costs in your Modal account. It’s best practice to create a dedicated Modal token for Vantage and rotate it according to your organization’s security policy.

​
Connect Your Modal Account

​
Prerequisites

  • You must have a Vantage Organization Owner or Integration Owner role to add or remove this integration. See the Role-Based Access Control documentation for details.
  • You need access to a Modal workspace that can create API tokens.
  • Create a free Vantage account, then follow the steps below to integrate Modal costs.

​
Create the Connection

1
Navigate to your Modal token settings.
2
Create a new token, then copy the generated Token ID and Token Secret.
Modal only shows the token secret once. Save it securely before closing the dialog.
3
From the top navigation in Vantage, click Settings.
4
On the left navigation, select Integrations > Modal.
5
The Modal integrations page is displayed. Ensure you are on the Connect tab.
6
Click Add Token and complete the integration form:
  • Token ID: Paste the Modal token ID.
  • Token Secret: Paste the Modal token secret.
  • Description: Enter a label to identify this Modal workspace in Vantage. This value is used as the Billing Account dimension in Cost Report filters.
7
Click Connect Account.
After clicking Connect Account, you will see the status of your integration change to Importing within the Vantage console. This status indicates that Vantage is actively importing your Modal cost data. Vantage backfills up to six months of historical cost data upon initial connection. Ongoing retention follows your Vantage data retention settings. See the Integration Status documentation for details on integration statuses. You can connect multiple Modal workspaces, each with its own token, as separate integrations in Vantage.
As soon as costs are processed, they will be available on your All Resources Cost Report. If you decide to remove your Modal integration from Vantage, all costs associated with that Modal token will be removed from the Vantage console.

​
Next Steps - Manage Workspace Access

Once the import is complete and the integration status changes to Stable, you can select which workspaces this integration is associated with. See the Workspaces documentation for information.

​
Data Refresh

See the provider data refresh documentation for information on when data for each provider refreshes in Vantage. Modal data refreshes once daily. On Modal Cost Reports, you can filter and group across several dimensions:
  • Billing Account (the description you enter when connecting the integration; use Billing Account for filtering and grouping)
  • Account (the Modal environment name, such as main)
  • Service (for example, App)
  • Category (the compute resource that generated the cost, such as CPU, Memory, or a GPU type, like H100, B200, etc.)
  • Resource (the Modal App; shown as the App name while the App is active, or the Modal object ID such as ap-... once the App is no longer active)
  • Charge Type (Usage)
In addition, Modal costs include the following tags, available for filtering and grouping alongside any Virtual Tags you create:

​
Active Resources

Vantage syncs your Modal Apps as Active Resources, so you can view currently active Apps and their costs in Resource Reports. Each Modal App resource includes metadata such as its name, environment, and status, along with the tags applied to it in Modal. Active resources are synced at least once every 24 hours.
In Cost Reports, the Resource for a Modal App is displayed as the App’s name while the App is active. Apps that are no longer active aren’t synced as Active Resources, so their costs show the raw Modal object ID (such as ap-...) instead.