Commitment Plans
Reduce compute costs with prepaid commitments applied automatically to your On-Demand Priority workloads.
Overview
Commitment Plans let organizations prepay for compute and use it at a discounted rate for a fixed term. Once configured, savings are applied automatically to eligible On-Demand Priority (ODP) workloads. Your team continues submitting jobs as ODP with no additional steps or workflow changes.
Commitment Plans apply exclusively to On-Demand Priority workloads. On-Demand Economy (ODE) workloads are not eligible.
Two plan types are available:
- Rescale Savings Plan covers multiple coretypes under a single dollar-per-hour commitment. It is region-agnostic and applies to any eligible coretypePre-configured and optimized architectures for different HPC... More in your configured list. This is the recommended option for most organizations.
- Coretype Plan commits to a fixed number of cores on a specific coretype and region. It is designed for organizations with concentrated, predictable usage on a single hardware type.
Both plan types can be held simultaneously. Contact your account team to get started.
How Savings Are Applied
Commitment Plans use invisible orchestrationThe automated management and coordination of various computi... More by automatically finding eligible workloads and applying benefits:
- Users submit workloads as On-Demand Priority.
- The platform identifies eligible ODP workloads running against committed compute plans.
- A billing negation (“Applied Commitment”) is applied retroactively for covered hours.
There is no separate billing priority to select. Savings are calculated per hour. An eligible workloadWorkload refers to the amount and type of computing tasks or... More starting at any point during an hour receives the committed rate for that full hour up to the value the commitment allows.
Navigating Commitment Plans
Organization admins manage Commitment Plans under Financials → Commitment Plans.
The management page displays all active commitments with their type, status, commitment details, term, queueA list of jobs waiting to be processed by an HPC system. Que... More policy, and workspaceWorkspaces allow rescale customers to create dedicated teams... More scope.
Commitment Burst Policy
The commitment burst policy controls what happens when committed capacity is full and a new job is submitted. Admins can configure the policy per commitment.
| Mode | Behavior |
|---|---|
| Immediate | Job launches at On-Demand Priority rates. No waiting. |
| Balanced | Job waits a configured period (30 min to 6 hours) for committed capacity, then launches at On-Demand Priority rates. |
| Savings Required | Job waits up to 24 hours for committed capacity. Cancelled automatically if capacity does not open. |
Scope:
- Jobs: policy applies at launch.
- HPS: always launches immediately, regardless of policy.
- Workstations: not affected by policy. Launches and resumes always proceed immediately.
Commitment Plan Badge
When an active Commitment Plan covers a coretype, users see a commitment plan badge in the coretype list during job setup. The badge appears where the On-Demand Priority indicator would normally display.
The badge displays:
- Remaining committed capacity (e.g., “108 / 324 cores available”)
- The active burst policy behavior (e.g., “Policy runs excess workloads immediately at On-Demand Priority rates”)
Users can hover over the badge to see full policy details. This helps users select coretypes that maximize their plan utilization.
The displayed price is always the On-Demand Priority rate. Savings are applied retroactively in billing.
Understanding Commitment Plan Utilization
The Utilization Dashboard shows how committed capacity is being consumed over time.
Navigate to Financials → Commitment Plans → Utilization Dashboard.
The dashboard displays:
- Utilization rate for the selected period
- Hourly or daily usage plotted against the commitment ceiling
- Filtering by month and by specific commitment
Job Management
The Jobs dashboard includes a By Commitment Plan view, which groups active and pending jobs by the commitment they are eligible to consume. For each commitment, the view shows:
- Remaining cores available
- Number of pending jobs
Note: Jobs shown as Pending in this view are not guaranteed to be covered by the commitment. Pending jobs may burst to ODP rates depending on the queue policy in effect. Additionally, jobs that are eligible to be covered by multiple plans will appear under all plans.
Workspace Scope
Commitments can be applied to all workspaces in the organization or restricted to specific workspaces. When restricted, only workloads from listed workspaces are eligible to consume committed capacity.
Configure workspace scope from the commitment detail view under Financials → Commitment Plans.
Billing
All workloads generate charges at the standard On-Demand Priority rate. The platform applies a retroactive negation for hours covered by the commitment at the workload level.
| Column | Description |
|---|---|
| Compute | Standard ODP charge |
| Applied Commitment | Negative value representing the covered portion |
| Net | Actual cost after commitment savings |
Partial Coverage
If a workload uses more capacity than the commitment can cover, the covered portion receives the commitment discount and the remainder is billed at On-Demand Priority rates. For example, a job using 80 cores against a 54-core Coretype Plan commitment: 54 cores are covered by the commitment, 26 cores are billed at ODP. The split is visible in workload-level billing detail.
Platform License
The Rescale platform license is metered based on actual usage. You are only charged for hours consumed, not for idle committed capacity.
Rescale Savings Plan
Rescale Savings Plan establishes a dollar-per-hour commitment across a broad selection of coretypes. Organizations commit to a $/hr spend for a set term (1 or 3 years), triggering automated discounts on eligible compute costs up to that hourly threshold. The specific discount percentage is coretype-dependent, reflecting the distinct economic profile of the underlying infrastructure.
Admins manage these plans via Financials → Commitment Plans. The active commitment view details the hourly commitment level, specific eligible coretypes, plan duration, active queue policy, and workspace scope.
Commitment Parameters
Every Savings Plan defines the following:
- $/hr commitment: the hourly dollar amount pledged.
- Eligible coretypes: the specific hardware families covered by the plan.
- Term: the 1-year or 3-year commitment duration (longer terms provide deeper savings).
Discount Mechanism
A dedicated discount percentage for each eligible coretype determines the portion of the On-Demand Priority charge covered by the commitment. These rates are influenced by coretype, region, operating system, and plan term. For eligible workloads, the platform applies a retroactive negation to the billing record, effectively lowering the net compute expense.
The commitment pool is consumed based on these negated dollar amounts. If the hourly commitment is exhausted, subsequent workloads within that same hour are billed at standard On-Demand Priority rates.
Regional Support
Savings Plans are inherently region-agnostic, allowing workloads in any cloud region to qualify for coverage. Unlike Coretype Plans, there is no requirement for a Regional Availability toggle.
Accessing Discount Rates
Organization admins can review the specific discount ranges for all eligible coretypes within the commitment details. Displayed rates correspond to the active plan term.
Coretype Plan
Coretype Plan commits to a fixed number of cores on a specific coretype, region, and term. ODP workloads running against available committed cores are covered at no additional compute cost.
Key characteristics:
- Designed for concentrated, predictable usage on a single coretype
- Region-specific: workloads are pinned to the committed region by default
- Each Coretype Plan specifies:
- Coretype — the specific hardware family (e.g., Emerald)
- Corean individual processing unit within a multicore processor o... More count — the number of cores reserved under the plan
- Region — the cloud region where the commitment is active
- Term — the duration of the commitment (e.g., 1 year)
- OS — the operating system eligible for the commitment
Regional Expansion
By default, workloads are pinned to the committed region to maximize commitment utilization. Workloads submitted to a different region are not eligible for the commitment and are billed at standard ODP rates.
Admins can enable the regional expansion toggle on a commitment. When enabled, if committed capacity is full, workloads can launch in other available regions at On-Demand Priority rates rather than waiting per the queue policy. This is useful when the committed region experiences capacity constraints.
When regional expansion is off and committed capacity is full, workload behavior is determined by the queue policy (Immediate, Balanced, or Strict).
Using Both Plan Types
Organizations can hold both a Savings Plan and a Coretype Plan:
- Coretype Plan applies first to matching workloads (more restrictive scope).
- Savings Plan applies to the remaining eligible usage.
This is useful when an organization has one dominant coretype (covered by Coretype Plan) and a diverse tail of other workloads (covered by Savings Plan).
Getting Started
Commitment Plans are available on Rescale today.
- Contact your Account Executive to discuss your workload profile and commitment sizing.
- Rescale configures the commitment based on the agreed-upon plan type, size, and term.
- Your team runs workloads as usual. Savings begin immediately.
For questions, contact your Account Executive or reach out to support@rescale.com.
FAQs
Does a Commitment Plan guarantee capacity?
No. Commitment Plans are a billing mechanism. They do not reserve or guarantee infrastructure capacity.
Which workloads are eligible?
Only On-Demand Priority (ODP) workloads are eligible, including Jobs, Workstations, and HPSes. On-Demand Economy (ODE) workloads are not covered by Commitment Plans.
Can I have multiple Commitment Plans?
Yes. An organization can hold multiple active commitments of different types, coretypes, or regions. Each is managed independently.
What term lengths are available?
1-year and 3-year terms are available. Longer terms offer deeper discounts.
What happens if I don’t use my full commitment?
Commitment capacity is use-it-or-lose-it per hour. Unused capacity in a given hour does not roll over. The utilization dashboard helps you track consumption and right-size your commitment.
What happens if my workload exceeds the commitment?
The portion within the commitment is covered at the discounted rate. The excess is billed at standard On-Demand Priority rates. This partial coverage is visible in workload-level billing detail.
Can I change my commitment after purchase?
Commitment parameters (size, term, coretype) are fixed at purchase. Your Account Executive can help plan for the next term. For Rescale Savings Plan, the eligible coretype list can be updated without a new contract.
Do end users need training?
No. End users submit workloads as On-Demand Priority with no change to their workflow. The commitment policy badge at job setup indicates available capacity and the active policy, but no training is required to use it.