The Akash Network is a decentralized protocol for provisioning, scaling, and securing cloud workloads. Using Akash, companies (Providers) make their spare server capacity available for containerized deployments by any developer (Tenants). Tenants benefit from access to a a low-cost, decentralized, geographically distributed cloud infrastructure platform whose conventions are very similar to any other cloud provider. Providers benefit by monetizing the idle compute capacity in their on-prem and colocated datacenters.
The Network contains two major functional elements:
Marketplace: A blockchain-based system that allocates capacity on provider servers to tenants wishing to deploy to them, and transfers payments from tenant to provider in the native Akash (AKSH) token.
Deployment: A Kubernetes-based system that provisions pods on provider servers and deploys/orchestrates Tenant containers within them.
The permission-less marketplace provides a censorship-resistant procurement mechanism for highly scalable and secure container based deployments for base resources which are compute, memory, bandwidth, and storage.
See a mistake? Open a pull request
The Akash Suite is composed of a full node
akashd and the client
akash. The full node (
akashd) is the (tendermint-based) blockchain node that implements the decentralized exchange.
akash is the client used to access the exchange and network in general.
$ /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
akashddaemon using homebrew
$ brew install ovrclk/tap/akash
The simplest way to install is by using homebrew. Install
akash client by running
brew install ovrclk/tap/akash. Once installed, verify the installation by running
Alternatively, you can manually download the binaries from the releases page. The latest release is
0.3.6 as of writing of this document, please make sure to check the releases page for the latest version. The final step is to make sure that the akash binary is available on the
PATH.This page contains instructions for setting the PATH on MacOS.
The final step is to make sure that the terraform binary is available on the
PATH.This page contains instructions for setting the PATH on Linux.
The final step is to make sure that the akash binary is available on the
PATH.This page contains instructions for setting the PATH on Windows.
Others (From Source)
Installing akash suite from source
$ go get -d github.com/ovrclk/akash $ cd $GOPATH/src/github.com/ovrclk/akash $ make deps-install $ make install
Additional requirements are:
- glide: Golang library management.
For development environments, requirements include:
- protocol buffers: Protobuf compiler.
Most golang libraries will be packaged in the local
vendor/ directory via glide, however the following packages will
be installed globally with their binaries placed in
Once you have the dependencies properly setup, download and build