RemarkableCloud

Features / S3 Backup Storage

What is the S3 backup destination?

S3-compatible object storage is the second, independent leg of the dual backup system included with every plan: a separate technology in a separate location holding its own copy of your data.

How it works, technically

Object storage is a different animal from server storage: data is stored as immutable objects, addressed by key, replicated internally, and accessed over an S3-compatible API. That difference is the point: a failure mode that damages a filesystem or a backup server cannot express itself against an object store.

Within the platform, the S3 leg receives backup copies independently from the PBS leg, and both are exercised by the weekly restore verification. If you have advanced needs, S3-compatible tooling (rclone, restic, and friends) speaks the protocol natively, ask support about direct use for your workflows.

The independent second copy

Backupproduced 1 Object storewrite 2 Internalreplication 3 Verifiedrestorable 4

Interface

S3-compatible API

Role

Second leg of dual backups

Independence

Separate tech + location from PBS

Verification

Included in weekly restore tests

FAQ

S3 Backup Storage, answered.

Is this a general-purpose S3 bucket for my apps?

Its included role is backup storage. If your project needs S3 for application data, talk to support about options.

Why S3-compatible specifically?

The S3 API is the industry standard for object storage: mature tooling, predictable behavior, and easy verification.

Where does it live?

Offsite, in separate infrastructure from both your VPS and the PBS system, that separation is its job.

Your server runs. You sleep.

Fully managed hosting from people who have been doing this since 2001.