Skip to main content
You can contribute two kinds of infrastructure to Tapenet. A storage node holds slices of the public network’s data, proves it still has them, and earns TAPE for the work. A gateway serves reads to users and applications; it stores nothing permanently and earns nothing from the protocol, but it gives heavy read workloads dedicated service. The architecture pages explain each role: storage nodes and gateways.
Joining the public network as an operator starts with the staking program. and we’ll help you get set up.
You do not need any of this to connect a client to Tapenet. Start with the quickstart. Running Tapedrive privately for your own data is a separate setup with no stake. See Run Tapedrive locally.

Run a storage node

Stake, register, and start earning for storage you prove.

Run a gateway

Serve reads at your own limits, with your own cache.

​
Availability

Tapenet is in early access. A storage node stakes, registers, and joins the network. The Tapenet setup guide covers funding the identity used by your node. Current endpoints are on the network details page.

​
Deployment tooling

The repository ships the tooling we use for our own fleet: Ansible playbooks and a provisioning CLI that automate everything in these guides. The guides below document the manual path, which is also the best way to understand what the automation does.