Budget

tip

Available only when Hybrid Cloud is enabled in FCP-Suite. Disabled by default.

Go to Billing Management > Budget from the left menu. This page allows administrators to set budget caps to limit platform spending and prevent cost overruns caused by excessive resource usage. It supports two types of budgets: global budgets and user budgets.

Global budget

Click Create global budget at the top-left. Fill in the form and confirm to activate. A global budget applies to all users on the platform and must be created by an administrator.

Field descriptions

• Total: Total amount of the global budget.
• Budget type: One-time budget or recurring budget.
• One-time: A one-time allocated budget.
• Recurring: Budget allocated on a recurring schedule: week, month, quarter, or year (calendar-based).
• Start time: When the budget becomes effective.
• End time: When the budget ends. If not set, the budget remains effective indefinitely.
• Budget alert: Off by default. When enabled, you can configure alerts by budget usage percentage.
• Status:

  Status	Color	Description
  Not effective	Dark gray	The budget has not reached its start time yet.
  Expired	Gray	Current time is past the end time. Alerts that occurred while effective will no longer trigger after expiration.
  Exceeded	Red	While effective, spending has exceeded the total budget.
  Effective	Green	Alerts are disabled and the budget is currently effective.
  No alert	Blue	Alerts are enabled and the budget is effective, but the alert threshold has not been reached.
  Triggered	Orange	Alerts are enabled and the budget is effective, and the alert threshold has been reached.

User budget

Click Create at the top-right. Fill in the form and confirm to activate. A user budget applies to a specific user and can be created by the user or an administrator.

Field descriptions:

Same as global budget.

Note: A user can have only one budget entry. If either the global budget or the user budget reaches its threshold, budget control is triggered.

Budget control

• Spending scope: The consumed amount includes compute costs for pay-as-you-go nodes and storage costs associated with all compute resources.
• Remaining amount: Remaining = Total - Consumed. Budget control is not triggered when remaining amount > 0.

After budget control is triggered, existing clusters can continue to run, but you cannot add pay-as-you-go nodes.

Budget control behavior:

Type	Behavior
Existing clusters	Autoscaling will no longer start new dynamic nodes.
Existing clusters: add nodes / add partitions	Cannot add dynamic nodes.
Existing clusters: power on nodes	Allowed.
Create task/cluster/desktop	Cannot create using dynamic nodes.
Host Management: create nodes	Cannot create pay-as-you-go nodes.

Budget alerts

Permissions

• Administrators can configure budget alerts. Regular users do not have permission.

Field descriptions

• Percentage thresholds: You can configure multiple thresholds, up to 10.
• Notification frequency: Trigger-only, daily, or weekly.
• Notification method: Email addresses, up to 50.

Editing notes

• After editing thresholds, frequency, or recipients, email alerts will be re-triggered.

In-app notifications

• Recipients
  • Users receive in-app notifications when budget alerts are configured.
  • For global budget alerts, only administrators receive notifications.
• Trigger conditions
  • If you click Do not remind again, the notification will not pop up again.
  • Notifications pop up when thresholds change (updates about every 15 minutes).
  • After clearing browser cache, all in-app notifications (including those previously marked as "Do not remind again") will pop up again.
• Email notifications
  • Email alerts are sent when a configured percentage threshold is reached.
• Known issues
  • Due to cost calculation delays, budget alert emails are for reference only.