Run your application on Australian capacity.
Choose where each job happens.
Your application runs on hosted capacity in Sydney today, and in your own environment from 2027. Every job ends in a useful result: its output files and a signed certificate anyone can verify offline.
One complete job.
Every job has a certificate. TALOS Warrant keeps the job within its limits, and TALOS Defence signs the certificate when the job ends.
Supply
You bring your application and its data.
Place
Your organisation chooses where each job happens: hosted capacity in Sydney, or your own environment from 2027.
Approve
Your organisation sets the limits and chooses who approves a new image.
Start
Start a job from the web, the command line or the API.
Run
TALOS Warrant, the part of Hangar that enforces limits, applies the limits before the job and keeps the job within them.
Certificate
You receive the output files and a certificate signed for that job. Anyone can verify it offline.
Update
A new image of your application starts only when your policy admits it.
Where jobs happen
The two forms, side by side.
Your organisation chooses where each job happens: hosted capacity in Sydney today, or its own environment from 2027.
| Aspect | Hosted in Sydney | Your own environment, from 2027 |
|---|---|---|
| Capacity | NVIDIA H100 and CPU capacity in AWS Sydney (ap-southeast-2). | Your organisation's own AWS account in ap-southeast-2. |
| Platform | TALOS Defence operates and supports Hangar. | TALOS Defence licenses and supports Hangar. Your people, TALOS Defence or a partner operate it. |
| Application | The vendor maintains its release. | The vendor maintains the same release. |
| Approval and limits | Your organisation's policy sets the limits of every job. | Your organisation approves each release and sets its limits in its own environment. |
| Data | Stays in Australia. Your outputs come back to you. | Stays in your environment, under your organisation's access control. |
| Certificates signed by | TALOS Defence keys. | Your organisation's keys. |
| Charging | Per hour and per vCPU-hour, including GST. | A licence and support. Your organisation pays for its own capacity. |
Faults
When something goes wrong.
Each fault has one answer, and Hangar gives it on every job.
| When | What Hangar does |
|---|---|
| A tag points at new bytes | Hangar runs each image by its digest. A new digest under the same tag starts only when your policy admits it. |
| A job connects to a destination its limits do not allow | Hangar refuses the connection and records the refusal on the job's certificate. |
| An instance stops during a job | The certificate records the interruption. The certificate never shows a job as succeeded when its instance was lost. |
The API
From your code.
Start a CPU job from your own service, follow it and get its signed certificate. The command line calls the same HTTPS API at api.gethangar.au.
| To | Route |
|---|---|
| Start a CPU job | POST /v1/sandboxes |
| Send it a command | POST /v1/sandboxes/{id}/commands |
| Follow its output | GET /v1/sandboxes/{id}/logs |
| Get its signed certificate | GET /v1/sandboxes/{id}/certificate |
From the command line.
The same jobs, from a terminal. Install the hangar command line and sign in with your passkey. Then book hours, start a job and verify its certificate from a script.
$ brew install talos-defence/hangar/hangar $ hangar login
$ hangar book --night 2026-10-31 --at 23:00 --hours 3
Holding Sat 31 Oct 23:00 to Sun 1 Nov 02:00 AEDT (12:00 to 15:00 UTC) for 3 h.
Charging A$104.85.
Confirmed ✓ booking HG-7K3M2Q charged A$104.85, including GST of A$9.53.
$ hangar verify HG-7K3M2Q.cert --fetch
Valid. Every check passed, including the published tree heads.