Storage Node — Getting Started
1. Storage Node Overview
Storage Node gives you fixed-size file storage you can access through standard protocols. There is no operating system, no compute resources, and no way to run software or processes. It is pure storage.
When you order, you get:
- A fixed storage capacity (for example, 1 TB or 5 TB)
- An internal IP address for access within your location
- A username and password
- Access through SFTP, FTP, and SMB
Your credentials and connection details arrive by email once the service is ready.
Billing starts at the moment of purchase. One billing period is 30 days.
2. Network Access
Internal access
By default, your storage node gets a private IP address. It is only reachable from servers in the same location. All protocols work over this internal network.
One location covers all data centers in the same location. If your storage node and your server are both in Frankfurt, they are on the same local network, regardless of which data center each is in.
Public access
To reach your storage from outside your location, you need to add Public Access to your storage instance. You can order this through the control panel.
Public Access includes a monthly traffic allowance. Inbound and outbound traffic are counted together. Once the allowance runs out, speed drops to 10 Mbit/s for the rest of the billing period. You can buy extra traffic at any time.
Traffic resets at the start of each new billing period.
Available Public Access plans:
| Plan | Included traffic | Price |
| SNB-IC-10 | 10,000 GB / month | $4.99/mo |
| SNB-IC-20 | 20,000 GB / month | $8.99/mo |
| SNB-IC-30 | 30,000 GB / month | $12.99/mo |
| SNB-IC-50 | 50,000 GB / month | $19.99/mo |
| SNB-IC-100 | 100,000 GB / month | $34.99/mo |
Without Public Access, there is no way to reach your storage from outside the location.
3. Supported Protocols
3.1 SFTP (Recommended)
Port 22. Encrypted. The account is set up for file transfer only. There is no shell, no command execution, no running processes. Each user can only access their own storage directory.
Works on the internal network and over the internet when Public Access is enabled.
Good for backups, automated transfers, file sync, and secure remote access.
Clients that work with SFTP: FileZilla, WinSCP, rclone, the native sftp command on Linux and macOS.
3.2 FTP
Port 21. Passive mode is supported. Uses the same credentials as SFTP. You can upload, download, rename, delete, and manage directories. No shell, no system access.
Available on the internal network by default. Works externally when Public Access is enabled.
If you are connecting from behind NAT or a firewall, use passive mode.
FTP is there for legacy systems and integrations that do not support SFTP. For anything new, SFTP is the better choice since it does the same job with encryption.
3.3 SMB (Samba)
Port 445. Internal network only. This protocol is not exposed to the internet.
SMB is useful when you want to mount your storage as a network drive and access files directly from servers in the same location.
Windows:
\\INTERNAL_IP\public
Linux:
First, make sure cifs-utils is installed:
sudo apt install cifs-utils
Create a directory where the storage will be mounted:
sudo mkdir /dir-name/storage-name
Then mount it:
sudo mount -t cifs //INTERNAL_IP/public /mnt/storage -o username=YOUR_USERNAME,password=YOUR_PASSWORD
4. Authentication
Each storage instance has its own username and password. The same credentials work across all protocols.
You only have access to your own allocated storage space. There is no way to access other instances or any system-level data.
5. Security
Use SFTP wherever you can. FTP sends your credentials and data in plain text, so avoid it on public networks or anywhere traffic might be intercepted.
Do not share your credentials with third parties. Do not put them in scripts that are stored in publicly accessible places.
6. Limitations and Performance
Storage Node runs on shared distributed infrastructure. It is intended for backup storage, data archiving, and server migration.
Transfer speed is not capped, but it depends on the current load of the shared infrastructure. No IOPS or throughput guarantees are provided.
This service is not suitable for high-traffic public download mirrors, video streaming to end users, heavy P2P activity, or any workload that needs consistent high IOPS. Running these without a separate agreement is not allowed under GTHost Terms of Service, Section 14.5.
The service does not include shell access, command execution, application hosting, background processes, or managed backup and versioning.
You are responsible for checking data integrity after upload and keeping independent copies of anything critical. Verifying uploads with checksums before deleting source files is a good practice.