XNS speaks the S3 API, so the backup software, sync client or platform on your servers today talks to it without a plugin, a connector or a rewrite. Thirty-seven of them have a step-by-step setup guide written and published below — endpoint, region, credentials, done.
Every entry links to its own guide with the exact endpoint, region and credential steps for that tool. If a tool is not on this list and it can talk to Amazon S3, it can talk to XNS — the guides exist because someone asked, not because the others are unsupported.
No tool matches that name. It may still work — anything that speaks the S3 API does.
37 of 37 shown
Want to check your tool first? Try your tool against a sandbox.
There is no XNS SDK to install and no proprietary protocol to learn. You run the Relayer gateway on a host and domain you control, it issues your credentials, and every client below signs against it exactly the way it signs against Amazon.
| Setting | Value |
|---|---|
| Endpoint | https://relayer.example.com — your own gateway domain |
| Region | us-east-1 |
| Signature | AWS Signature Version 4 |
| Addressing | Path-style and virtual-host style both work |
The region string is a signing constant, not a data location. Where your data physically sits is set by placement policy, not by this field.
Supported operations are published one by one on the S3 compatibility matrix, alongside the same operations on AWS S3, Ceph, MinIO, Wasabi, Backblaze B2 and Storj.
Stand up the gateway, issue yourself credentials, and paste the endpoint into the client you already have open. The setup guide walks the whole path, and nothing on it needs a sales call first.
Explore the platform
Everything you need to go from evaluation to production.