Starting with JarvisCloud

We built JarvisCloud with 2 purposes in mind. We wanted the platform to be simple and affordable for DL and AI practitioners. With JarvisCloud you get instant access to a GPU-powered Jupyter notebook with your favorite framework and can also ssh to it, all in one click.

Quick Start Guide TLDR;

  1. Create an account at

  2. Add payment information in Billing section

  3. Recharge wallet to add funds using recharge wallet

  4. Select machine type here and click Launch

  5. Start, Pause, or Delete with the buttons Action Buttons

Note: Paused instances are only charged for storage.

Launch your first instance in less than 30 Seconds

Create an account

Sign up here on

Add Credits

To avoid any unnecessary billing JarvisCloud follows a prepaid system. You buy credits using a credit card. JarvisCloud deducts money from the credits added to the JarvisCloud wallet for actions like create, pause, and resume instances.

Add a Credit card

JarvisCloud uses Stripe for managing all the credit card transactions. All the data shared to Jarvis Cloud related to your card is sent to Stripe. JarvisCloud does not store any information related to your credit card. You can add card details in the Billing section.

Add your card

Recharge the wallet

Once the card is added successfully, you can recharge for a predefined amount of $10, $20, $50, or $100. If the recharge is successful, then JarvisCloud adds the same amount as credits in your wallet.

Recharge wallet

Launch an Instance

Once you are logged in, you can choose different configurations like framework, number of GPUs, and the storage you may need. Once you have confirmed the chosen configurations, press the launch button. Your instance should be created in less than 10 seconds. We create an instance that is optimized for the framework of choice. We also install a variety of commonly used libraries like git, wget, GCC, Pandas, NumPy, scikit-learn, matplotlib, etc.

Create new instance

Launch only when you are ready to use, as the instances are billed per minute.

You should be able to see a running instance like this under create instance section.

Running Instance

There are 4 critical actions that you can do while running instances.

  1. You can access Jupyter lab and also connect to the instance through the command line(Optional).

  2. Pause the instance after using it to save the state of the instance for later use. (all the installations, notebooks, and data downloaded/created will be preserved until you resume/delete the instance.

  3. Resume paused instance to start from where you left.

  4. Destroy it completely when work is completed to stop the billing cycle.

Accessing the instance

Accessing the instance through Jupyter Lab

Clicking the green color play buttonplay button on the running instance opens a Jupyter Lab. If you like to work with Jupyter notebook, then change the word lab to tree in the URL.

Click green play button on Running instance

Accessing the instance through SSH

You can also easily access the instance through SSH. To do that, we would need you to update your public ssh key in the API Keys section.

Add SSH key

If you have created your ssh_keys earlier you can access it by using the below command in a local terminal / PowerShell.

cat ~/.ssh/

If you have never created an ssh key pair then you can create one as explained in the next section.

Create your local SSH key pair

Run the following command in a local terminal / PowerShell to generate an SSH key pair:

ssh-keygen -t rsa -b 4096

Get the SSH command here

Every launched machine will have SSH command associated with it once you have added your SSH key as shown in the previous step. To Copy the command specific to your machine right-click on the running instance and go to Get URLs, click on the first option to copy the SSH string. Your SSH string will be copied to the clipboard.

SSH command Now you can simply execute the SSH command from your terminal and start training your models.

Accessing the instance through VS Code

You can also access and run your deep learning programs straight from Visual Studio code in 3 easy steps. To do that, you should have updated your public_ssh keys as mentioned earlier.

  1. Install Remote - SSH Extension.

  2. Add New SSH Host.

  3. Connect to Host.

Install the Remote-SSH Extension from the Visual Studio code extenstions.

VS code plugin

Add & Connect to New Host

⇧⌘P / Ctrl+Shift+P to open Command Palette

Connect to new Host from VS Code

Accessing the instance through Jetbrains DataSpell IDE

You can also connect to the instance through Jetbrains DataSpell.

  1. Copy your instance JupyterLab URL using right-click menu.
  2. From DataSpell Extentions -> add New Jupyter Connection
  3. Choose Connect to Jupyter Server using URL
  4. Paste Jupyter URL into Server URL
  5. You will find to notebook server Running under Files Tab.

Below is small demonstration from our user

Dataspell Jupyter

Visualise your progress in TensorBoard

You can open up TensorBoard to visualize your model's loss and metrics over time. To open up TensorBoard right click on the running instance card as shown below. TB fire up

Pause your instance

After running a few experiments, if you want to pause the instance for later use then press the blue color pause button. pause buttonYou will be charged only for the storage during the paused duration.

All the paused instances are listed below the running instances.

Paused Instances

This feature is useful when you plan to return to use the instance in a few hours or a few days. If you plan not to use the instance further then press the red trash button to destroy the instance. It will prevent further charges for storage.

Resuming an instance

You can hit the green play button on the paused instance to resume your work. A new instance is created with all your previous data.

Paused Instances

Scale GPUs on resume

Scale GPUs

You can click on the setting icon button on the pause card Pause button to modify your instance parameters before resuming the instance.

You can

  • switch to higher or lower end GPU
  • scale GPUs
  • expand or shrink storage space.

Once you have chosen the parameters, you can click on the play buttonplay button to resume your instance.

Destroying/Stopping the instance

If you have completed your work and no longer need the instance, then press the red color trash buttontrash button which will delete/destroy the entire instance. Your billing will be stopped. This is an irrecoverable event, so ensure you have backed up any important data before destroying the instance.

You can delete both running and paused instances.

Running Instance Paused Instance

Note: Ensure you destroy the instance to avoid any unnecessary billings

Advanced Features

Automatically Pause the instance from your code

You can choose to pause your instance from your Jupyter notebook or VScode by calling the below function

from jarviscloud import jarviscloud

Download Data to JarvisCloud instances

Once an instance is created, we would need data to train our deep learning models. In this post, we will cover some of the popular sources from which you can download data. As we come across other popular data sources, we will update the post.

Downloading data from Kaggle

In the last few years, Kaggle has become a great source for a variety of data. Kaggle provides a command-line tool, which helps us to do different activities like

  • Downloading data

  • Uploading data

  • Make your Kaggle submissions

Since it is a very important command-line tool, we install it on all the instances. To check if it is installed, connect to the terminal of your Jarvis instance and type Kaggle in your terminal.

Kaggle commands

To use the Kaggle API, we need Kaggle API Token, which can be downloaded from the Kaggle Accounts section page.

Download kaggle.jsoncopy to root dir

Now let's upload the kaggle.json to our remote instance and move it to ~/.kaggle/kaggle.json and check again how the Kaggle command line responds.

Now since the configuration part is done, let's grab a dataset from a Kaggle competition.

enter image description here

Upload Data to JarvisCloud instances

Uploading Small files.

Often times we would need small files on our instance. Assuming it is on your local machine, we can use Jupyter lab/notebook to upload. If the file is larger than a few megabytes then avoid this approach.

Uploading Large files from the local machine.

If you have a large file greater than 10MB, you can use a tool called Secure Copy (SCP) to transfer files to the remote machine. You can also use the tool for copying data from remote instances back to your local machine. To use SCP, do not forget to add your public SSH keys in the API Keys section. If you are not sure how to do that, then read Accessing the instance through SSH section.

scp -P 8961 ~/Documents/

If your id_rsa file is not in its default location, then you need to give a path of it using -i option.

scp -i ./id_rsa -P 10960 /Users/akshath/Downloads/cat.jpeg

Using a public container image BYOC (Beta).

You can Bring Your Own Container(BYOC) on

To launch an instance from public image follow below steps.

  1. Enter a public image name like pytorch/pytorch. (Organization/repository)
  2. Ensure you have configured your SSH key in the API keys section.

Once the instance is launched, right-click on the instance to get the SSH string and connect to the instance. The ssh string would look like this

ssh -p 8960 -L 9960:localhost:8888

Connecting to a jupyterlab inside the instance

Install jupyterlab in the newly created instance.

pip install jupyterlab

Starting JupyterLab

jupyter lab --allow-root

Copy the token from the terminal, which we will need to access. Open a browser, and enter the below URL


Copy the port number from the ssh URL and replace the port number above. Use the token from the terminal to start using jupyter lab. The feature is in beta, in case you face any challenges, please reach out to us. We will be happy to adapt and make the process smoother.


Instance not getting paused

Your storage disk might be full. To delete unwanted files use the below command sudo rm-rf <filepath/filename>

delete files

Note: If you need any more assistance please drop an email to or ping us on the Chat window.