# Vault Storage

> Make room for the data behind your project. Vault separates a dedicated NVMe boot drive from configurable SAN storage, with CPU, memory and transfer allowances you can size independently.

Canonical human page: https://swissoctet.com/services/vault/

SwissOctet public catalogue. Currency: USD. Location: Switzerland / CH. The fixed-address crypto checkout uses a public USD rate to calculate the exact amount for the selected asset and network, with a 25-minute payment window. This browser quote is not a server-issued invoice. Transaction attribution, payment confirmation and provisioning require the operator’s backend.

Room for media, archives and growing datasets. A storage-focused Linux configuration.

## Starting configuration
Starting configuration: Vault Storage 01 (vault-01); USD 62.42 effective monthly base on the shortest available 1-month term; USD 62.42 base charge for that term. Add-ons and applicable tax are separate.

| Starting-plan specification | Listed value |
| --- | --- |
| CPU Cores | 2 |
| RAM | 8GB |
| SAN Disk Size [GiB] | 5000 GB (Upgradable) |
| Bandwidth limit [TB] | 20TB |
| IPv4 Addresses | 1 |
| Boot Drive | 50GB NVME |

## Service capabilities
### Separate system and data storage
The configuration lists an NVMe boot drive alongside SAN capacity, making the system volume distinct from the space intended for larger datasets.

### Capacity as a configuration choice
Choose the SAN storage option that matches your data volume and expected growth. Read the units in the selector when calculating usable capacity.

### Processing resources for stored data
Adjust CPU cores and memory for indexing, checksums, cataloguing or applications around the storage, rather than selecting capacity alone.

### Transfer and addresses under control
Select a traffic allowance and IPv4 count suited to the workflow. Storage capacity and monthly data transfer are separate parts of the configuration.

## Example workloads
### Media and document libraries
Keep larger collections behind an application that controls who can browse, upload or retrieve each item.

### Dataset repositories
Provide a Swiss storage environment for project data, exports and research collections with a defined access policy.

### Backup destinations
Use storage as one component of an independent backup strategy, with encryption, retention and restoration tests under your control.

## A closer look
### Plan for growth before filling the volume
Count the data you already hold, the rate at which it grows and any temporary space needed for processing. Capacity options allow a larger data allocation, while the boot drive remains a separate specification. Filesystem overhead and your storage layout can change the space an application sees.

### Data movement belongs in the same calculation
A large storage volume may be quiet most days or move substantial amounts of data. Initial uploads, regular backups and repeated downloads all affect traffic. Choose the bandwidth allowance alongside storage, then ensure your own connection and software can complete the workflow within the required time.

### Decide how the data should remain private
You control the software and access model around the stored files. Encrypt sensitive archives before upload where appropriate, keep encryption keys separate, and restrict storage interfaces to authorised users. A storage environment can hold a backup, but the existence of a second folder does not by itself make the original data recoverable.

### Choose the storage interface as well as the capacity
Vault lists SAN capacity, an NVMe boot drive and Linux template choices. Decide whether applications will read a local volume or use a file-sharing service such as NFS or SMB, then check operating-system support and protect the interface. Ceph, RBD, replication and failover describe possible storage architectures; the operator must confirm the actual backend and recovery scope before they become service commitments.

## Configurations and billing
Base prices exclude separately selected add-ons. The actual configuration total, availability, delivery, licences and any applicable tax are confirmed before a real order.

### Vault Storage 01
A storage-oriented Linux configuration with a listed 5,000 GB SAN allocation and a separate 50 GB NVMe boot drive. Two CPU cores, 8 GB of memory and 20 TB of traffic support archive and file-storage projects.

Configuration ID: vault-01. Location: Switzerland / CH. Availability: confirm availability on the final quote.

Nominal monthly base rate before billing-period pricing: USD 62.42. This rate is not a separate payable invoice total.

Shortest available billing term: 1 month. Base charge for this term: USD 62.42; displayed effective monthly base: USD 62.42. Selected add-ons and applicable tax are separate.

| Specification | Listed value |
| --- | --- |
| CPU Cores | 2 |
| RAM | 8GB |
| SAN Disk Size [GiB] | 5000 GB (Upgradable) |
| Bandwidth limit [TB] | 20TB |
| IPv4 Addresses | 1 |
| Boot Drive | 50GB NVME |

#### Available billing periods
| Duration | Displayed effective monthly base | Total base for period |
| --- | --- | --- |
| 1 month | USD 62.42 | USD 62.42 |
| 3 months | USD 62.42 | USD 187.27 |
| 6 months | USD 62.42 | USD 374.54 |
| 12 months | USD 62.42 | USD 749.08 |

#### Plan-specific available choices
##### CPU allocation
| Choice | Listed monthly add-on price | Default for this plan |
| --- | --- | --- |
| 2 CPU Cores | USD 0.00 | Yes |
| 4 CPU Cores | USD 13.77 | No |
| 6 CPU Cores | USD 18.36 | No |
| 8 CPU Cores | USD 27.54 | No |
| 10 CPU Cores | USD 36.72 | No |
| 12 CPU Cores | USD 45.90 | No |
| 14 CPU Cores | USD 55.08 | No |
| 16 CPU Cores | USD 64.26 | No |
| 18 CPU Cores | USD 73.44 | No |
| 20 CPU Cores | USD 82.62 | No |
| 22 CPU Cores | USD 91.80 | No |
| 24 CPU Cores | USD 100.98 | No |
| 26 CPU Cores | USD 110.16 | No |
| 28 CPU Cores | USD 119.34 | No |
| 30 CPU Cores | USD 128.52 | No |
| 32 CPU Cores | USD 137.70 | No |

##### Memory [GB]
| Choice | Listed monthly add-on price | Default for this plan |
| --- | --- | --- |
| 8 GB RAM | USD 0.00 | Yes |
| 16 GB RAM | USD 9.18 | No |
| 24 GB RAM | USD 16.52 | No |
| 32 GB RAM | USD 23.87 | No |
| 40 GB RAM | USD 31.21 | No |
| 48 GB RAM | USD 36.72 | No |
| 64 GB RAM | USD 51.41 | No |
| 128 GB RAM | USD 110.16 | No |
| 256 GB RAM | USD 227.66 | No |

##### SAN Disk Size [GiB]
| Choice | Listed monthly add-on price | Default for this plan |
| --- | --- | --- |
| SAN Disk Size 5000 GiB | USD 0.00 | Yes |
| SAN Disk Size 10000 GiB | USD 50.49 | No |
| SAN Disk Size 15000 GiB | USD 100.98 | No |
| SAN Disk Size 20000 GiB | USD 137.70 | No |
| SAN Disk Size 25000 GiB | USD 183.60 | No |
| SAN Disk Size 30000 GiB | USD 229.50 | No |
| SAN Disk Size 35000 GiB | USD 275.40 | No |
| SAN Disk Size 40000 GiB | USD 321.30 | No |
| SAN Disk Size 45000 GiB | USD 367.20 | No |
| SAN Disk Size 50000 GiB | USD 413.10 | No |
| SAN Disk Size 55000 GiB | USD 459.00 | No |
| SAN Disk Size 60000 GiB | USD 504.89 | No |
| SAN Disk Size 65000 GiB | USD 550.79 | No |
| SAN Disk Size 70000 GiB | USD 596.69 | No |
| SAN Disk Size 75000 GiB | USD 642.59 | No |
| 80,000 GiB SAN · variant A · operator quote | Operator quote required; not assumed free | No |
| 80,000 GiB SAN · variant B · operator quote | Operator quote required; not assumed free | No |
| SAN Disk Size 90000 GiB | USD 780.29 | No |
| SAN Disk Size 95000 GiB | USD 826.19 | No |
| SAN Disk Size 100000 GiB | USD 872.09 | No |

##### Bandwidth limit [TB]
| Choice | Listed monthly add-on price | Default for this plan |
| --- | --- | --- |
| 20TB | USD 0.00 | Yes |
| 40TB | USD 27.54 | No |
| 60TB | USD 41.31 | No |
| 80TB | USD 55.08 | No |
| 100TB | USD 73.44 | No |
| 150TB | USD 119.34 | No |
| 200TB | USD 165.24 | No |

##### IPv4 allocation
| Choice | Listed monthly add-on price | Default for this plan |
| --- | --- | --- |
| 1 | USD 0.00 | Yes |
| 2 | USD 3.67 | No |
| 3 | USD 6.43 | No |
| 4 | USD 8.26 | No |
| 5 | USD 11.02 | No |

##### Operating system image
| Choice | Listed monthly add-on price | Default for this plan |
| --- | --- | --- |
| Debian 11 (Stable) | USD 0.00 | Yes |
| Ubuntu 20 (Stable) | USD 0.00 | No |
| Ubuntu 21 (Stable) | USD 0.00 | No |
| Ubuntu 22 (Stable) | USD 0.00 | No |

## Service questions
### What is the difference between the boot drive and SAN storage?
The catalogue lists the NVMe boot drive separately from the SAN allocation. Plan the operating system and large data volume as distinct storage components.

### Why do some labels use GB and others GiB?
The catalogue preserves the source units for each specification and option. Compare the actual selected capacity and confirm the allocation rather than treating different unit labels as interchangeable.

### Does more storage also include more traffic?
No. SAN capacity and the bandwidth allowance have separate selectors. Check both in the configuration summary when preparing a data-heavy workflow.

### Is Vault automatically a backup service?
Vault is a storage configuration. You still need backup software or a transfer process, retention rules, encryption where appropriate and a tested restoration procedure.

### Can I increase processing resources as well as capacity?
Yes. The configurator includes CPU-core and memory choices in addition to SAN storage, traffic and IPv4 addresses. Select resources for the applications using the data.

### Can I provide NFS or SMB access to the stored files?
A supported Linux setup can run a suitable file-sharing service. Verify package support, authentication and firewall rules, and restrict storage access to the intended users or private network.

### Is Ceph replication or RBD guaranteed for Vault?
The current catalogue specifies SAN capacity, not a verified Ceph topology or RBD interface. Confirm backend technology, redundancy, failure handling and recovery responsibility with the operator.

### Can the allocation grow after the server is delivered?
The catalogue lists capacity options for the initial request. Later resizing, filesystem changes and any downtime must be confirmed for the installed environment.

## Relevant guides
- [When NVMe makes a difference to your application](https://swissoctet.com/insights/nvme-storage-when-it-matters/index.txt): Distinguish capacity, latency and throughput so that a faster storage label answers a real application problem.
- [Build a backup you can actually restore](https://swissoctet.com/insights/build-a-backup-you-can-restore/index.txt): Choose a recovery target, protect an independent copy and practise the restoration before an incident forces the issue.
- [Swiss data residency: map the whole service](https://swissoctet.com/insights/swiss-data-residency-map/index.txt): A Swiss server location is a starting point. Map application data, backups, support access and external services before making a residency commitment.
- [Turn RPO and RTO into a recovery budget you can test](https://swissoctet.com/insights/rpo-rto-recovery-budget/index.txt): Translate acceptable data loss and interruption into a timed recovery plan, with dependencies, restore capacity and a measurable exercise.
- [Snapshots and backups: choose the failure you need to survive](https://swissoctet.com/insights/snapshots-backups-consistency/index.txt): Compare recovery points, failure boundaries and application consistency instead of assuming a snapshot and an independent backup provide the same protection.
- [Object, file or block storage: choose the interface your application needs](https://swissoctet.com/insights/object-file-block-storage/index.txt): Distinguish storage interfaces, access semantics and operational responsibilities before turning a capacity requirement into an application architecture.
- [Publish an onion service without overlooking the application](https://swissoctet.com/insights/publish-onion-service-safely/index.txt): Plan a legitimate onion publication with controlled backend exposure, careful content review, service-key recovery and an explicit audience-access model.
- [Choose a hosting operating model before choosing a cloud](https://swissoctet.com/insights/choose-a-hosting-operating-model/index.txt): Compare shared hosting, a VPS, dedicated hardware and large cloud platforms through responsibility, recovery, dependencies and the complete operating budget.