Date: Sat Oct 3 19:03:00 2026 +0200 pithos.sia: product site for Pithos A home for Pithos on its own BCNR name: what it does, how s3d and Sia fit together, the three ways to run it, a getting-started path and the security model. Self-contained page with relative links, since the gateway serves it under . Live on Sia at bns/pithos.sia/, and pithos.sia is registered on chipnet with {"s3":"bns/pithos.sia/"} (tx bdc48e0d6e78ea0d325b6d727a9e149d9706bdcd734e78d8ae66da1ead339fbb). diff --git a/assets/favicon.svg b/assets/favicon.svg new file mode 100644 index 0000000..4335a25 --- /dev/null +++ b/assets/favicon.svg @@ -0,0 +1 @@ + diff --git a/assets/logo.svg b/assets/logo.svg new file mode 100644 index 0000000..4335a25 --- /dev/null +++ b/assets/logo.svg @@ -0,0 +1 @@ + diff --git a/index.html b/index.html new file mode 100644 index 0000000..590e0da --- /dev/null +++ b/index.html @@ -0,0 +1,304 @@ + + + + + +Pithos — a control panel for your Sia storage + + + + + + + + + + + + + + +

Your own S3, stored on Sia

Pithos runs s3d, the Sia Foundation's S3 gateway, without the command line. Connect it to Sia, hand out access keys, manage buckets and watch your files reach the network.

+ Get Pithos + How it works +

+ + +

+ +

Everything s3d does, on one screen

s3d is a great piece of plumbing that you drive with a CLI and config files. Pithos keeps the plumbing and gives you the controls.

🔗

Connect to Sia

Register with sia.storage or your own indexer using your recovery phrase, or generate a new one. You approve the connection in your browser; the phrase never leaves your machine.

🔑

Users & access keys

Create a user per app or person. Issue and revoke keys, and copy ready-made config for the aws CLI, rclone or environment variables.

🗂️

Buckets & files

Browse any user's buckets, drag files in, download them, delete folders, and make a bucket public-read when you want to serve files.

📤

Share links

Signed links that work without a key and expire after an hour, a day or a week.

📈

Upload pipeline

See what is still buffered locally, what is already on Sia, and anything that failed. Flush the buffer on demand.

⚙️

Daemon & settings

Install the official s3d release with its checksum verified, start and stop it, follow its logs and edit its settings, including redundancy and upload threads.

+ +

How it works

Your apps talk plain S3. s3d encrypts and erasure-codes the data and spreads it across independent Sia hosts. Pithos sits beside s3d and runs it for you.

Your appsaws, rclone, backups, any S3 SDK

→

s3dS3 API on your machine · encrypts locally

→

Sia networkindependent hosts, 3× redundancy by default

Pithos starts and watches s3d, holds the Sia connection, issues keys and shows you the pipeline.

Files are encrypted before they leave your computer. Sia hosts store pieces they cannot read, and no single host holds enough to rebuild a file.

+ +

Three ways to run it

The same Pithos everywhere: one engine, one interface, three homes.

🧭

In Theseus Navigator

Built into the Theseus browser as an extension. Open it from the dock and it runs in a tab. Nothing extra to install.

+ Ships with the next Theseus release +

🖥️

Desktop app

A standalone window for Windows, macOS and Linux. Quitting stops s3d cleanly, so your upload buffer is always flushed to disk.

+ Installers coming +

🌐

Web console

Run it next to s3d on a server and open it in any browser. Loopback-only by default; password plus a TLS proxy for remote access.

+ Source release coming +

+ +

From zero to S3 in four steps

You need a sia.storage account (or your own indexer). Pithos walks you through the rest.

Install s3dPithos downloads the official s3d release from the Sia Foundation and checks its SHA-256 before using it.
Connect to SiaEnter your recovery phrase or create a new one, then approve the connection on the indexer's page.
Create a userPithos makes the first access key with it and shows ready-to-paste client config.

Point your tools at itAnything that speaks S3 now stores on Sia. +

aws --profile backups --endpoint-url http://127.0.0.1:8000 s3 cp ./photos s3://family/ --recursive

+ +

Built to be boring about security

A storage control panel holds the keys to your data, so Pithos is strict by default.

Your recovery phrase stays local. It goes straight to the s3d process on your machine and is never stored, logged or uploaded.
Loopback only by default. The control panel listens on 127.0.0.1 and rejects requests that arrive under any other host name.
One-time sign-in. Theseus and the desktop app open the panel with a single-use secret that becomes a strict, HttpOnly session cookie.
No cross-site tricks. Every change needs a custom header that other websites cannot send.
Verified downloads. s3d binaries are checked against the Sia Foundation's published SHA-256 before they are installed.
Untrusted files stay inert. Downloads are served sandboxed, so a stored HTML file cannot run inside the panel.

+ +

Questions

Is Pithos a storage provider?

No. Pithos is a control panel. Your data goes from s3d on your machine straight to Sia hosts, paid through your indexer account. Silent Mode never sees or holds your files.

What does it cost?

Pithos is free and open source. Storage is billed by your Sia indexer, for example sia.storage.

Which s3d version do I need?

v0.2.0 or newer. Pithos offers to install the right one for you and tells you when yours is too old.

I already run s3d as a service. Can Pithos manage it?

Yes. Pithos uses the same config file a hand-run s3d uses. If s3d is already running, Pithos shows it as external, reads its stats and leaves the process alone.

Is there a size limit?

Uploads from the Pithos window are capped at 5 GiB per file for now. S3 clients such as aws and rclone use multipart uploads and go well beyond that.

Why the name?

A pithos was the great storage jar of the ancient Greek world, where a household kept what it could not afford to lose.

+ + + + +