> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tape.network/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

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](https://docs.tape.network/protocol/architecture/storage-nodes.md) and
[gateways](https://docs.tape.network/protocol/architecture/gateways.md).

> [!NOTE]
>
> Joining the public network as an operator starts with the staking program.
> [Fill out the form](https://form.typeform.com/to/jJlpMc8r#path=tapenet\&source=node-setup) 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](https://docs.tape.network/protocol/quickstart.md). Running Tapedrive privately for your own data is a
separate setup with no stake. See
[Run Tapedrive locally](https://docs.tape.network/tapenet/local.md).

> **[Run a storage node](https://docs.tape.network/protocol/node-setup/storage-node.md)**
>
> Stake, register, and start earning for storage you prove.

> **[Run a gateway](https://docs.tape.network/protocol/node-setup/gateway.md)**
>
> 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](https://docs.tape.network/tapenet/access.md#fund-a-node) covers
funding the identity used by your node. Current endpoints are on the
[network details page](https://docs.tape.network/protocol/architecture/networks.md).

## 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.