info@intercolo.net +49 (0)69 564060 Frankfurt am Main
เข้าสู่ระบบ ลงทะเบียน
S3-compatible · straight into Hyper Backup

Synology C2 Alternative from Frankfurt

Plugs straight into Hyper Backup, Active Backup for Business and Cloud Sync as S3 Storage. Endpoint https://de-fra.i3storage.com, region de-fra, SigV4 — a German operator with a DPA, a transparent per-TB price, no egress trap. From €2.49 per TB/month.

ทดลองฟรี ถามเราโดยตรง
intercolo vs. US-Clouds
ศูนย์ข้อมูลแฟรงก์เฟิร์ต อัม ไมน์ Frankfurt, DE
GDPR / DPA Art. 28
ทราฟฟิกรวมอยู่แล้ว 1 TB / TB
เริ่มต้น €2.49 ต่อ TB พื้นที่จัดเก็บ
Hyper Backup
native S3
German operator
DPA / Art. 28
from €2.49
per TB/month
For Synology NAS users

The honest, German alternative to Synology C2

Synology C2 is convenient, but it ties you to the Synology ecosystem: the C2 Backup Vault is a proprietary target, the applicable law depends on the region you pick, and both price and restore behaviour are plan-bound. intercolo i3 Object Storage takes the open route: an S3-compatible backup target that plugs into Hyper Backup simply as S3 Storage — reached via the endpoint https://de-fra.i3storage.com in region de-fra using SigV4. Run by a German provider with a DPA under Art. 28 GDPR, in a Frankfurt data center, on 100% green power, at 99.999999% durability and strong read-after-write. A transparent per-TB price, no egress trap — and your data never leaves Frankfurt.

Why switch

Away from the proprietary vault, toward the open S3 standard

The C2 Backup Vault is tied to your Synology account and Synology's cloud — available in regions such as Europe, North America and Asia, where the US region can bring US law (CLOUD Act) into play. Price and restore behaviour depend on the chosen plan. The open S3 standard at intercolo flips that: no lock-in, any S3-capable tool talks to the same endpoint, and your objects stay freely portable at any time — via aws-cli, rclone or straight from Hyper Backup. A single location, Frankfurt data center, a German operator, Schrems II safe: no access under US law, one point of contact, one legal regime.

Away from the proprietary vault, toward the open S3 standard

Switch Hyper Backup to S3 Storage — step by step

1

Create a new backup task

In Hyper Backup on the NAS: plus sign → Back up folders and packages. As the backup destination, choose S3 Storage — the generic, S3-compatible target, not the hard-wired C2 entry.

2

Enter server & region

For the S3 server pick Custom Server URL and enter de-fra.i3storage.com as the server address (without a leading https://). Signature version: v4. Enable the Enable transfer encryption option so the connection runs over TLS.

3

Store credentials (SigV4)

Enter the Access Key and Secret Key from your intercolo API key pair. Access runs exclusively through these SigV4 keys — no password login. For multiple NAS units or jobs, create a dedicated key pair for each.

4

Pick a bucket

Select the bucket from the list (or pre-create it via aws-cli/rclone) and optionally a directory. One bucket can hold several backup tasks as long as each task uses its own directory.

5

Client encryption & rotation

In the next step enable client-side encryption with your own password — Hyper Backup then encrypts BEFORE upload. Finally set version rotation (Smart Recycle or a fixed number of versions), which governs your retention.

Check the endpoint: create & list a bucket

bash 
# Synology "S3 Storage" — exact values for Hyper Backup:
#   S3 server        : Custom Server URL
#   Server address   : de-fra.i3storage.com
#   Signature version: v4
#   Bucket           : synology-backup     (example)
#   Access Key       : <ACCESS_KEY>
#   Secret Key       : <SECRET_KEY>

# Pre-create the bucket and verify credentials (AWS CLI, SigV4):
aws --endpoint-url https://de-fra.i3storage.com \
    --region de-fra \
    s3 mb s3://synology-backup

# List contents after the first Hyper Backup run:
aws --endpoint-url https://de-fra.i3storage.com \
    --region de-fra \
    s3 ls s3://synology-backup/ --recursive --human-readable

# Alternatively via rclone (remote 'i3'):
rclone --s3-endpoint https://de-fra.i3storage.com \
       --s3-region de-fra  mkdir i3:synology-backup

Path-style: https://de-fra.i3storage.com/synology-backup · Virtual-hosted: https://synology-backup.de-fra.i3storage.com. Both work; in Hyper Backup you enter the server address without https:// and enable transfer encryption.

Synology C2 vs. intercolo as a backup target

Synology C2 intercolo
Location / operator Regions EU/US/Asia, operated by Synology (Taiwan) Frankfurt DC, German operator, 100% DE
DPA under Art. 28 GDPR Depends on region and contract DPA included, GDPR-compliant
Data residency / law Region selectable, US region → US law possible German operator, Schrems II safe
Access via open S3 API C2 Backup Vault proprietary, no open S3 Yes — S3-compatible, SigV4
Ecosystem lock-in Tied to Synology account and C2 Open standard, freely portable
Egress / restore Plan- and tier-dependent 1 TB incl./TB, then +€3.99/TB
Storage pricing model Package-/plan-bound from €2.49 per TB/month

Honest: no Object Lock, no versioning on the storage side

To set expectations correctly: i3 Object Storage provides NO storage-side immutability — no Object Lock/WORM and no object versioning. Instead you govern retention through rotation in Hyper Backup (Smart Recycle or a fixed version count) and through the 3-2-1 principle: this off-site target in Frankfurt is your 2nd copy alongside the local NAS and a further copy. For confidentiality, enable client-side encryption in Hyper Backup with your own password — data is encrypted BEFORE upload, the key stays with you, and only ciphertext lands in storage. Transport is additionally secured over TLS. Store the password safely: no key, no restore.

Not just Hyper Backup — your whole Synology stack

Hyper Backup

Backs up folders, packages and the system configuration straight to Frankfurt as S3 Storage. With client-side encryption and version rotation, it is your classic off-site backup target — right where C2 used to sit.

Active Backup for Business

Active Backup for Business first backs up VMs, PCs and servers locally to the NAS. You then offload those ABB repositories via Hyper Backup as an off-site 2nd copy into the S3-compatible storage in Frankfurt.

Cloud Sync

Cloud Sync connects a folder directly to an S3-compatible target: connection type S3 Storage with Custom Server URL de-fra.i3storage.com, region de-fra and SigV4 — one-way or two-way sync with no detour.

aws-cli & rclone

For scripts and automation you address the same endpoint directly. Create, list, sync a bucket — every S3 tool works against https://de-fra.i3storage.com with region de-fra, independent of the Synology ecosystem.

No egress trap

Restores and recovery tests stay predictable

The most expensive backup mistake is the untested restore. Per booked TB of storage, 1 TB of egress is included — enough to cover regular recovery tests and real restores from Hyper Backup without the next invoice exploding. Extra traffic is billed transparently at +€3.99/TB: predictable, not surprising. You know what a restore costs before you run it — and therefore test as often as your recovery strategy demands. That is exactly what plan-bound models lack, where every retrieval test becomes a cost question.

Restores and recovery tests stay predictable

Multiple NAS units, multiple jobs — cleanly separated

If you run several NAS units or want to separate backup tasks, create a dedicated API key pair (access/secret) and a dedicated bucket for each. Access runs purely through these SigV4 keys — no account sharing, no complex bucket policies needed. A compromised or retired device is rotated in isolation without touching other backups. Every backup chain stays organisationally separated, billable per bucket and cleanly attributable — the blast radius of a single key stays small.

บริการย้ายพื้นที่จัดเก็บ

เราย้ายข้อมูลให้คุณ

ประสบการณ์ของเราพูดแทนตัวเอง: เราย้ายข้อมูลสำเร็จแล้วหลายเพตะไบต์และไฟล์กว่า 500 ล้านไฟล์

500M+
files migrated
Petabytes
of data migrated
since 2006
in business
ติดต่อเรา
FAQ

ยังมีคำถามเพิ่มเติม?

ถามเราโดยตรง
Yes. In Hyper Backup choose S3 Storage as the destination, Custom Server URL for the S3 server, and enter de-fra.i3storage.com as the server address. Region de-fra, signature version v4, plus your access/secret key pair (SigV4) and the bucket — done.
Yes. i3 Object Storage replaces C2 as a backup target for Hyper Backup, Active Backup for Business (via Hyper Backup offload) and Cloud Sync. The difference: an open S3 standard instead of the proprietary C2 vault, a German operator with a DPA, and a transparent per-TB price.
Transport runs over TLS. For confidentiality, enable client-side encryption in Hyper Backup with your own password — data is encrypted before upload, the key stays with you and only ciphertext lands in storage. There is no storage-side at-rest encryption.
No — there is neither Object Lock/WORM nor object versioning on the storage side. You govern retention through rotation in Hyper Backup (Smart Recycle or a fixed version count) and through 3-2-1: this target is the off-site 2nd copy alongside your local NAS.
Per booked TB of storage, 1 TB of egress is included, which covers regular restores and recovery tests. Traffic beyond that costs a predictable +€3.99/TB — not a blanket free model, but one you can calculate in advance.
Yes. Cloud Sync connects a folder directly as S3 Storage to de-fra.i3storage.com. Active Backup for Business backs up locally to the NAS; you then offload those repositories via Hyper Backup as an off-site copy into the S3 storage in Frankfurt.
Both: path-style https://de-fra.i3storage.com/<bucket> and virtual-hosted https://<bucket>.de-fra.i3storage.com. In Hyper Backup the server address de-fra.i3storage.com with region de-fra is enough; for aws-cli/rclone, --endpoint-url https://de-fra.i3storage.com suffices.
ทดลองใช้ฟรี 1 เดือน

ทดลองใช้พื้นที่จัดเก็บที่รองรับ S3 ของเราฟรี 1 เดือน

ทดลองตอนนี้ พื้นที่จัดเก็บ