# Hanzo Visor — Hanzo AI

> Provision, configure, monitor, and tear down virtual machines and bare-metal hosts from one API.

hanzoai/visor

# Hanzo Visor

Machines from several clouds, through one API

Launch a machine, attach a volume, open a console, tear it down — the same four verbs whether the hardware is DigitalOcean, AWS, Hetzner, Azure, Google Cloud, Aliyun, Lightsail, or a KVM host in your own rack. Every machine belongs to an organization, and that organization is read from the signed identity on the request, never from a field the caller filled in.

[Get Started](https://docs.hanzo.ai/docs/services/visor)[View on GitHub](https://github.com/hanzoai)

## What you get for the price of one integration

A machine is a machine. The provider is a field on it.

### One catalogue, GPUs included

Regions, sizes and GPU instances from each provider, cached and priced, read through the same call. Ask for what you want; Visor knows which provider can give it to you and what it will cost there.

### Volumes and images

Attach and detach block storage, launch from a provider image or one of your own. Batch launches name themselves in sequence and group under the prefix, so a fleet is just machines and there is no second object to learn.

### Pools, and managed Kubernetes

Node pools group machines by shape and role. Managed Kubernetes clusters are provisioned through the same surface, so the cluster and the machines beside it are one inventory rather than two consoles.

### Priced before it exists

A launch can run as a dry run: it returns the quote and spends nothing. A real launch is metered against the organization as it goes, per provider, so the bill is assembled from the same numbers the quote came from.

### A console in the browser

RDP, VNC and SSH reach the machine through a gateway and render in a tab — no client to install, no key to hand out, and no bastion of your own to keep patched. The session is a record, not just a connection.

### Every action leaves a row

Who launched it, who opened a console, who destroyed it, under which organization and project. Authorization runs through the same grant calculus the rest of the estate uses, so a machine cannot be reached by anyone whose token does not cover it.

## Get started with Hanzo Visor

[Read the docs](https://docs.hanzo.ai/docs/services/visor)[View on GitHub](https://github.com/hanzoai)

## Open source

License: Apache-2.0[hanzoai](https://github.com/hanzoai)

## Get Visor

Machines, volumes, and clusters

[Deploy to Cloud](https://console.hanzo.ai/deploy)[Self-host](https://docs.hanzo.ai/docs/services/visor)