Docs
Install the hangar command line, sign in, start your first job and verify its certificate. On a fresh machine it takes under five minutes.
$ brew install talos-defence/hangar/hangar $ hangar login
/
Start
4 pages
QuickstartQuickstart. Quickstart takes you from nothing to a verified GPU job in three commands. A job uses your prepaid credit: an NVIDIA L4 costs A$4.55 an hour including GST, charged by the second.The hangar command lineThe hangar command line is a program that runs your software on GPUs and CPUs in Australia from your terminal. Each job ends with a certificate that you can verify on your own machine. A container is your software packaged with everything that it needs. You pay from prepaid credit for each job that you start.What a booking getsA slot gives you one GPU instance for the booked window, and nobody else uses it. You pay for the booked hours, including GST, from prepaid credit.GPU types and hoursGPU types. Hangar offers four GPUs in Australia, and this page shows the command that starts each one. You pay from prepaid credit at the price of the GPU, including GST: A$1.35 an hour for a fractional L4 and A$4.55 an hour for an L4, by the second. An H100 or a Trainium2 costs the price that hangar status shows, by the minute.
Jobs and images
6 pages
Jobs and the APIJobs and the API. The Hangar API lets a program start jobs, follow them and download the results. Each job that a request starts uses your prepaid credit, and each request key has its own spend limit.Bring your imageA container image contains your code and everything that the code needs to run. You send the image to Hangar once, and then run the image on a GPU or CPU as many times as you want.Images from your registryHangar can run a public container image straight from Docker Hub, GitHub Container Registry, NVIDIA NGC, Amazon ECR Public or Quay, so you do not need Docker on your machine. You pay for the jobs of the image.Image names and tagsImage tags give your container images short names, so you can say v3 and still know exactly which image a job used.How images are stagedStaging puts your container image on the instance that runs your image. Hangar refuses an image that fails a check before any container starts.CUDA and the driverCUDA is NVIDIA's toolkit for programs that run on a GPU. Hangar runs one NVIDIA driver branch on every GPU instance, and your image contains the CUDA version that the image was built for. The host supplies only the driver.
CPU jobs
3 pages
The sandbox and its gatewaySandbox sessions give your AI agent a private computer in Sydney, and the agent can reach only the internet addresses that you list. You pay by the second from prepaid credit.Sandbox sessionsSandbox sessions keep your agent's work safe when a client drops, goes idle or stops. A running session costs compute. A paused session costs storage.Credentials in sandboxes and runsCredentials let your jobs and sandbox sessions call services that need a password or a key, without the secret appearing in your image, your logs or your certificates. You store each secret once by name. A job or session can use only the secrets that you allow for that destination.
Security and records
7 pages
How a job is isolatedEvery slot runs on its own freshly launched instance, so your job never shares a machine with another customer's job. The instance runs inside Hangar's capacity block in Sydney, from the signed Hangar image.What a certificate provesA job certificate is a signed record that shows what happened in one job. An assessor, a privacy officer or a risk committee can check the certificate on their own machine, with no Hangar account.The verifierThe verifier checks a Hangar job certificate on your own machine, so you do not have to trust Hangar's word. Anyone can use it with no account, and it costs no credit.Where your data livesThis page shows every place where Hangar stores your data, how each place is encrypted and how long Hangar keeps the data there.Retention and deletionRetention is how long Hangar keeps your uploads, outputs, checkpoints and job logs before Hangar deletes them. You can delete the data earlier, or lock the data for 7 years or until a date that you set.SubprocessorsThis page lists every subprocessor in two columns: those in the data path, which handle customer data, and those outside it, which handle account and billing details only. Each entry names the service, its location and its role.Security advisories and maintenanceThis page tells you, before you book, how fast Hangar acts when a vulnerability or an advisory appears.
Reference
2 pages