A separate home for lawful transfers
A storage-focused environment for distributing and retrieving files you are authorised to handle.
Content revised · English
- Architecture to evaluate
- Transfer client / disk cache / lawful library
- Prepared starting points
- 3 plans
- Responsibilities
- Application, rights and recovery
A fit shortlist, not installed software or live inventory.
Keep these in view.
- Transfer client / disk cache / lawful library.
- Match the disk to the access pattern.
- Playback does not always mean transcoding.
Transfer client / disk cache / lawful library
qBittorrent, Deluge and rTorrent can be evaluated as clients with their own web-interface and maintenance needs. Restrict the control UI and budget active connections, disk cache and storage growth. Use only content you are entitled to receive and share.
Match the disk to the access pattern
Large sequential libraries can suit capacity-oriented storage; many active pieces and concurrent reads have different I/O needs. Compare the exact product’s quota or unmetered fair-use condition. “Unmetered” is not a permission to exhaust shared resources or ignore policy.
Playback does not always mean transcoding
Direct play and transcoding in Jellyfin or Plex impose different CPU/GPU loads. Codec, client device and concurrent sessions determine the work. No untested torrent-count or playback-count promise is made; measure the chosen library and software.
Work within the rights
A seedbox is a remote transfer system, not permission to distribute copyrighted material. Confirm content rights, provider rules and any port or protocol restrictions before use.
Balance storage and traffic
Sustained transfers can be limited by disk I/O, network ports or monthly allowances. Distinguish the amount you can store from how quickly you can move it.
Protect the control interface
Restrict the web interface, use encrypted administrative access and keep downloaded content away from publicly served directories. Define cleanup rules so temporary data does not fill the filesystem.
Capacity to consider.
Match these starting points to the representative application. Software installation and live inventory are not connected; the exact specification and period total come from the catalogue.
Vault 2
Store backups, archives or authorised media on a 2 TB HDD configuration with two virtual CPUs and 4 GB of memory. The 10 TB monthly transfer allowance and 1 Gbps port suit scheduled file movement, with rTorrent and Jellyfin as the listed software stack choices.
- Compute
- 2 vCPU
- Memory
- 4 GB DDR4
- Storage
- 2 TB HDD
- Transfer
- 10 TB / month
billed monthly
Vault 8
Grow an archive to 8 TB of HDD storage with four virtual CPUs, 8 GB of memory and unmetered transfer on a 1 Gbps port. A seedbox software stack and an S3-compatible object-storage option support file workflows, with access controls and retention configured for your use case.
- Compute
- 4 vCPU
- Memory
- 8 GB DDR4
- Storage
- 8 TB HDD
- Transfer
- Unmetered
billed monthly
Vault 16
Combine 16 TB of HDD storage, four virtual CPUs and 16 GB of memory for larger backup sets and file collections. The configuration adds cold-storage snapshots and LUKS encryption to unmetered transfer on a 1 Gbps port, while recovery and key management remain part of your storage design.
- Compute
- 4 vCPU
- Memory
- 16 GB DDR4
- Storage
- 16 TB HDD
- Transfer
- Unmetered
billed monthly
Before this workload goes live.
- Check the exact plan’s CPU, memory, disk, transfer and port.
- Choose a listed region and verify the workload’s permitted use.
- Test the representative application and an independent restore.
Questions, answered.
Is unmetered transfer unlimited resource use?
No. The exact storage plan’s transfer rule and fair-use policy still apply. Budget the client’s active connections and sustained traffic.
Can several transfer clients run together?
Technically compatible software may share a system, but it increases storage and connection demand. Test the actual access pattern and keep each web control endpoint secured.
Is HDD always too slow?
Sequential storage and many concurrent random pieces stress disks differently. Match the real I/O workload instead of choosing solely from capacity or a technology label.
How are torrent complaints handled?
P2P requires the relevant rights. The proposed ordinary complaint and urgent-harm process applies; a seedbox plan is not a guarantee that every notice is ignored.
What is kept in my account workspace?
Your configuration, selected plan, image, location and billing term are kept with the order and payment request references. Quotes, payment-state reads and support conversations remain linked to your account. Read fulfilment details separately from payment status.