obsideo

encrypted s3-compatible storage

Encrypted cloud storage. Continuously verified.

Your files are encrypted before they leave your machine and stored on three independent providers. Every few hours the network re-proves that each one is still there, and you can check.

Start free · 12 GB, no card How it works

works with rclone restic kopia boto3 any S3 client

01 · how it works

Three things happen to every file. You can check all three.

01

Encrypted before it leaves

The SDK encrypts on your machine with keys only you hold. On the S3 path you bring your own encryption and we store exactly what you send. Either way, nothing here can read it.

02

Stored on three providers

One S3 endpoint in front, datacenter hardware for speed, independent provider nodes for survivability. Every object lands on three of them; the network handles placement.

03

Proven, continuously

Each stored chunk is challenged with a merkle proof on a rolling cycle of roughly four hours. Providers are paid only for proofs they pass, and a missed proof triggers re-replication.

Each upload is encrypted client-side and replicated to 3 of N distinct providers. Different files land on different provider sets, reducing correlated failure risk.

Priced on logical size: store 1 TB across three replicas, pay for 1 TB. How the encryption, placement and proofs work: /security/.

02 · pricing

$5 per month per 200 GB block · 12 GB free · egress included.

No card for the free tier, no expiry on it, and nothing changes on your bill without your say-so. Enterprise volume: $15 per TB-month ($0.50 per TB-day), invoiced; write to regan@obsideo.io.

03 · who it is for

Pick your door. Same bytes, same proofs behind each one.

Developers

An S3 endpoint for rclone, restic, kopia, boto3 or the AWS CLI, plus a TypeScript SDK and a CLI when you want encryption handled for you.

→ Docs

Software agents

Signup, upload and verification as a runnable contract. An MCP server for tool use, and a no-email trial for agents without a mailbox.

→ agents.md

Chain infrastructure

Verified offsite backups for indexer databases, node snapshots and validator state. One cron line, USDC settlement.

→ Chain-infra backups

Run a provider

Earn by storing encrypted chunks you can prove you are holding. Open-source node, four commands to join.

→ Providers

04 · trust

Who holds what.

You hold the keys. Three providers hold the ciphertext. The coordinator holds names, sizes and proof records, and is never on the byte path. Obsideo is a young network without an availability SLA yet, which makes it a strong additional copy of your data today.

What the network protects against

  • A provider claiming to hold data it does not.
  • A provider quietly dropping data.
  • Anyone at Obsideo reading your data.
  • A single machine or facility failing.

What it does not do

  • Stopping a provider from deleting from its own hardware.
  • Verify proofs without the coordinator. In development.
  • Recover a lost key or password.
  • Encrypt for you on the S3 path. You encrypt first.

The mechanisms, the full table and the recovery paths: /security/. The live fleet: /network/.

get started

Start free: 12 GB, no card.

Enter an email address, confirm the code, and the page hands you working S3 credentials. A software agent can do the same from agents.md without a human in the loop.

Start free What happens after