Cost and credit usage for Snowflake App Runtime¶
This topic describes how Snowflake bills compute used by Snowflake App Runtime and where to track that usage.
How App Runtime compute is billed¶
Snowflake App Runtime uses a dedicated service type:
| Service type | Description |
|---|---|
SNOWFLAKE_APP_RUNTIME | Compute used to build and host Snowflake App Runtime services. |
All App Runtime apps in an account share Snowflake-managed compute. Credit
usage is billed at the account level under the SNOWFLAKE_APP_RUNTIME service
type, separate from your warehouses and other compute. Per-app cost
attribution isn’t available.
Find App Runtime usage in metering views¶
App Runtime credits appear in the same metering views that report other Snowflake compute usage:
- METERING_HISTORY: hourly credit usage for the last 365 days.
- METERING_DAILY_HISTORY: daily credit usage rolled up by service type.
For cross-account roll-ups, use organization-level metering views such as USAGE_IN_CURRENCY_DAILY.
The following query returns hourly App Runtime credit usage for the last 30 days:
Inspect App Runtime credit usage¶
For a focused view of App Runtime credit usage, query SNOWFLAKE_APP_RUNTIME_COMPUTE_HISTORY. The view returns hourly account-level credit usage for App Runtime over the last 365 days.
Reduce App Runtime cost¶
App Runtime bills compute only while apps are running. To reduce cost:
- Suspend idle apps. Use
ALTER APPLICATION SERVICE ... SUSPENDto stop billing compute for apps that aren’t in active use. - Monitor app state. Use Observability for Snowflake App Runtime to find apps stuck in unexpected states that may still consume compute.
- Drop unused apps. Use
DROP APPLICATION SERVICEto remove apps you no longer need.
See also¶
- Observability for Snowflake App Runtime: service state and logs.
- SNOWFLAKE_APP_RUNTIME_COMPUTE_HISTORY view: hourly App Runtime credit usage view.
- Understanding compute cost: general cost concepts for Snowflake compute.