Is Nordic Data Sync 100% wire-compatible with AWS S3 SDKs?
Yes. Our gateway implements the S3 REST API with Signature Version 4, multipart uploads up to 5 TB per object, byte-range GETs, conditional ETags (If-Match / If-None-Match), and S3 Object Lock headers. Drop in our endpoint URL with aws-cli, boto3, Go AWS SDK v2, Terraform, Restic, Kopia, Velero, or pgBackRest with zero code changes.
How are encryption keys managed and who can read our data?
Zero-knowledge by design. When using client-side encryption (SSE-C, Restic, Kopia, or pgBackRest cipher keys), blocks are encrypted in your host's RAM before touching the network. Beneath that, every NVMe and SAS drive uses hardware XTS-AES-256 self-encryption tied to our Stockholm HSM cluster.
Are there hidden egress charges or minimum retention penalties?
None. Unlike archival cloud tiers that impose 30- to 90-day minimum object duration fees when rotating daily backups, Nordic Data Sync bills strictly on hourly average gigabytes stored, and includes free outbound egress up to 3x your stored volume (unlimited on Enterprise WAL plans).
How does QUIC HTTP/3 acceleration help backup throughput?
On cross-border or high-latency paths, a single dropped packet stalls an entire TCP TLS connection. Our edge supports RFC 9000 QUIC (HTTP/3 on UDP :443) alongside TCP HTTP/2, multiplexing streams independently with BBRv3 congestion control.
Can we sign a custom GDPR Art. 28 DPA and pay via SEPA invoice?
Yes. All EU/EEA corporate accounts receive a counter-signed GDPR Data Processing Agreement, ISO/IEC 27001:2022 certificate package, and net-30 SEPA EUR or SEK invoicing (Peppol BIS Billing 3.0 supported).