Docs - Overview


1) Create account & add credit #

Before you can rent a machine on, you will need to setup an account and add a method of funding. Go to the billing page of the console and click on the Create Account link to setup a username and password.

You will need to add credits to your account before you can rent an instance. Click on the Add Credit button to see the billing options. Adding a credit card is the simplest method. Crypto payments through and Coinbase are also supported. You can select an initial deposit amount (minimum $5) and follow the selected payment flow. Once that completes the amount of credit purchased will be added to the account and appear in the upper right status bar.

Once you spend your balance down your instances will be stopped until you add additional credits. To prevent that from happening, you can set an auto-billing threshold on the billing page to have your card auto-charged when your credit balance goes below the threshold you set. We recommend setting an auto-charge threshold greater than your daily spend rate, and a low-balance email threshold a bit lower so that you get an email if the auto-charge billing attempt fails for whatever reason.

2) Set up your device for connecting to instances #

Based on how you plan to connect to your Vast instances, you should have your account and device set up accordingly. You can learn more about our launch modes here. If you are interested in SSH, you will need to create an SSH key and upload to your account, or if you want to use Jupyter you may need to install the Jupyter certificate for Vast. To make sure these modes of connecting to your instances are set up properly, we recommend you follow our set up documentation step-by-step, as we find some users have trouble with this portion of set up.

3) Select and customize a template #

A template contains a Linux docker image, related settings and launch mode(s) for connecting to the machine. Built in Jupyter and SSH are supported as options for most images. Click on the template link in the navigation panel to open the templates page. The recommended and popular templates are displayed near the top. The recent section near the bottom displays your recent templates. Whenever you edit a template, a new version if it is created and stored in your recent list.

Read the template descriptions and pick one that suits your use case by clicking the select button.

Any template that uses the Jupyter HTTPS launch mode will require you to first install a certificate on your local machine. On macOS, this is required. Windows and Linux will show a bypassable warning if the cert is not installed. To install the Jupyter certificate for Vast, follow the instructions here.

To use SSH, you will need to create an SSH key and upload the public portion to Vast. Learn more here.

4) Filter machines #

Use the filters to specify the GPU number, type and other factors such as port ranges, number of CPUs, amount of GPU ram and more. Each filter will narrow the offers displayed. If you see few or zero search results, reset your filters.

5) Select Storage #

Make sure to use the storage slider on the left of the create page to choose your storage allocation size. You can't change this after instance creation, so make sure to size correctly at start!

6) Rent #

Hitting the blue RENT button will accept the offer and create an instance with the specified docker image and launch mode. Once rented, the instance will appear in the Instances tab.

7) Enjoy #

If the docker image is cached your instance should load in a minute or less depending.
If the image is not cached, it will go through stages of downloading which can take 10 minutes to an hour depending on internet speeds. After loading the instance will startup. If your image uses the open button this will transition from connecting to open once an application starts responding on the port. If your image uses ssh or jupyter, you can access those through their own buttons on the instance control panel.

8) Destroy #

Make sure to destroy instances after you are done with them. Stopping the instance will prevent GPU charges but you will still accrue charges for the instance storage allocation. Stopped instances can be restarted if/when the GPU is available.