Buckets and access keys that speak the S3 API — for server backups with restic or rclone, for files your application stores through an S3 SDK, or for archives. One flat monthly price with transfer included: no per-gigabyte download fees, no request charges, no surprises on the day you restore.
s3 · us-west
Example values — your endpoint and keys are in the dashboard.
Works with the tools you already use
Off-site server backups
Point restic, Kopia or rclone at a bucket and run it nightly. Encrypted on your side, stored away from the server it protects — and there is no per-download fee to restore it (it counts toward your monthly transfer, like uploads).
Files for your application
User uploads, generated reports, media: store them through any S3 SDK and hand out pre-signed links for downloads, so files never pass through your web server.
Archives and second copies
Old projects, logs, the extra copy the 3-2-1 rule asks for. Checksummed storage that notices and repairs corruption, at a price you know in advance.
Pick a size — you can upgrade to a larger one from your dashboard at any time, paying only the difference for the rest of the period. Prepay 3, 6 or 12 months for a lower monthly rate.
Billing term
Most object storage looks cheap per gigabyte and then adds charges for every request, every gigabyte downloaded, and early deletion. The day you restore a whole server is the day that bill arrives. Here the plan price covers it.
S3 API
Multipart uploads, pre-signed links and the usual object operations. Path-style addressing, region us-west.
Up to 10 buckets
Create and delete buckets from your dashboard. Your plan size is shared across them.
Private by default
Every request is signed with your key. Share single objects with pre-signed links that expire.
Transfer included
Monthly transfer equal to your plan size. Past it transfers slow down — never cut off, never billed per GB.
Checksummed storage
Mirrored drives with end-to-end checksums that find and repair silent corruption.
HTTPS only
One endpoint with a valid certificate; plain HTTP is redirected to HTTPS.
Your dashboard
The object-storage page in your dashboard, with sample data. Create a bucket, reveal and replace the key, or drag the usage sliders to see what happens at each limit.
Object storage · 1 TB
us-west · United States (West)
Buckets
3 of 10
| Name | Objects | Size | |
|---|---|---|---|
| server-backups | 1,284 | 612 GB | |
| app-uploads | 18,902 | 41.3 GB | |
| archive-2025 | 0 | 0 B |
Your plan size is shared across all buckets. Every bucket is private.
Same location, same flat pricing and transfer rules. The difference is how your tools connect.
| Object storage | Storage box | |
|---|---|---|
| Connect with | The S3 API over HTTPS | SSH on port 23: SFTP, SCP, rsync, Borg |
| Organised as | Up to 10 buckets of objects | One folder tree |
| Sign in with | Access key + secret | Password or SSH keys |
| Share a file | Pre-signed link | — |
| Best for | restic, rclone, Kopia, S3 SDKs, apps | rsync, Borg, SFTP clients, scripts |
Yes — it speaks the S3 API. Point the AWS CLI, rclone, restic, Kopia, Duplicati or an S3 SDK at the endpoint shown in your dashboard, with your access key, the region us-west, and path-style addressing (most tools call it "force path style"). Multipart uploads and pre-signed links work as they do on S3.
None. You pay the monthly price for the plan, and that includes as many requests as you make and monthly transfer equal to the plan size. Past the transfer allowance uploads and downloads slow down; nothing is billed.
Uploads and downloads slow to 2 Mbit/s for the rest of the month (on up to two connections at a time). Nothing is cut off, nothing extra is charged, and the allowance resets on the 1st. Uploads and downloads both count toward it.
New uploads are refused until you delete something or upgrade to a larger size, which you can do from your dashboard at any time. Reading and deleting keep working, so you can always get your data back out.
Yes, from your dashboard, at any time. You pay the difference for the rest of the current period, the extra space and transfer are there within a minute, and your buckets and keys do not change.
Not at launch. Every request needs your access key, or a pre-signed link you generate for a single object. That keeps your data private by default, and pre-signed links cover sharing a file or letting your application's users download one.
Not yet. If your backup software needs immutable (locked) storage — some Veeam setups do — this is not the right fit today. restic and Kopia keep their own snapshot history, so overwriting a file does not lose its older versions.
In one location in the western United States, on mirrored drives with checksums that detect and repair silent corruption. It is not copied to a second region. Object storage is often where backups go; for anything irreplaceable, keep one more copy somewhere else.
Object storage if your tools speak S3 or your application stores files through an S3 SDK. A storage box if you use SFTP, rsync or Borg over SSH. Both have the same flat pricing and transfer rules, and both live in the same place.
Switching
Moving From B2, Wasabi or S3arrow_forward
Copy a bucket with rclone and switch your tools over.
Storage
Need SFTP, rsync or Borg?arrow_forward
Storage boxes: plain storage over SSH, same flat pricing.
Servers
Pair It With a VPSarrow_forward
Back up your Virteche servers to a bucket in another region.