Integration · Storj
Back up email to Storj — automatically.
Forward any email to your private InboxBucket address and the original .eml is written to your Storj bucket — where it's encrypted, split into pieces, and spread across thousands of independent nodes. No one data center holds your mail.
Free plan available · No credit card required
- From:
- Acme Billing <[email protected]>
- To:
- [email protected]
- Subject:
- Invoice #4471 — June services
- Files:
- invoice-4471.pdf
s3://your-bucket/inboxbucket/2026/07/0714__invoice-4471__acme-billing.eml
✓ stored · 84 KB · original MIME
Why back up to Storj
A backup with no single point of failure.
Built to lose machines
Every object is erasure-coded into dozens of encrypted pieces on separate nodes, and only a fraction of them are needed to rebuild it. Most of the pieces could vanish at once and your archive would still come back intact.
Outside the big clouds
The nodes are run by independent operators across more than a hundred countries — not racked in one company's region. If you'd rather your mail archive didn't live inside a hyperscaler, this is the storage for it.
Ordinary S3 on the surface
You get a normal bucket behind Storj's hosted S3-compatible gateway. InboxBucket writes to it like any S3 endpoint; the encryption, splitting, and worldwide distribution all happen behind that one address.
How it works
Point it at your bucket, then forward.
Add your Storj bucket
Pick Storj in InboxBucket and paste in your S3 credentials and bucket name — the gateway endpoint is already filled in (details on the right).
Get your address
We generate a private inbound address for you — it can only receive:
[email protected]Forward anything
Send one message by hand or point an auto-forward rule at it; moments later the original .eml is distributed across the Storj network.
What you'll need to connect
- Endpoint
- https://gateway.storjshare.io
- Region
- us1 (or eu1 / ap1)
- Access key + secret
- S3 credentials generated in the Storj console under Access Keys
- Bucket
- your backup bucket name
The endpoint is Storj's hosted S3 gateway — the same for everyone. It speaks the same API as Amazon S3, so InboxBucket uses the same connector; only the credentials and bucket are yours to fill in.
The access we ask for
Credentials you scope, on a network no one owns.
In the Storj console, under Access Keys, you generate S3 credentials and decide their reach as you create them — limit them to your backup bucket and grant only the permissions you're comfortable with. InboxBucket gets exactly that key and nothing wider, and stores it encrypted at rest with AES-256-GCM.
We're the pipe, not the vault. Your mail touches our servers only long enough to be written out to Storj; the dashboard runs on metadata alone — sender, subject, date, status — and we never keep message bodies. Revoke the key in the Storj console whenever you like, and every .eml already distributed across the network stays yours.
- Scoped to one bucket, with permissions you choose at creation
- Keys you generate in the Storj console — and can revoke there too
- Nodes hold encrypted pieces only — never a readable message
The details
Built like a backup should be.
No single point of failure
Storj erasure-codes every object into dozens of pieces on independent nodes; only a fraction are needed to rebuild it. A dead disk, a dark data center — your archive doesn't notice.
Nodes can't read your mail
Objects are encrypted before they're split, so any one node operator holds a shard of ciphertext — never a message, never an attachment, never even a filename.
The .eml is the original
What lands in your bucket is the raw RFC 822 message — headers, body, and attachments in one file that any mail client or text editor opens. Nothing lossy in between.
Attachments of any real-world size
InboxBucket streams big files with S3 multipart through Storj's gateway, so a heavy signed contract arrives in one piece instead of hitting a request cap.
Exactly one copy per message
Mail servers retry and people forward twice. We dedupe on Message-ID before writing, so a message never turns into duplicate objects on the network.
Nothing fails quietly
If a write to Storj doesn't land, it queues and retries, and your dashboard shows the status until it does — including a plain warning when credentials need replacing.
FAQ
Storj backup, answered.
What endpoint and region do I use for Storj?
Use https://gateway.storjshare.io — Storj's hosted S3-compatible gateway, the same address for everyone, which routes you to the nearest gateway instance. Set the region to us1, eu1, or ap1 to match where you created your Storj project; the Storj console shows which one your account uses. InboxBucket pre-fills the endpoint when you pick Storj.
What credentials does InboxBucket need for Storj?
S3 credentials — an access key and secret key — generated in the Storj console under Access Keys. When you create them, choose the S3 credentials type and scope them to just your backup bucket with only the permissions you want to grant. InboxBucket stores what you paste in encrypted at rest with AES-256-GCM, and you can revoke the key in the Storj console at any time.
How do Storj's encryption and decentralization actually work?
Every object is encrypted, then erasure-coded into many pieces spread across independent nodes run by different operators around the world — only a fraction of the pieces are needed to reconstruct it, and no node ever holds a readable file. One honest caveat: through the hosted S3 gateway, Storj manages that encryption server-side, so the gateway handles your data in flight (protected by TLS). It is not end-to-end encryption in the strict sense — that requires running Storj's own client tools. What the distributed network gives you is that no single machine, data center, or operator holds your mail.
Is backing up email to Storj the same as Amazon S3?
On the wire, yes — Storj's hosted gateway speaks the S3 API, so InboxBucket writes to it with the same connector it uses for AWS. The difference is what happens after the write: instead of landing in one provider's data center, the object is encrypted, split, and distributed across the Storj network. If you're comparing destinations, the Amazon S3 setup covers the same fields.
What format are the backups in?
Plain .eml files — each one the complete RFC 822 message exactly as it arrived, with headers, body, and attachments together. It's the most portable email format there is: readable today in any mail client and still readable decades from now, with nothing proprietary to migrate away from.
Is Storj email backup free?
InboxBucket's Free plan backs up 100 emails a month to one storage connection, so Storj works on the free tier — no credit card. Storj bills you separately for the storage itself: new accounts get a trial allowance, and ongoing per-gigabyte pricing runs well below the big clouds. An email archive of small .eml files costs very little to keep.
Free plan · No credit card
Put your email on a network, not a server.
Connect your Storj bucket, get your address, and the next email you forward is encrypted, split, and spread across thousands of independent nodes — with no single point of failure.
Add your Storj bucket