Media Operating System
MOS. Your media, kept safe and ready to play.
Keep files on your own machine. MOS backs them up across nodes around the world, yours or the network's. Lose a drive, lose a site, your content is still whole.
- S3-compatible
- Only you hold the keys
- Encrypted on your device
- Survives node failures
Studio node · Brisbane
Mac mini · Apple Silicon · v1.4.2
Copy health
3/3Every file here is kept whole on 3 nodes. Lose one and nothing is lost.
Uptime
99.97%Last 30 days
Earned
148.20 USDCThis month
01 / Developers
Build on an S3 API you already know.
Upload, encode and run AI in one call each. See the SDK ↓
02 / Studios and publishers
Upload once. Stream everywhere.
Seasons, rights and payouts in one place. See MOS Stream ↓
03 / Node operators
Earn USDC on hardware you own.
Store, serve and encode for the network. See Run a node ↓
How it works
Local first. Everywhere after.
No single data centre to go down.
Keep it local.
Your files stay on your machine, fast and in your hands.
Spread it out.
Each file is encrypted and kept as 3 whole copies on different nodes. Any one copy serves it.
Choose where it lives.
Your own nodes, the MOS network, or both.
Stays whole on its own.
Nodes are checked every few seconds. A missing piece is rebuilt somewhere else.
MOS Store · Media Object Store
Storage that works like S3, without the landlord.
Private by default
Encrypted before it leaves your device.
Your keys never leave your hands. Nobody else can read your files, including us.
Nothing to see
Operators see anonymous pieces.
Never names, never folders. A node holds a slice of a file it can't open.
Direct ingest
Drop files straight in from your node.
No browser upload. A 50 GB master goes in like any other file.
Nearest first
Fetched in parallel from the nearest nodes.
Pieces arrive at once from several holders, then join up on your side.
S3 API
Works with the tools you already use.
Point the AWS CLI, rclone or your SDK at gateway.mosnet.io.
MOS Stream
From master file to every screen.
- 01
Play it from where it's stored.
HLS straight from nodes, no CDN middleman.
- 02
Full 240p to 1080p ladder.
Hardware encoded on nodes in the network.
- 03
Rights checked on every play.
By territory and date window, before the first segment loads.
For studios
Open Studio →Upload once, the network does post.
Seasons, episodes, artwork and captions in one place. Drop in a master and MOS encodes the ladder and stores every rendition.
For publishers
See the feed →One feed, any player.
Titles land in your feed the moment rights are granted. No files to move, no delivery to chase.
Of your content revenue
Get paid
MOS never takes a cut of your content revenue.
50 / 50 ad split
Creator and publisher, settled in USDC.
Pay for delivery used
Publishers pay for the streaming they serve.
Pay-per-view
On the roadmap.
Also on MOS
Transcripts, captions, IAB v3 and GARM, chapters and clip picks. Run inside the network on your encrypted media.
Learn about Vision →Rights, provenance and licensing on the RITE Registry. Claim a title, prove who owns it, license it on the record.
Visit riteregistry.xyz →The MOS chain
A layer one built for media.
It tracks where every piece lives and pays the nodes that keep it. Fees are pegged to the US dollar, so prices don't swing with a token.
Validators and consensus in the docs →Run a node
Earn USDC on hardware you own.
Get paid for storing, serving, encoding and AI jobs. Your node runs in the background and the network sends it work.
| HARDWARE | STORE · SERVE | VISION |
|---|---|---|
| macOSApple Silicon and Intel | ||
| Linux x86_64Desktops, servers, NAS boxes | ||
| Linux ARMIncluding Raspberry Pi |
Developers
Three calls to a streaming library.
- Upload, encode and AI are one call each.
- No cloud keys in the browser. Files are encrypted on device.
- S3-compatible reads for your existing tools.
// Encrypt and upload. Files are encrypted on
// your device before any bytes reach a node.
const { file_id, cdn_url } = await
MOS.store.upload(file, registration);
// One call: HLS encode, transcription,
// and a Vision sidecar (GARM, IAB, chapters).
await mos.stream.encode(file_id, {
transcription: 'balanced',
vision: 'standard',
});
// Webhooks tell you when each stage is done.
// POST https://you.example.com/mos-hook
// event: encoding.complete | vision.completeCompare
How MOS stacks up.
| MOS | AWS S3 | Dropbox | Backblaze B2 | Filecoin | Sia | |
|---|---|---|---|---|---|---|
| Pricing | Pay for use, paid out to the nodes | Premium retail | Consumer flat rate | Wholesale flat rate | Moves with a token | Moves with a token |
| Performance | Nearest nodes, in parallel | High, costly | Consumer | Budget tier | Archival only | P2P, no CDN |
| Ownership | Your keys | Vendor lock-in | None | None | Miner-controlled | Renter keys |
| S3 API | Yes | Yes, locked in | Yes, centralised | Partial | ||
| Streaming | HLS from nodes | Via CloudFront | ||||
| AI on your media | In the network | Separate bill | ||||
| Studio, rights, distribution | Built in | |||||
| Operator sees file names | Never. Anonymous IDs only | Yes | Yes | Yes | Partly | Partly |
| Nodes paid in | USDC | FIL token | Siacoin |
FAQ
Questions, answered.
Still stuck? Ask us on Telegram.
What happened to ZiB?
ZiB is now MOS. Same network, same nodes, new name.
How does MOS keep my data secure?
Files are encrypted on your device before they leave it, so nothing readable ever reaches the network. Each file is kept as 3 whole copies on different nodes, and operators only ever see anonymous IDs, never your file names, folders or content. If a node fails, the other copies keep serving.
How do I start earning as a node operator?
Install the MOS node app, choose how much spare storage to give, and turn your node on. You earn USDC for the storage you provide, the video you encode and the AI jobs you run. More storage and better uptime earn more.
What happens if a node goes offline?
Your files stay available, because every file is kept whole on 3 nodes. The network checks nodes every few seconds, and when a copy goes missing it places a new one on another node.
How is storage priced?
You pay for what you store and serve, priced in US dollars, and that money is paid out to the nodes that keep your files. Fees on the MOS chain are pegged to the US dollar, so prices do not swing with a token.
Can I use MOS for business storage?
Yes. The MOS SDK handles encrypted uploads, video encoding and AI with one call each, and the S3-compatible API fits server-side tools you already run. On top you get redundancy across nodes, built-in streaming, AI in the network, and Studio, rights and distribution, with no lock-in.
What hardware do I need?
A stable internet connection and spare storage. Storage, encoding and serving run on macOS (Apple Silicon and Intel) and Linux (x86_64 and ARM, including Raspberry Pi). Transcription runs on all of these. Vision AI needs a Mac or an x86_64 Linux machine with enough RAM, and a modern GPU speeds it up.
Does MOS support video streaming?
Yes. MOS encodes adaptive HLS across a full 240p to 1080p ladder, using hardware encoding where it is available (VideoToolbox, NVENC, AMF, QSV) and software otherwise. Encrypted segments are served straight from nodes, so the backend stays out of the playback path.
What is MOS Vision and how does it work?
MOS Vision runs AI on video stored in the network without ever writing the decrypted video to disk. Nodes transcribe the audio and analyse it for chapters, clip picks, captions, thumbnail moments and GARM and IAB brand safety. The results come back encrypted and are stored in MOS.
Is MOS compatible with the AWS S3 SDK?
For reads and object management, yes. MOS has an S3-compatible API (SigV4 or token auth), so you can list, fetch and manage objects with your existing S3 tools. Uploads go through the MOS SDK, which encrypts each file on your device first, so no cloud credentials are ever exposed.
What is Studio, and who owns the content?
Studio is where creators and studios organise series, seasons and titles. Upload once and the network encrypts, encodes to HLS and runs Vision. You keep ownership: your content is encrypted on your device, and your rights are yours to grant, change or revoke. MOS is infrastructure, not a rights holder.
How do rights and publisher distribution work?
You grant distribution rights per title, with territory, window and exclusivity. Publishers only see what they are licensed for, and pull encrypted, ready-to-stream titles into their own apps through a keyed API, with no re-encoding or re-hosting. Rights are checked on every stream, and access ends when a window closes.
How do payments work?
Payments are in USDC. Video ad revenue is split 50/50 between creator and publisher and settled to a payouts ledger you claim from. Publishers fund a prepaid balance and are billed per GB of delivery. MOS takes no cut of content revenue and only bills for infrastructure: storage, encoding, AI and delivery. Pay-per-view is on the roadmap.