Skip to content

Getting Started

Get started with the Spearhead Cloud today. Sign-up for a free trial.


This document will describe how to set-up a Spearhead Cloud account.

Create a Spearhead Cloud account

  1. Create a Spearhead Cloud account.
  2. Add your SSH key(s).

Now you are ready to start working with the Spearhead Cloud.

SSH Keys

You can use your existing key or create a new one in the Spearhead Cloud Portal.

  • Manually create an SSH key pair from MacOS (or Linux/Unix)
  • Manually create and SSH key pair from Windows

When you login to the customer portal you should add/create your SSH keys before creating any instances by visiting your Profile settings. Do not skip this step as the key is required if you wish to log-in to your remote linux/unix systems or if you wish to use the Spearhead Cloud Tools1.

1Without these SSH keys uploaded you will not be able to access your instances.

Create SSH Keys (MacOS or Linux/Unix)

You can create ssh keys using the following command on most unix-like systems:

ssh-keygen -t rsa

Next steps


  • instance(s) - an instance in the spearhead cloud may refer to:
    • a hardware virtual machine
    • an infrastructure container
    • a Docker container
  • image(s) - images contain your operating system, applications and services. Spearhead provides several images to help you get started. Some images contain complete applications and services for easy and quick deployments or start from scratch images where you can configure the applications yourself.
    • Docker container images - you can connect public or private container registries to run those images on Spearhead Cloud.
    • Infrastructure container images - are container native Linux and SmartOS systems running on bare-metal. These offer high performance, scalability by allowing on-line resizing and security. Take advantage of preconfigured images for many scopes such as databases and web servers.
    • Hardware virtual machines - these are typical virtual machines that run using KVM. We provide these for legacy systems or workloads that cannot be deployed as containers.
  • package(s) - packages define the resources allocated to an instance.

Last edit: 2018 Thu 26 Jul 19:48 GMT+3