Getting Started

About 2 min

Getting Started

Join us in creating the decentralized future of CI/CD! Our passion is helping open source communities to build better software faster and more efficiently. Open source software is developed out in the open, so why wouldn't you use an open source CI/CD tool?

Welcome to the Nosana Node documentation. Here you will learn everything that you need to know to get up and started with a Nosana Node. Nosana Nodes are key to running the Nosana Network. Without the nodes we have no network. What ever your reason is to run a node and there are a couple such as:

  • You want to earn NOS tokens
  • You want to run pipelines and donate a pipeline to your favorite opensource project
  • You want to contribute to a decentralized docker engine
  • You want to be part of a resilient and reliable network to power the next crowd computing platform.

This is the easy way to get started.


In this quickstart guide will operate with the following assumptions:

These assumptions are made in order to get you up and running as quickly as possible, without the need to setup your node with NOS tokens and a Nosana NFT.

Now that we have the assumptions out of the way, we need to take care of some prerequisites.


The first one is to make sure Docker installed and the proper priviliges set. Right now, these instructions will only work on macOS and Linux; maybe, WSL should work but has not been tested.

Make sure you have Docker installed and that it is added to its own user group. Please follow these links to install and setup Docker:

This will make sure that we can spin up the Nosana Node without any root priviliges.

Nosana Install Script

You will be able to run this one command in your command line and you will have a Nosana Node running on your machine.

curl -fsSL | bash

Note that this script requires the requirements mentioned above, it is configured to run in such a way that it does not require sudo. You should never run any script from the internet with sudo priviliges without double checking it. Even in this situation, do double check the script before running it on your box. You can read it here: in new window

Last update: