Share access, keep control
Infrastructure for authorised file exchange with a clear permission model.
Content revised · English
- Architecture to evaluate
- Nextcloud / Seafile / FileBrowser
- Prepared starting points
- 5 plans
- Responsibilities
- Application, rights and recovery
A fit shortlist, not installed software or live inventory.
Keep these in view.
- Nextcloud / Seafile / FileBrowser.
- Give recipients narrow access.
- Separate the interface from large capacity.
Nextcloud / Seafile / FileBrowser
Nextcloud offers a collaboration-oriented application, Seafile a synchronisation-oriented model and FileBrowser a smaller file UI. Choose the maintained software that fits the access pattern, then secure TLS and back up both file data and any application database.
Give recipients narrow access
Use permissions, expiration dates and revocation for shared links. Review how much a link holder can list or download. Client-side encryption can be evaluated with a tool such as Cryptomator, but filenames, access timing and recipient devices still need attention.
Separate the interface from large capacity
A VPS front end and a storage tier can form a design when their network, authentication and availability are configured. The catalogue does not automatically connect them. Document each dependency and restore a test file plus application metadata before opening access.
Define who receives what
Public downloads, team collaboration and confidential exchange need different interfaces. Use expiring links and access permissions where the application supports them, and avoid sharing an administrative account.
Understand the storage layer
Filesystem storage and an S3-compatible service solve different application needs. Object compatibility alone does not guarantee identical behaviour, durability or performance to another platform.
Control the lifecycle
Set file size limits, retention rules and malware handling. Keep quotas and available space visible, and verify that deletion and backups behave the way recipients expect.
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.
Umbra 2
Give web applications, containers or a private tunnel two AMD EPYC virtual CPUs, 4 GB of ECC memory and 60 GB of NVMe storage. Root access on KVM, a 1 Gbps port and 3 TB of monthly transfer provide more room than the entry configuration without moving to dedicated hardware.
- Compute
- 2 vCPU (AMD EPYC)
- Memory
- 4 GB DDR4 ECC
- Storage
- 60 GB NVMe SSD
- Transfer
- 3 TB / month
billed monthly
Umbra 4
Balance four AMD EPYC virtual CPUs and 8 GB of ECC memory with 120 GB of NVMe storage for several services or a growing application. This KVM configuration includes a weekly snapshot, 6 TB of monthly transfer on a 1 Gbps port and a 20 Gbps network mitigation tier.
- Compute
- 4 vCPU (AMD EPYC)
- Memory
- 8 GB DDR4 ECC
- Storage
- 120 GB NVMe SSD
- Transfer
- 6 TB / month
billed monthly
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.
Which stack is the easiest?
The answer depends on whether the project needs collaboration, synchronisation or a minimal file UI. Compare the maintained Nextcloud, Seafile and FileBrowser requirements with the administrator’s skills.
Can recipients use end-to-end encrypted files?
Evaluate and test an appropriate client-side encryption workflow and key sharing. Public links, filenames, access timing and recipient devices can remain exposed.
Does the host inspect every file?
No production storage service or inspection policy is connected. A launch operator must describe its actual access, request handling and retention instead of promising universal scanning or no scanning.
Can a public share link expire?
That is an application control to configure and test. Use narrow permissions, expiry and revocation, and verify the recipient experience; a catalogue plan does not set those rules.
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.