# Overview Welcome to the SILO Documentation! ### What is SILO[​](http://localhost:3000/docs/Home/intro#what-is-silo) ? SILO is a leading provider of enterprise-grade, globally distributed cloud object storage. It serves as a seamless replacement for any S3-compatible object storage, offering unparalleled durability with 99.95% availability and enhanced global performance from a single upload. SILO provides default multi-region, CDN-like performance with zero-trust security, all at a cost up to 80% lower than AWS S3. Easily integrable into existing tech stacks with S3 compatibility, SILO operates as a trustless, globally distributed network that leverages existing excess storage capacity. This ensures enterprise-grade performance, privacy, and resiliency with compelling economic benefits. ### Main Features[​](http://localhost:3000/docs/Home/intro#main-features) Some of the main SILO features include: | Feature | Description | | --------------------- | ------------------------------------------------------------------------------------------------------------------------------ | | S3 Compatibility | Update the endpoint and credentials in your S3-compatible tool to get started in minutes. | | Third-party Tools | Dozens of compatible tools for backups, large file transfers, file management, content delivery, scientific data, and more! | | End-to-End Encryption | Maintain full control over your data with default encryption and user-assigned access grants, ensuring no unauthorized access. | | Cost Efficiency | Storage as low as $3.00 per TB per month with $6.00 per TB for egress. | | Multi-region | Multi-region cloud object storage with data distributed across tens of thousands of nodes worldwide. | | Open Source | Enjoy transparency through open source code. You’re never locked into specific technology or cost structures. | ### How to Use These Docs[​](http://localhost:3000/docs/Home/intro#how-to-use-these-docs) On the left side of the screen, you'll find the docs navbar. The pages are organized sequentially, allowing you to follow step-by-step. If you're already familiar with object storage, jump directly to the section that fits your use case. On the right side of the screen, there's a table of contents to help you navigate within pages. Use the search bar at the top or press Ctrl+K or Cmd+K to find pages quickly. ### Join the Community[​](http://localhost:3000/docs/Home/intro#join-the-community) If you're stuck on an issue, others in the community can help troubleshoot or share insights. Learn how to build on SILO, administer servers, write and deploy code, and configure open source tools. [Forum](https://forum.silos3.com/) ### Getting Help[​](http://localhost:3000/docs/Home/intro#getting-help) Visit our Help Center for support. # Pricing
{% content-ref url="/pages/WThz75zwrR0ZXqxHwM0R" %} [Individual](/home/pricing/individual) {% endcontent-ref %} {% content-ref url="/pages/K2t9mGjckAxmKpS3HRPG" %} [Enterprise](/home/pricing/enterprise) {% endcontent-ref %} # Enterprise The price for object storage with SILO starts as low as $0.0036 per GB per month, with $0.0063 per GB for egress bandwidth. The following table lists the types of metered services that appear in billing and usage user interfaces as well as invoices:
Metered Service TypeMetered UnitsIncrementPricing UnitPrice per Pricing UnitDescription
Object StorageBytesGB HourGB Month$0.0036 per GB MonthStorage is calculated based on bytes uploaded, including any encryption-based overhead
Egress BandwidthBytesGBTotal Volume$0.0063 per GBBandwidth related to object downloads calculated on bytes downloaded including long tail elimination-related bandwidth
SegmentsSegmentsSegment HourSegment Month$0.0000079 per Segment MonthSegments usage depends on storage. The default size for a segment is 64MB (or less), i.e., smaller objects use more segments
Billing is aggregated at the project level. A project is the SILO service construct used for aggregating usage, calculating billing, invoicing fees, and collecting payment. Billing on a project begins when a user upgrades to a pro account (even if their free trial has not ended). Projects are created by a single user, then multiple users may be added to a project team, and one user may be on more than one project. Within a project, usage is tracked at the bucket level and aggregated for invoicing to the project. The following section describes how the charges listed in the table above are calculated to provide users with detailed insights into their cloud storage usage, broken down by storage, egress bandwidth, and the number of objects. Note that for billing purposes, usage data is continuously rolled up and aggregated. Billing data is not displayed in real-time in the SILO interface, and some time lag should be expected. ### Object Storage[​](http://localhost:3000/docs/Home/pricing#object-storage) Object storage is priced per GB per month in increments of byte hours. The calculation of object storage fees is based on a standard 720-hour month. Actual storage is metered in bytes uploaded. Bytes uploaded include the bytes associated with actual objects plus any nominal overhead associated with encryption. Byte hours are calculated based on the number of hours bytes are stored on the SILO Platform from when an object is uploaded to when it is deleted. The calculated number of bytes is then multiplied by the byte hour price. The byte hour price is derived from the GB month price divided by the standard 720-hour month and base 10 conversion of GB to bytes. **Example** A user uploads a 1TB file. Halfway through the month, the user deletes the file. With encryption overhead, the file is stored as 1.001TB. The 1.001TB is accounted for as 1,001,000,000,000 bytes. The file is stored for 360 hours. The file is stored for 360,360,000,000,000 byte hours. In this example, the price per GB month is $0.0036, and per GB hour is $0.000005. The price per byte hour is $0.000000000000005. The total amount charged for the storage is $1.80. ### Bandwidth Fee[​](http://localhost:3000/docs/Home/pricing#bandwidth-fee) Download bandwidth, also referred to as egress bandwidth, is priced per GB in increments of bytes downloaded. The calculation of download bandwidth price per byte is derived from the GB download bandwidth divided by the base 10 conversion of GB to bytes. The calculated number of bytes is then multiplied by the byte download bandwidth per byte price. When an object is downloaded, several factors can impact the actual amount of bandwidth used. The download process includes requests for pieces from more than the minimum number of storage nodes required. While only a subset of pieces out of the total are required to reconstitute an object, SILO will try to retrieve an object from additional storage nodes to avoid potential long-tail performance lag from a single node. **Example** A user downloads one 1TB file. Based on the long tail elimination, up to 1.3TB of download bandwidth may be used. The 1.3TB of download bandwidth is accounted for as 1,300,000,000,000 bytes. In this example, the price per GB is $0.0063, and per byte is $0.000000045. The total amount charged for the egress is $8.19. ### Per Segment Fee[​](http://localhost:3000/docs/Home/pricing#per-segment-fee) For most users and usage patterns, we do not expect a Per Segment Fee to be charged. Only when large numbers of segments are stored relative to a disproportionately small amount of data do we expect there to be a Per Segment Fee. Only use cases with large numbers of very small files or large numbers of very small multipart upload parts are expected to be subject to the Per Segment Fee. Each segment stored on the network is charged a nominal Per Segment Fee. The Per Segment Fee is $0.0000079 per segment per month. Distributed object storage is optimized for large files (several MB or larger - the larger, the better). Very small objects generate more overhead with the storage of the metadata for the file than the actual storage of the object. Consequently, we charge a small Per Segment Fee to account for that overhead. **Examples:** * A single 1MB file is one segment. * A single 10MB file is one segment. * A single 64MB file is one segment. * A single 256MB file is four 64MB segments. * A single 1GB file is 16 segments. **Cost Example:** A user uploads 1.6 million one MB files, totaling 1.6TB. Halfway through the month, the files are deleted. The files are stored for 360 hours, accounting for 576,000,000 segment hours. The total cost for the segment fee would be $7.04. ### Next Steps[​](http://localhost:3000/docs/Home/pricing#next-steps) Explore more details about SILO pricing and features on our [SILO Documentation](https://docs.silos3.com/). For assistance, visit the [SILO Forum](https://forum.silos3.com/). # Individual SILO Storage Pricing for Individual Users ### Introduction SILO offers flexible storage plans for individual users through **SILO Drive**, **SILO Photos**, and other future apps from SILO. Individual users can select from a variety of plans based on their storage needs. The main difference between individual users and enterprise users is that individual users: * Do not have access to the **S3-compatible SILO Storage Nexus**. * Do not have access to the **pay-as-you-go** plan, which is exclusive to enterprise users. To view the enterprise user pricing, [click here](https://docs.silos3.com/enterprise-pricing). *** ### Pricing Plans {% tabs %} {% tab title="Monthly" %} | **Plan Name** | **Storage** | **Price (per month)** | | ------------- | ----------- | --------------------- | | Starter | 25 GB | $0.00 | | Essential | 60 GB | $0.35 | | Pro | 100 GB | $0.41 | | Advanced | 200 GB | $0.60 | | Plus | 2000 GB | $1.88 | | Elite | 5000 GB | $4.71 | | Premium | 10000 GB | $9.42 | | {% endtab %} | | | {% tab title="Yearly" %} | **Plan Name** | **Storage** | **Price (per year)** | | ------------- | ----------- | -------------------- | | Starter | 25 GB | $0.00 | | Essential | 60 GB | $10.91 | | Pro | 100 GB | $11.62 | | Advanced | 200 GB | $18.59 | | Plus | 2000 GB | $60.45 | | Elite | 5000 GB | $151.14 | | Premium | 10000 GB | $302.28 | | {% endtab %} | | | | {% endtabs %} | | | *** ### Important Notes 1. **Changes to the Free Plan:**\ The **free plan** is subject to availability, and SILO reserves the right to increase, decrease, or remove the free storage plan. If any changes are made, users will be informed in advance via email. 2. **Initial Free Space and Tasks:**\ All new users will initially receive **10 GB** of free space. To increase it to **25 GB**, users must complete small tasks within the **SILO Drive** and **SILO Photos** applications. These tasks will be simple and will be designed to help users explore the features of SILO's applications. ### Plan Details 1. **Starter Plan (Free)**: Great for light storage needs, such as document backups. 2. **Essential and Pro Plans**: Ideal for users who need more space for photos, videos, and files. 3. **Advanced, Plus, Elite, and Premium Plans**: Best for users with large storage needs, such as media creators or users who store large libraries of data. With SILO’s storage plans, you get: * Secure cloud storage. * Access across multiple devices. * Integration with future SILO applications as they become available. Select the plan that best fits your needs and enjoy the benefits of **SILO’s advanced storage solutions**. # Product Overview ### Introduction[​](http://localhost:3000/docs/Learn/product-overview#introduction) SILO makes open-source software that anyone can run - individuals with a Network Attached Storage Device or NAS, those with desktop computers that are always on, businesses, or data centers - that allows these users to share unused disk drive space and bandwidth with the network. Our software aggregates all of that storage capacity and bandwidth to create an extremely secure, private, and durable cloud storage service for developers. SILO makes that storage and bandwidth available as a distributed cloud object storage service for developers, with an enterprise-grade 99.95% availability and S3 compatibility under the SILO brand. ### What is SILO?[​](http://localhost:3000/docs/Learn/product-overview#what-is-silo) SILO is an encrypted, secure, and affordable object storage service that enables you to store, back up, and archive large amounts of data to the decentralized cloud. {% embed url="" %} For developers who demand ownership of their data and who want to build with confidence, SILO is private by design and secure by default—delivering unparalleled data protection and privacy when compared to traditional centralized cloud object storage alternatives. SILO offers affordable and predictable pricing, S3 compatibility, a robust library of open source technical documentation, and familiar development tools - along with a vibrant user community - which enables developers to economically and easily learn and leverage decentralized cloud storage technology to take control of their data when building the next great application or service. ### Peer Classes[​](http://localhost:3000/docs/Learn/product-overview#peer-classes) There are 3 main components, or peer classes, on the network - Storage nodes, the application that enables people to share excess hard drive capacity and bandwidth with the network, Sconnect Clients, developer tools (sometimes hosted) to upload and download data, and finally, the Orbital, a hosted set of services that handles access management, metadata management, storage node reputation, and data repair, as well as billing and payment. The Storage Node stores data for others, and gets paid for storage and bandwidth. All data stored on storage nodes is client-side encrypted and erasure-coded. Sconnect Clients enable developers to store data on SILO, handling end-to-end encryption from the client-side (by default), and erasure coding, where files are split into 80 pieces then distributed across our network of storage nodes. Each of the 80 pieces is stored on different, diverse storage nodes, with different operators, power supplies, networks, and geographies, etc. - yielding tremendous security, performance, and durability advantages. The client-side managed, end-to-end encryption combined with our edge-based access management capabilities provide easy-to-use tools for building applications that are more private, more secure, and less susceptible to a range of common attack vectors. Sconnect clients include both our self-hosted and SILO-hosted S3 compatible gateways, the CLI, and the libuplink Go library and bindings. The Orbital is a set of hosted services that handles developer account access, API access management, metadata management, storage node reputation, data audit, and data repair, as well as billing developers and payment for Storage Nodes. SILO Labs orbitals are operated under the SILO brand. ### How it's Different[​](http://localhost:3000/docs/Learn/product-overview#how-its-different) To give you a sense of how the SILO service is different, it’s helpful to describe what happens with a round-trip upload and download of a file. Files are uploaded using a Sconnect client, whether directly using the CLI or S3 compatible gateway, or indirectly using a tool that has integrated the libuplink library, such as FileZilla, Rclone or Restic. ### What Happens When You Upload[​](http://localhost:3000/docs/Learn/product-overview#what-happens-when-you-upload) When a file is uploaded, it’s first encrypted by the Sconnect client using an encryption key held by that client. Next, it’s erasure-coded, meaning it’s broken up into pieces, of which only a subset are required to reconstitute a file. The redundancy from erasure coding is far more efficient than replicating files and this technology used by most data storage systems, including DVDs, which is why you can still watch a movie even if there are scratches and fingerprints on the disk. For example, we may need 29 of the 80 pieces we uploaded. The Sconnect Client then contacts the Orbital to get a list of Storage Nodes on which to store the pieces. The Orbital returns more than 80 Storage Node addresses. The Sconnect Client uploads pieces peer-to-peer, in parallel, directly to the Storage Nodes. The Sconnect client stops attempting to upload pieces once 80 pieces have been successfully uploaded to at least 80 Storage Nodes. The Sconnect Client attempts a few more than 80 during the upload process to eliminate any long-tail effect and the related latency from the slowest Storage Nodes. ### What Happens When You Download[​](http://localhost:3000/docs/Learn/product-overview#what-happens-when-you-download) When the Sconnect Client downloads a file, it’s essentially the same process as an upload but in reverse. The Sconnect Client requests a file from the Orbital and the Orbital returns a list of Storage Nodes from which the Sconnect Client can retrieve the pieces of the file. The Sconnect Client starts attempting to download pieces from the given Storage Nodes, again, stopping once it has retrieved the required pieces needed to reconstitute the file after eliminating latency from the long-tail effect. The pieces are re-encoded and then decrypted by the Sconnect client as only it has the encryption key. ### Why Developers Love SILO[​](http://localhost:3000/docs/Learn/product-overview#why-developers-love-silo) Even with the sophisticated privacy and security features and the default multi-region availability, developers love SILO because it's extremely easy for them to get started and build more secure and private applications. When uploading and downloading files, a developer or app issues a simple `cp` command - the Sconnect Client does the rest, abstracting all of the complexity of encryption, erasure coding, and distributing pieces on storage nodes to the SILO software in the background. What's more, developers can use the Orbital Admin Console web interface or the `share` command with either our CLI or developer library/SDK to abstract all the complexity of granular access management via client-side delegated authorization. ### Features[​](http://localhost:3000/docs/Learn/product-overview#features) Developers have a wide range of choices for S3-compatible object storage, but SILO provides a number of key advantages to help developers build more secure and private applications: * **🛡 Security**: Confidently store your data with files split, distributed, and stored multi-regionally across the globe providing no single point of failure, resistance to hacking, tampering, and bitrot, and an edge-based security model. * **🔓 Privacy**: Own your data with default encryption and user-assigned access grants so no one can view or compromise your data without permission. * **🔌 Plug-in S3 Compatibility**: Swap out a few lines of code, and you’ll be up and running in minutes. * **☁️ Availability**: Download your data anytime you need it with multi-region architecture, no single point of failure, and Orbital-automated data orchestration. No downtime, no bitrot, and no lost files. * **🛠 Durability**: Automate file repair and know that Reed-Solomon erasure coding enables the highest levels of durability for all files uploaded to SILO. * **💰 Cost Efficiency**: Get high availability multi-region cloud object storage for a fraction of the price of a single availability zone from centralized providers like AWS. * **📂 Open Source Freedom and Flexibility**: Take advantage of absolute transparency through our open source code. You are not locked into our technology or cost structure - giving you the freedom of choice. * **👨🏽‍💻 Developer Friendly**: Take advantage of familiar development tools and robust technical documentation, tutorials, and videos to help get you started and leverage all the benefits of decentralized cloud object storage. * **💬 Community Driven**: Share, discuss, and collaborate with other open source developers in the SILO community and find answers to questions in our very active forum. # Overview ### 1. Introduction SILO is a decentralized storage network that allows individuals and organizations to share their unused storage space and bandwidth. By becoming a **Storage Node Operator**, you can contribute to the SILO network and earn rewards by hosting and maintaining data securely on your device. **Key benefits of becoming a SILO Node Operator:** * Monetize your unused storage space and bandwidth. * Be part of a global, decentralized cloud storage network. * Help enable secure and efficient data storage for users worldwide. *** ### 2. Become a Storage Node Operator Anyone with sufficient storage, bandwidth, and technical capability can become a **SILO Storage Node Operator**. Whether you have a personal computer or a dedicated server, you can contribute to the SILO network. #### **Requirements:** * **Device Requirements:** * Minimum of 500 GB of available storage space. * Stable internet connection with at least 5 Mbps upload and 25 Mbps download speeds. * **Node Uptime:** Your node should be online and available at least **99.3% of the time** each month to maintain good reputation and eligibility for rewards. #### **Why Join?** * **Earn SILO tokens** for providing storage and bandwidth. * Support a decentralized network that prioritizes security and privacy. * No central authority—your data, your rules. *** ### 3. Set Up Your Node Setting up your SILO node is simple and can be completed in a few steps: 1. **Download and Install the SILO Node Software:** * Visit the official [SILO Documentation](/node/overview/step-by-step-instructions-to-install-silo-node-using-docker) for the latest software downloads and instructions. 2. **Create Your TrustKey:** * Generate your **TrustKey** to authenticate your node and securely connect to the SILO network. 3. **Configure Your Node:** * Allocate the storage space and bandwidth you want to share. * Ensure your firewall and network settings are optimized for node operation. 4. **Start Earning:** * Once your node is connected and operational, it will begin contributing to the network and earning rewards. *** ### 4. Want to Contribute? SILO’s decentralized network thrives with community involvement. If you want to contribute beyond operating a storage node, there are many ways to get involved: * **Provide Feedback:** Share your experience and suggestions for improving the SILO platform. * **Join the Community:** Participate in discussions and stay updated by joining the SILO community on forums and social platforms. * **Spread the Word:** Help grow the SILO network by inviting friends, family, and colleagues to use SILO Drive, Photos, or become Storage Node Operators. * **Development Contributions:** If you’re a developer, contribute to SILO’s apps and tools to enhance the ecosystem. *** Ready to become part of the SILO network? Get started by setting up your node and begin earning rewards today! # Step-by-Step Instructions to Install Silo Node Using Docker *** ## **Step 1: Understand Prerequisites** Before setting up a Silo node, ensure the following: 1. **Hardware Requirements**: * Minimum **500 GB of free storage**. * Minimum **2 TB of bandwidth per month**. * Stable and consistent **internet connection**. 2. **Operating System**: * Linux or Windows (Docker support is required). 3. **Docker**: * Ensure Docker is installed. Follow the [Docker installation guide](https://docs.docker.com/get-docker/) if needed. 4. **Public IP Address**: * A public IP or properly configured Dynamic DNS. 5. **Wallet Address**: * A [Larissa Network](https://play.google.com/store/apps/details?id=network.larissa.wallet\&hl=en_IN) wallet address for Silo payouts. *** ## **Step 2: Get an Authorization Token** 1. Open **Silo** registration page on the [Silo website](https://silos3.com/signup/). 2. Enter your email to generate an **authorization token**. 3. Save this token securely, as it will be used to authenticate your node. *** ## **Step 3: Setup Port Forwarding** 1. Access your router’s configuration page: * Typically accessed via `http://192.168.1.1` (or your router's IP address). 2. Forward the following ports: * **TCP Port 28967**: Default Silo node communication port. * **UDP Port 28967** (if QUIC is enabled, see Step 4). 3. Ensure the forwarded ports point to the local IP address of the machine hosting the Silo node. *** ## **Step 4: Configure QUIC** QUIC improves performance and is recommended for Silo nodes. 1. Forward **UDP Port 28967** (as per Step 3). 2. Confirm with your ISP that **UDP traffic** is not blocked. 3. No additional configuration is required on the node for QUIC if the port is open. *** ## **Step 5: Create an Trustkey** **Download the Trustkey Tool**: {% tabs %} {% tab title="Windows" %} PowerShell: ``` [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12; curl https://github.com/silos3/silo-release/releases/download/v1.0.0-P/trustkey_windows_amd64.exe.zip -o trustkey_windows_amd64.exe.zip; Expand-Archive ./trustkey_windows_amd64.exe.zip . -Force; Rename-Item -Path ./trustkey_windows_amd64.exe -NewName trustkey.exe ``` **Generate an Trustkey**: ```bash ./trustkey.exe create silonode ``` **Authorize the Trustkey**: ```bash ./trustkey.exe authorize silonode ``` {% endtab %} {% tab title="Linux" %} ``` curl -L https://github.com/silos3/silo-release/releases/download/v1.0.0-P/trustkey_linux_amd64.zip -o trustkey_linux_amd64.zip unzip -o trustkey_linux_amd64.zip chmod +x trustkey_linux_amd64 sudo mv trustkey_linux_amd64 /usr/local/bin/trustkey ``` **Generate an Identity**: ```bash trustkey create silonode ``` **Authorize the Identity**: ```bash trustkey authorize silonode ``` {% endtab %} {% endtabs %} **Store Securely**: * Ensure the trustkey files are saved in a secure and accessible location. *** ## **Step 6: Install Silo Node Software - Docker** **Pull the Silo Docker Image**: * Use the following command to download the official Silo node Docker image: ```bash docker pull silos3/silo-node:latest ``` {% tabs %} {% tab title="Windows" %} Paste the command into a plain text editor, such as Notepad++ (highly recommended), avoiding any word processing software. ``` docker run --rm -e SETUP="true" --mount type=bind,source="",destination=/app/trustkey --mount type=bind,source="",destination=/app/config --name storagenode silos3/silo-node:latest ``` Substitute `` and `` with your specific parameters, execute the revised command in a terminal, and confirm that your node is now successfully configured. {% endtab %} {% tab title="Linux" %} Copy the command into a plain text editor like a `nano`: ``` docker run --rm -e SETUP="true" \ --user $(id -u):$(id -g) \ --mount type=bind,source="",destination=/app/trustkey \ --mount type=bind,source="",destination=/app/config \ --name storagenode silos3/silo-node:latest ``` Substitute `` and `` with your specific parameters, execute the revised command in a terminal, and confirm that your node is now successfully configured. {% endtab %} {% endtabs %} **Run the Docker Container**: {% tabs %} {% tab title="Windows" %} Paste the command into a text editor, such as Notepad++ (highly recommended), avoiding the use of any word processing software. ``` docker run -d --restart unless-stopped --stop-timeout 300 -p 28967:28967/tcp -p 28967:28967/udp -p 127.0.0.1:14002:14002 -e WALLET="0xXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" -e EMAIL="username@domain.com" -e ADDRESS="domain.ddns.net:28967" -e STORAGE="2TB" --mount type=bind,source="",destination=/app/trustkey --mount type=bind,source="",destination=/app/config --name storagenode silos3/silo-node:latest ``` Modify the values for WALLET, EMAIL, ADDRESS, and STORAGE, replacing `` and `` with your specific parameters. Execute the updated command in your terminal. Congratulations, you are now operating as a Storage Node! {% endtab %} {% tab title="Linux" %} Copy the command into a plain text editor, like a `nano`: ``` docker run -d --restart unless-stopped --stop-timeout 300 \ -p 28967:28967/tcp \ -p 28967:28967/udp \ -p 127.0.0.1:14002:14002 \ -e WALLET="0xXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" \ -e EMAIL="username@domain.com" \ -e ADDRESS="domain.ddns.net:28967" \ -e STORAGE="2TB" \ --user $(id -u):$(id -g) \ --mount type=bind,source="",destination=/app/trustkey \ --mount type=bind,source="",destination=/app/config \ --name storagenode silos3/silo-node:latest ``` Update the WALLET, EMAIL, ADDRESS, and STORAGE fields with your specific parameters, replacing `` and `` accordingly. After making the necessary changes, copy the revised command and execute it in your terminal. Congratulations, you are now operating as a Storage Node! {% endtab %} {% endtabs %} **Check Node Status**: Verify the Silo node is running by listing Docker containers: ```bash docker ps -a ``` **Monitor** : Your node stats ```bash http://127.0.0.1:14002 ``` *** # Payout SILO Node Payout ### Introduction Storage Node Operators are compensated for the resources used by SILO Orbitals for their nodes every month. Our payout policy and details can be found in the [SILO Node Operator Terms and Conditions](https://www.silos3.com/legal/supplier-terms-conditions/). In the event of a conflict between this documentation and the Node Operator Terms & Conditions, the Node Operator Terms & Conditions shall govern. *** ### Understanding How Storage Nodes are Paid on the SILO Network This document explains how Storage Node Operators are compensated for storing data and providing bandwidth. Node Operators are paid for the actual resources used by SILO-operated Orbitals. Any Orbitals operated by third parties not associated with SILO may have different terms, rates, and payment methodologies. *** ### Paid Resources SILO Nodes share unused hard drive capacity and bandwidth with the SILO network and are compensated for the following: 1. **Storage of Storage Materials on Space:**\ Compensation for the storage space used by Orbitals and users. This is calculated in GB-hours per month and paid monthly at the rates listed below. 2. **Egress related to Nexus Clients:**\ Compensation for bandwidth used when users retrieve data from the network through registered Nexus applications. This is calculated in GB of bandwidth utilized and paid monthly at the specified rates. 3. **Egress related to file repair:**\ Compensation for bandwidth used when SILO Orbitals retrieve data from Storage Nodes for the purpose of file repair. This is calculated in GB of bandwidth utilized and paid monthly at the specified rates. 4. **Audit Bandwidth:**\ Compensation for bandwidth used when SILO Orbitals retrieve data to perform audits. This is calculated in GB and paid monthly at the specified rates. *** ### Exclusions Storage Node Fees will not be paid for the following types of resource usage: * **Storage of Garbage Data:** Data on a Storage Node that was not removed after deletion by a Nexus client. Such data will be removed by the SILO garbage collector function. * **Other Resources:** SILO will not compensate for any other resources not explicitly identified above. *** ### Current SILO Node Payout Rates | **Payment Category** | **Rates (as of Jan 1st, 2025)** | | -------------------------- | ------------------------------- | | Storage (per TB per Month) | **$2.03** | | Egress (per TB) | **$2.70** | | Audit/Repair (per TB) | **$2.70** | *** #### Important Note All payouts are made in **SILO tokens**. For example, if your payout totals $100, you will receive $100 worth of SILO tokens. The SILO token's value will be calculated based on its current price as listed on [CoinGecko](https://www.coingecko.com/) or a recognized CEX exchange at the time of the payout. *** For detailed information on how data storage and bandwidth are measured, refer to [SILO Pricing Documentation](/home/pricing).