Legal

Hangar Capacity Terms

Bookings, Accelerator Time, cancellation, and the credit when capacity fails.

Version 1.0. Effective date: 27 October 2026.

These terms are part of the Hangar Terms of Service. They cover how you book and use accelerator capacity on Hangar, and what happens when capacity fails. Words defined in the Terms of Service have the same meaning here.

1. What you buy#

1.1 A managed run, not an instance. TALOS Defence buys and operates all Hangar capacity in its own Amazon Web Services accounts, including EC2 Capacity Blocks. When you buy Hangar capacity, you buy the execution of your Workload on that capacity, managed by TALOS Defence, with its Certificate. You do not receive an instance, a reservation, a Capacity Block, cloud credentials, a login to the host, or access to the Infrastructure Provider's console. Nothing in this agreement leases, sublicenses or transfers any Infrastructure Provider capacity to you.

1.2 The products. Hangar sells capacity in these forms. The pricing page states each price, unit and minimum.

Product	What it is
Booked slot	A confirmed number of hours on a stated accelerator type and pool, inside a published night or block, at a fixed start time
Exclusive night	A booked night on which only your Workloads run
Instant session	Accelerator or CPU time started on request and metered by the second, when capacity is free
CPU run and sandbox session	CPU time on a fresh instance, metered by the second
Accelerator Time	Time on a Hangar-managed accelerator to run your own Workload, with Hangar's reset, isolation and Certificate, sold by the hour or by the second

1.3 Pools. A pool is a set of capacity of one accelerator type in one place. Hangar's pools are in AWS Sydney (ap-southeast-2), including NVIDIA H100, and in AWS Melbourne (ap-southeast-4), with AWS Trainium2. A booking names its pool. A Workload runs only on the accelerator type and pool it was booked on.

1.4 What a slot gets. The documentation states the instance type, memory, disk, network and limits for each product. A Workload that exceeds a limit ends, and the Certificate records why.

2. Booking#

2.1 Holds. When you choose hours, Hangar holds them, and reserves their price from your Credit, for 10 minutes. A hold costs nothing. If you do not confirm within 10 minutes, the hold lapses and the reserved Credit returns.

2.2 Confirmation. A booking exists when you confirm it in Hangar and its price is charged to your Credit. Hangar shows the confirmation and emails it to you.

2.3 Published availability. Published nights, blocks and hours show what we expect to be able to supply. Until you confirm a booking, availability can change without notice.

2.4 Start and end. A slot starts at its booked time and ends at its booked end time. Your Workload receives a stop signal 60 seconds before the end, and is stopped at the end. The changeover between customers takes place in TALOS Defence's time, not in your booked time.

3. Cancellation by you#

You cancel	What happens
A hold, before you confirm it	The reserved Credit returns at once
A confirmed booking, 48 hours or more before it starts	The full price returns to your Credit
A confirmed booking, less than 48 hours before it starts	We offer the hours for booking again. If they are booked again, we return Credit for those hours, in proportion. Otherwise, the booking is charged

We buy capacity in advance, and the Infrastructure Provider does not refund it. The 48-hour rule reflects that cost.

4. Instant sessions and metered time#

4.1 Start. An instant session, CPU run or sandbox session starts only when capacity is free. If none is free, nothing starts and nothing is charged.

4.2 Metering. Metered time runs from the moment the instance runs to the moment it is terminated, as the Certificate records. Hangar takes Credit as the time is used.

4.3 Stop. A session ends when its Workloads end, at the limit you set, when you stop it, or when your Credit runs out. Hangar warns you before a stop for Credit.

4.4 No run, no charge. If no Workload starts because the instance fails its attestation, reset or staging, the session is not charged.

5. When capacity fails#

5.1 Capacity events. A Capacity Event is any of these, if it is not caused by you or your Workload:

the Infrastructure Provider does not deliver, ends early, reclaims, interrupts or retires capacity for a booking;
the hardware, a pre-run check, the reset or the attestation fails;
Hangar fails;
we suspend a pool or the Service for security or maintenance under clause 5.4 of the Terms of Service;
an event outside our reasonable control prevents supply.

5.2 Credit back. For a Capacity Event, we return to your Credit the price of the booked or metered time that was lost. For a booking that cannot start, that is the full price. For a booking cut short, it is the price of the hours not delivered, rounded up to the next whole hour.

5.3 What we preserve. Where we can, we preserve the outputs and checkpoints that your Workload had written before the event, and the Certificate records the event.

5.4 Rebooking. Where we can, we offer you other hours. You may accept them or keep the Credit.

5.5 Refund to card. If you ask within 30 days after the Capacity Event, we refund to your card the Paid Credit returned under clause 5.2, instead of keeping it as Credit.

5.6 Your sole remedy. To the maximum extent permitted by law, and subject to clause 14 of the Terms of Service, the remedies in this clause 5 are your only remedies for a Capacity Event. We are not liable for damages, lost work, lost results or any other loss arising from a Capacity Event.

5.7 Not a Capacity Event. These are not Capacity Events, and no Credit is returned:

your Workload fails, crashes, runs out of memory or disk, or does not start because of your image, code, data or configuration;
your Workload is stopped because of a breach of the Acceptable Use Policy, or a suspension caused by you;
your Credit runs out;
a destination you rely on outside Hangar is unavailable.

6. Capacity allocation#

6.1 We allocate capacity in the order in which bookings are confirmed.

6.2 We may keep capacity for our own operations, testing, security work and support, and may choose not to offer every hour of a block.

6.3 New-account limits apply to bookings (Terms of Service clause 3.6).

7. Prices#

The price of a booking is the published price when you confirm it. Metered prices are the published price when the time is used. All prices are in Australian dollars and include GST where GST applies.