Compute Credit and Committed Use Terms

These terms (the “Committed Use Terms”) apply when a Customer pre-purchases Compute Credits under a Committed Use Agreement, whether through Console, a Service Order, AWS Marketplace, or another ordering channel.

They do not apply to a Customer using Axiom solely on an on-demand basis without pre-purchasing Compute Credits.

Committed use provides a discounted rate in exchange for purchasing a fixed quantity of Compute Credits for a fixed term. Eligible Data Loading Compute and Query Compute Charges draw down the prepaid Compute Credit balance. Storage, platform fees, and add-ons remain separate cash charges.

A monthly tolerance threshold accommodates ordinary workload variability. The standard threshold is twice the committed allowance for the Billing Period. Any estimated Burst Surcharge displayed during a Billing Period is provisional and does not constitute a final determination of liability. Axiom determines the Burst Surcharge only after the full Billing Period closes. Crossing the pace reference on an individual day does not itself create a charge. The terms below also explain top-ups, exhaustion, renewal, rollover, and early renewal.

1. Definitions

The following terms are defined as set forth below unless otherwise defined in the Agreement:

1.1 “Agreement” means the Axiom Terms of Service (the “ToS”) or similar agreement entered into by Axiom and Customer governing Customer’s use of the Service.

1.2 “Order” means a Service Order form, accepted Console order, AWS Marketplace order, private offer or CPPO, any resale transactions, or other ordering document that incorporates these terms and states the applicable commercial variables.

1.3 “Eligible Compute Charges” means the charges produced by Customer's use of the Data Loading Compute and Query Compute functions of the Service. The underlying usage is measured in the units stated in the Documentation and rated under the applicable graduated SKU schedules. Eligible Compute Charges exclude storage, platform fees, add-ons, taxes, and other cash-only charges.

1.4 “Compute Credit” means a prepaid accounting unit that may settle one U.S. dollar ($1.00) of Eligible Compute Charges. A Compute Credit is not the unit in which the underlying Data Loading or Query Compute usage is measured.

1.5 “On-Demand Compute Credit Rate” means $1.00 per Compute Credit.

1.6 “Committed Use Agreement” means an Order under which Customer purchases a stated total quantity of Compute Credits (the “Committed Compute Credits”) for a stated period (the “Commitment Term”) at a stated price per Compute Credit (the “Committed Rate”).

1.7 “Commitment Term” means the period beginning on the Commitment Start Date and ending on the fixed Commitment End Date, each as specified in the Order. Customer may select a commitment duration of twelve (12), twenty-four (24) or thirty-six (36) months. The Commitment End Date is the first monthly Billing Period boundary on or after the end of the selected duration. The Order will specify the resulting Commitment Start Date and Commitment End Date, and the Daily Committed Pace is calculated using the actual number of days between those dates.

For example, a commitment starts on October 21, 2026. Its selected 12-month duration reaches October 21, 2027. If monthly Billing Periods end on the 10th, the Commitment End Date is November 10, 2027. The Daily Committed Pace uses the resulting 385-day term.

1.8 “Billing Period” means the monthly billing period applicable to Customer under the Order. The Billing Period is distinct from the payment schedule and Compute Credit Grant Schedule.

1.9 “Daily Committed Pace” means the Committed Compute Credits divided by the total number of days in the Commitment Term.

1.10 “Tolerance Multiplier” means the multiplier used to calculate the Period Tolerance Threshold. The Tolerance Multiplier is 2.0 (200%), unless otherwise expressly specified in the applicable Service Order.

1.11 “Active Days in Period” means the number of days in a Billing Period during which the Committed Use Agreement is active. A partial first or final Billing Period includes only the days overlapping the Commitment Term.

1.12 “Period Tolerance Threshold” means the Daily Committed Pace multiplied by the Active Days in Period and then by the Tolerance Multiplier.

1.13 “Above-Threshold Compute Credits” means the greater of zero and the number of Compute Credits consumed in a Billing Period minus the Period Tolerance Threshold.

1.14 “Burst Rate” means the On-Demand Compute Credit Rate, unless otherwise expressly specified in the Order.

1.15 “Compute Credits Applied in Period” means the actual number of Compute Credits consumed from Customer's active prepaid balance to settle Eligible Compute Charges during a Billing Period. A Compute Credit Grant, Top-Up Compute Credit, expiry, or retirement is included according to its effective time. A Compute Credit that becomes available before an open Billing Period ends may be applied when that Billing Period is finalized, including to Eligible Compute Charges accumulated earlier in that Billing Period, but may not be used for or in connection with a prior closed Billing Period.

1.16 “Prepaid Above-Threshold Compute Credits” means the greater of zero and the Compute Credits Applied in Period minus the Period Tolerance Threshold.

1.17 “Burst Surcharge” means the Prepaid Above-Threshold Compute Credits multiplied by the difference between the Burst Rate and the Committed Rate.

1.18 “Service Order” means an order form issued by Axiom, fully executed by Customer and Axiom, that references the Agreement.

1.19 “Console” means the Axiom web application through which a Customer may purchase Compute Credits.

1.20 “Data Loading Compute” means the compute used to ingest Customer Data into the Service for indexing and storage. Usage of Data Loading Compute is measured in gibibytes of data loaded (“GiB”) and rated under the applicable graduated SKU schedule.

1.21 “Query Compute” means the compute capacity used to run queries and analyses against Customer Data stored in the Service. Usage of Query Compute is measured in gibibyte-hours (“GiB-hours”), representing one GiB of query-compute capacity used for one hour, and rated under the applicable graduated SKU schedule.

1.22 “Compute Credit Grant” means a grant of pre-purchased Compute Credits made under the Compute Credit Grant Schedule, excluding Top-Up Compute Credits and Rollover Compute Credits.

1.23 “Top-Up Compute Credits” means Compute Credits purchased within the Commitment Term following the initial purchase (as defined in Section 5).

1.24 “Axiom Organization” means an administrative tenancy boundary with respect to a Customer’s use of the Service.

2. Purchase, Compute Credit grants and payment

2.1 Fees for Committed Compute Credits equal the Committed Compute Credits multiplied by the Committed Rate. The fees, payment dates and permitted payment method are stated in the Order. Unless the Order states an instalment schedule, the fees are due upon execution or acceptance of the Order.

2.2 The Order will state when the corresponding Compute Credits are granted (the “Compute Credit Grant Schedule”). Committed Compute Credits are the total Compute Credits purchased for the full Commitment Term regardless of payment or grant cadence. Every grant under the Order expires on the fixed Commitment End Date.

2.3 A multi-year Order may provide for annual payment and grant instalments without changing the rate earned by the full multi-year contractual commitment. All such grants remain subject to the same Commitment End Date.

2.4 Fees for Committed Compute Credits are non-cancellable and non-refundable. Compute Credits cannot be redeemed for cash or transferred, except for the limited rollover and early renewal treatment expressly described in Sections 6 and 7 or as required by applicable law.

Notwithstanding anything to the contrary herein, the term “Compute Credit” is used throughout these terms solely as a unit of measure for tracking and allocating usage of the Services. Compute Credits do not constitute, represent, or evidence (a) a store of value; (b) a monetary instrument, currency, or cash equivalent; (c) any right, entitlement, or claim to monetary payment or reimbursement; or (d) any property interest of any kind.

Compute Credits have no independent monetary value, are not redeemable for cash or cash equivalents, and may not be transferred, sold, or assigned except as expressly permitted under these Terms. The use of the term “Compute Credit” is for administrative convenience only and shall not be construed to create any financial obligation of Axiom beyond the provision of the Services to which such Compute Credits apply.

3. Consumption and customer visibility

3.1 Each $1.00 of Eligible Compute Charges consumes one Compute Credit from Customer's available Compute Credit balance while a balance remains, regardless of the price Customer paid for that Compute Credit.

For example, $1,200 of Data Loading Compute charges and $800 of Query Compute charges consume 2,000 Compute Credits. A balance of 10,000 Compute Credits then becomes 8,000 Compute Credits. Storage, platform fees, and add-ons do not consume that balance.

3.2 For the calculations in Sections 4 and 7, every Compute Credit in the active balance—including Compute Credits added by top-up or rollover—is treated at the active Committed Rate. Historical price tranches are not maintained within one active balance.

3.3 During a Billing Period, Axiom may display usage to date, pace, balance, estimated or projected surcharge, projected exhaustion and related alerts. These values are provisional operational information, may increase, decrease, or return to zero as the Billing Period progresses, and are not an invoice or a final determination of liability.

3.4 Commercial liability for a Burst Surcharge is determined only after the relevant Billing Period closes. No daily positive or negative billing adjustment is created.

4. Period threshold and Burst Surcharge

4.1 At the close of each Billing Period, Axiom will determine the Period Tolerance Threshold, Above-Threshold Compute Credits, Compute Credits Applied in Period and Prepaid Above-Threshold Compute Credits for that Billing Period.

4.2 Eligible Compute Charges at or below the Period Tolerance Threshold consume Compute Credits normally and create no Burst Surcharge.

4.3 Prepaid Above-Threshold Compute Credits are calculated as the greater of zero and Compute Credits Applied in Period minus the Period Tolerance Threshold. This aggregate calculation excludes usage already invoiced on-demand without requiring individual usage events to be classified as prepaid or on-demand above the threshold.

4.4 Prepaid Above-Threshold Compute Credits continue to consume the Compute Credit balance and also incur the Burst Surcharge. The two amounts together produce the Burst Rate for those Compute Credits; the Burst Surcharge is only the difference between the Committed Rate already paid and the Burst Rate.

4.5 Axiom will invoice one final Burst Surcharge in cash for the closed Billing Period. It is not deducted from the Compute Credit balance.

4.6 Usage already invoiced at the On-Demand Compute Credit Rate receives no Burst Surcharge.

4.7 The result is final for that Billing Period. Lower usage within the same open Billing Period may reduce or eliminate a provisional surcharge, but usage in a later Billing Period does not reopen or offset a closed result.

For example, a Daily Committed Pace of 1,000 and 30 active days produces a standard threshold of 60,000 Compute Credits. If 70,000 prepaid Compute Credits are applied, 10,000 are above the threshold. At a $0.80 Committed Rate and $1.00 Burst Rate, the cash surcharge is $2,000.

5. Top-ups and exhaustion

5.1 During the Commitment Term, Customer may purchase additional Compute Credits at the active Committed Rate (“Top-Up Compute Credits”). Cumulative Console purchases of Top-Up Compute Credits during the Commitment Term may not exceed fifty percent (50%) of the original Committed Compute Credits.

5.2 Top-Up Compute Credits enter the existing Compute Credit balance and expire on the existing Commitment End Date. They do not change the Committed Compute Credits, Daily Committed Pace, Tolerance Multiplier, Period Tolerance Threshold, Committed Rate or Commitment End Date.

5.3 A top-up does not combine with the original purchase to qualify for a different aggregate volume tier and does not reprice the original purchase or the Top-Up Compute Credits.

5.4 A Top-Up Compute Credit becomes available when Axiom receives the applicable payment. If it becomes available before an open Billing Period ends, it may be applied to Eligible Compute Charges accumulated earlier in that Billing Period. A top-up does not reopen or recalculate a closed Billing Period, reverse a final Burst Surcharge, or reprice usage already invoiced on-demand for a closed Billing Period.

5.5 If the available Compute Credit balance reaches zero, subsequent Eligible Compute Charges accrue at the On-Demand Compute Credit Rate. If a Top-Up Compute Credit becomes available before the same Billing Period ends, it may settle those charges when the Billing Period is finalized. Any Eligible Compute Charges not settled by Compute Credits are invoiced monthly in arrears at the On-Demand Compute Credit Rate and receive no Burst Surcharge.

5.6 Exhaustion does not shorten, terminate or renew the Commitment Term and does not change the Commitment End Date.

6. Scheduled expiry, renewal and rollover

6.1 Every unused Compute Credit associated with a Committed Use Agreement—including Top-Up Compute Credits and Rollover Compute Credits—expires at the Commitment End Date unless it qualifies for rollover under Section 6.2.

6.2 If Customer enters into a replacement Committed Use Agreement effective immediately following the scheduled Commitment End Date with Committed Compute Credits equal to or greater than the expiring Committed Compute Credits, unused Compute Credits may roll into the new Commitment Term for up to twenty percent (20%) of the new Committed Compute Credits (“Rollover Compute Credits”). The following is an example of the applicable Rollover Compute Credits:

If the expiring Committed Use Agreement has 100,000 Committed Compute Credits, 30,000 Compute Credits remain unused, and Customer enters into a replacement Committed Use Agreement for 100,000 Committed Compute Credits, the rollover limit is 20,000 Compute Credits. Accordingly, 20,000 Compute Credits become Rollover Compute Credits and the remaining 10,000 unused Compute Credits expire.

6.3 Rollover Compute Credits are added to the new Compute Credit balance and expire on the new Commitment End Date. The new Daily Committed Pace and Period Tolerance Threshold are calculated from the new Committed Compute Credits only; Rollover Compute Credits do not increase pace.

6.4 If the new Committed Compute Credits are fewer than the expiring Committed Compute Credits, or Customer does not renew, all unused Compute Credits expire without refund.

6.5 If Customer does not renew, subsequent Eligible Compute Charges remain available at the On-Demand Compute Credit Rate.

7. Mutually agreed early renewal

7.1 The parties may enter into a replacement Committed Use Agreement before the scheduled Commitment End Date (an “Early Renewal”). An Early Renewal takes effect at the next Billing Period boundary stated in the replacement Order.

7.2 The expiring agreement remains unchanged until the Early Renewal takes effect. The original Daily Committed Pace will continue to apply to the expiring agreement’s final Billing Period. Axiom will close its final Billing Period normally and then determine the unused Compute Credits in the active balance (“Remaining Compute Credits”).

7.3 Solely to price the Early Renewal, the “Remaining Prepaid Value” equals the Remaining Compute Credits multiplied by the expiring Committed Rate. Remaining Prepaid Value is a non-cash price offset available only for the Early Renewal; it is not a refund, cash redemption right or transferable monetary balance.

7.4 The replacement Order must have more Committed Compute Credits than the expiring Order. Its total value (“New Commitment Value”) equals the new Committed Compute Credits multiplied by the new Committed Rate and must exceed the Remaining Prepaid Value.

7.5 The amount due for the Early Renewal equals the New Commitment Value minus the Remaining Prepaid Value, subject to the payment schedule in the replacement Order.

7.6 On the Early Renewal effective date, Axiom will retire the entire old Compute Credit balance and establish the replacement grants in accordance with the new Compute Credit Grant Schedule. No old Compute Credit is both recognized in Remaining Prepaid Value and carried forward as a unit. Scheduled-renewal rollover under Section 6 does not also apply.

7.7 The replacement Order begins one new full Commitment Term with a new Daily Committed Pace and fixed Commitment End Date. An Early Renewal creates no cash refund and does not reprice an open or closed Billing Period.

7.8 If the parties do not agree an Early Renewal, the existing Committed Use Agreement, balance, pace, surcharge treatment and Commitment End Date continue unchanged.

8. On-demand use, other charges and spend controls

8.1 In the absence of a Committed Use Agreement, and following exhaustion or expiry, Customer may continue to use the Service at the On-Demand Compute Credit Rate without a committed-use cutoff, subject to the Agreement and Customer's applicable spend controls.

8.2 Storage, platform fees, add-ons and other non-compute charges are not payable in Compute Credits and are invoiced in cash at the rates and times stated in the Documentation or Order.

8.3 Certain features in the Service may pause further cost-generating activity but do not amend the Committed Use Agreement, alter any threshold, or waive fees and liability already incurred.

9. Rates and changes

9.1 The Committed Rate, Tolerance Multiplier and Burst Rate are fixed for the Commitment Term unless the parties execute an Early Renewal under Section 7.

9.2 Published rates may change for future orders, but no published change applies to an executed Order during its Commitment Term.

9.3 Rates specified in an Order apply only to that Order and its Commitment Term. They do not carry into a renewal or replacement Order unless expressly restated.

10. One active commitment

10.1 Each Axiom Organization identified in an Order may have only one active Committed Use Agreement at a time.

11. Standard Compute Credit rates

11.1 For purposes of the rate table below, annual committed volume equals the total Committed Compute Credits multiplied by twelve (12) and divided by the selected commitment duration in months. The selected duration of twelve (12), twenty-four (24) or thirty-six (36) months is used for this rate calculation; the actual dated Commitment Term determines the Daily Committed Pace under Section 1.9.

11.2 The standard rate is determined by the row corresponding to annual committed volume and the column corresponding to the selected commitment duration. All rates in the table are stated in U.S. dollars per Compute Credit. No standard committed-use discount applies to annual committed volume below 25,000 Compute Credits.

11.3 For example, an Order for 1,200,000 Committed Compute Credits over thirty-six (36) months has annual committed volume of 400,000 Compute Credits. The applicable row is 250,000 to 499,999 and the applicable column is 36 months, resulting in a Committed Rate of $0.73 per Compute Credit and total Compute Credit fees of $876,000.