Documentation

QuietSync is a background relay infrastructure designed to be invisible. This guide covers setup, configuration, and best practices for using the private beta.

Quick start

Once you receive an invite, you'll get a connection string. That's all you need. There's nothing to install on your end.

Your connection string looks like this:

# Connection string format
host: quietsync.org
port: 443
secret: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Configuration

QuietSync requires no client-side software. The relay is configured server-side at account provisioning. The following parameters are fixed at account creation:

• host — always quietsync.org (DNS round-robin across all nodes)
• port — 443 by default, 8443 as fallback
• secret — unique per account, rotate via API (see API reference)

Node overview

QuietSync operates 6 relay nodes across 4 regions. Each node runs independently — if one becomes unavailable, DNS stops resolving to that IP within 30 seconds.

# Active nodes (March 2025)
eu-west-1   Frankfurt    ✓  ~11ms
eu-west-2   Amsterdam    ✓  ~14ms
us-east-1   New York     ✓  ~9ms
us-west-1   Los Angeles  ✓  ~17ms
ap-se-1     Singapore    ✓  ~22ms
ap-ne-1     Tokyo        ✓  ~19ms

Failover logic

When a node fails its health check (3 consecutive failures over 90 seconds), it is removed from the DNS pool. Clients that already resolved the old IP will reconnect on the next attempt — typically within a few seconds.

No action is required on your end. Failover is fully automatic.

Secret format

Secrets are 32-byte hex strings prefixed to indicate the relay protocol. All beta accounts use the ee prefix (FakeTLS mode), which wraps traffic to appear as standard HTTPS.

# Secret anatomy
eexxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
^^ prefix = FakeTLS mode

FAQ