stand up your own storage · ~10 minutes · no surprises

You are not signing up for storage.
You are standing up your own

The Relayer you install in step three is not a client and it is not a toll. It is the endpoint itself — the piece every other cloud keeps on their side of the line and we hand to you. It holds your keys, resolves your bucket names and writes your access log, all on your host. That is the whole reason we can say we cannot see your data. Here is the entire path, start to finish, so you know what each screen will ask before you get there. Four steps, about ten minutes.

4 steps ~10 min Docker on your host $0 egress after

The whole journey, up front

Four steps — here’s what each one looks like

You’ll move through four screens. We tell you what each will show so none of them catches you off guard — the most common reason people stall is a screen they didn’t expect.

Evaluating rather than installing? Two pages answer the questions this one doesn’t: production readiness → covers what you operate, what the rate covers and how you would leave, and trust & security → covers encryption, identity, the audit surface and who operates what.

1

Create your account

A free XNS account, so your storage is bound to you and nobody else.

What you’ll see: a secure sign-up form, then a verification email — not a paywall.

2

Deploy your Relayer

One Docker command brings your private S3 gateway up on your own machine.

What you’ll see: a copy-paste command and containers starting. You author no config files.

3

Claim & verify

A quick browser sign-in ties the running Relayer to your account. We store a test file and read it back.

What you’ll see: one sign-in, then a green “storage verified” confirmation.

4

Store your data

Point the xns CLI — or aws-cli, rclone, any S3 tool — at your endpoint and upload.

What you’ll see: your endpoint URL, your keys, and your first file landing in a bucket.

What you’ll need: a machine you control with Docker Desktop installed — a spare server, a VPS, or even your laptop. It’s a free one-click install for Windows, Mac, and Linux, and it’s the only software you need. Not ready to install Docker? Drive a live Relayer in your browser.

Two ways to do it

By hand, or hand it to an agent

The destination is the same — a private S3 you own. Pick the path that fits how you like to work.

Do it yourself

The full manual guide — every command, copy-paste ready, with what each one does and what success looks like.

Let your AI do it

Add one MCP server to Claude and say “set up XNS storage.” The agent runs all four steps for you.

Before you start

The questions everyone asks first

Yes — XNS storage runs on a machine you control. That’s the point: your data lives on infrastructure you own, not in someone else’s account. A spare server, a cheap VPS, or your own laptop is enough to start, as long as it has Docker.

It’s the XNS storage gateway — the S3-compatible server you run. It speaks standard S3 to your tools and stores your data, erasure-coded and encrypted, across the distributed network. You deploy it in step 2.

Because your keys belong to your account, the first step is creating that account. After you deploy and claim your Relayer, your keys are issued to you in the console. This page exists so that hop isn’t a surprise.

Yes. XNS is S3-native — aws-cli, rclone, restic, boto3, and any S3 SDK work by changing one endpoint. The first-party xns CLI is optional and just makes it faster.

About ten minutes if Docker is already installed: a couple of minutes to register, a few to pull and start the Relayer, and the rest to claim it and run your first upload.

The manual setup guide has every command with troubleshooting notes, and the docs cover the details. You can also let an AI agent drive the whole thing from /setup-with-ai.

Ready? Step 1 is your account

The next screen is a secure XNS sign-up. Create your account, and you’re on step 2 — deploying your own private S3.


© Copyright - SCP, Corp | Xa Net Services and Affiliates