Object storage that outlives the hardware.LIVE
S3-compatible buckets on storage that is spread across many machines in more than one rack of the zone you pick — a failed disk, node or rack is repaired by the system itself. A file manager in the console that uploads and downloads straight to the storage, versioning, lifecycle rules, object lock, public or private buckets, static websites, access keys with ready-made tool configurations, an API, and plans that are fixed or pay as you go. NVMe volumes for servers and backup space come from the same fabric.
What happens when a disk dies.
- 01
Your application writes once
Through the S3 API, the console or a volume attached to your server. The write is acknowledged only when it exists on several nodes.
- 02
Copies land in two racks
Every object is held on multiple storage nodes spread across racks with independent power and switching. No single rack holds all copies.
- 03
A node fails
Its copies are gone. Nothing you do changes: reads and writes continue from the remaining copies.
- 04
The system rebuilds
The missing copies are recreated on healthy nodes automatically, from the surviving replicas, without a ticket or a maintenance window.
- 05
Your data stays in the zone
Objects live in the zone you created the bucket in. Account and billing data lives in India with encrypted backups in Singapore.
One fabric underneath, three ways to use it.
S3-compatible buckets
Standard S3 API for applications, backups, static sites and media; the console file manager for everything else. Versioning, lifecycle, object lock, policies, CORS, static websites.
LIVENVMe volumes
Attachable volumes for cloud and dedicated servers, grown live, snapshotted independently of the server.
COMING SOONBackup space
Off-host capacity for scheduled full-server backups, priced per GB in 10 GB steps, on any plan or custom build.
LIVEFixed or pay as you go. Served from the zone you pick.
A fixed plan includes a set amount of storage for a monthly fee; pay as you go charges the average stored over the month per TB, invoiced on the 1st. Bandwidth as the plan says — included, an allowance per month, or per GB. Prices exclude tax.
| Plan | Storage | Buckets | Bandwidth | Features | Price |
|---|---|---|---|---|---|
| 100GB | 100 GB | 100 | egress included | versioning · object lock | $1.00 / mo $0.88 / mo annual |
| 1 TB – Orbit | 1 TB | 100 | egress included | versioning · object lock | $5.20 / mo $4.58 / mo annual |
| 3 TB – Nova | 3 TB | 100 | egress included | versioning · object lock | $15.60 / mo $13.73 / mo annual |
| 6 TB – Vertex | 6 TB | 100 | egress included | versioning · object lock | $31.20 / mo $27.46 / mo annual |
| 10 TB – Horizon | 10 TB | 100 | egress included | versioning · object lock | $52.00 / mo $45.76 / mo annual |
| 25 TB – Apex | 25 TB | 100 | egress included | versioning · object lock | $130.03 / mo $114.43 / mo annual |
| Elastic Bucket PAY AS YOU GO | no cap | 100 | egress included | versioning · object lock | $8.50 / TB-month + $25.00 / mo |
Pay as you go is settled on the 1st for the average stored over the month. Prices exclude tax; 18% GST is added for customers in India.
Every file, without a client.
Straight to the storage
Drag files or whole folders into the browser: single uploads up to 64 MB, bigger files in 16 MiB parts, three at a time, with a progress queue — presigned links, so the bytes never pass through the platform.
Folders, search, preview
Folder view with breadcrumbs, a filter box, search across the whole bucket, previews of images, video, audio, PDF and text, a properties drawer with size, type, ETag, storage class and metadata.
Links that expire
Download links and share links good for up to seven days, with or without an attachment header — hand a file to anyone without a key.
Copy, move, rename, delete
Across folders and across buckets, one object or a selection; calculate the size of a folder; new folders; bulk ACL changes.
Every change kept
With versioning on, overwrites and deletes keep the previous version: list, restore or delete any version from the console.
Tags, metadata, ACL, retention
Edit object tags, content type and cache headers, per-object ACL grants and legal holds or retention dates (governance / compliance) in the drawer.
Everything the storage lets you set on a bucket.
| Setting | What it does | Typical use |
|---|---|---|
| Versioning | Keeps every overwrite and delete as a version; old versions count towards storage | Backups, documents, anything you may need to roll back |
| Lifecycle rules | Expire objects after N days, retire old versions, abort unfinished uploads — per prefix, with presets | Logs and temporary data, keeping versions 30 days |
| Access | Private, public read, anonymous reads from listed IP addresses, or your own bucket policy | Public downloads, a private origin for the CDN |
| ACL | Grants to other storage users, by e-mail, to everyone or to authenticated users — the owner always keeps full control | Sharing a bucket between accounts |
| CORS | Browser origins allowed to read or upload directly; the console's own origin is always kept | Uploads from your web app |
| Static website | Serve index and error documents from a bucket | Documentation, downloads, a landing page |
| Object lock | Default retention in governance or compliance mode on buckets created with lock; legal holds per object | Audit trails, regulated archives |
| Encryption | Default server-side encryption (AES-256) for new objects | Compliance |
| Tags | Up to 50 key / value pairs on the bucket | Cost allocation, environment labels |
| Unfinished uploads | See and abort multipart uploads that never completed | Reclaiming space after a broken client |
| Metrics | Stored bytes and objects day by day, traffic served | Capacity planning |
Any S3 tool. Or the API.
Up to five access keys
Create a pair (the secret shown once), verify it with a signed call from the console, delete all but the last. Path-style addressing and Signature V4 — the settings every tool wants.
Written for you
The console writes the configuration for the AWS CLI, rclone, s3cmd, MinIO client, boto3, PHP and Node SDKs with your key filled in, and a Cyberduck / Mountain Duck profile to download.
Buckets, keys, settings, files
A console API token with the storage scope creates buckets, hands out presigned upload and download links, changes settings and runs every file operation of the console — the bytes never pass through the platform.
Priced like the rest of the platform. Renewed by itself.
A set amount for a monthly fee
Pick 1 TB, 3 TB, 10 TB … paid monthly, quarterly or yearly with the usual cycle discounts. The renewal invoice is raised 7 days ahead and, with auto-renew on, paid from your wallet on the due date.
Per TB-month
The average stored over the month, invoiced on the 1st and paid from the wallet when it covers it. No minimum, no commitment.
Included, an allowance, or per GB
A plan says what its egress is: included; an allowance per month (over it charged per GB or paused until the 1st, with notices at 80 % and 100 %); or per GB from the first byte.
Alerts before the limit
At 80, 90 and 100 % of the plan's storage you get a notice and an e-mail; at the limit uploads are refused until you free space or move to a bigger plan — nothing is deleted.
Day by day
Stored bytes, objects and traffic per bucket and per day in the console; the month's invoice lines match them.
Change the plan any time
Order a bigger plan from the console: the quota follows the moment the order is paid; nothing moves.
Backups that survive the host
Point restic, rclone or your backup tool at a bucket; keep versions 30 days with one lifecycle rule.
Images, video, downloads
Object storage as the origin for the CDN: upload once, serve from every edge, purge in seconds.
Datasets and logs
Cheap, durable buckets for the things you keep but rarely read; expire them by prefix.
Static websites
Publish a bucket as a website behind the CDN and ship multi-gigabyte release files without touching a server.
How do I use object storage?
Order a plan under Console → Object storage, create a bucket, and use the access keys with any S3-compatible tool (AWS CLI, rclone, s3cmd, the SDKs) — the console writes the configuration for you — or upload and download straight from the console's file manager. Buckets, keys and settings are also available through the customer API.
Where is my data stored?
In the zone you create the bucket in — Noida. Objects are spread over several storage nodes in more than one rack of that zone and never leave it; account and billing data lives in India with encrypted backups in Singapore.
What does bandwidth cost?
What the plan says: included, an allowance per month (10 TB, say — over it either a per-GB price on the usage invoice or a pause until the 1st), or per GB from the first byte. The console shows how much of an allowance is used and warns at 80 %.
What happens when a renewal is due?
Fixed plans get a renewal invoice 7 days before the date; with auto-renew on it is paid from your wallet on the due date (you are told if the wallet is short). Unpaid, the account is suspended after the grace period — every key refused, nothing deleted — and resumes the moment the invoice is paid. Pay as you go is invoiced on the 1st for the month's usage.
Can I make a bucket public or serve a website from it?
Yes — Settings → Access makes a bucket readable by anyone (or only from listed IP addresses, or by your own policy), and Settings → Website serves index and error documents from it. Put the Joy CDN in front of it for edge delivery.
What can I use for servers today?
Backup space: off-host capacity for scheduled full-server backups, added in 10 GB steps to any plan or custom build — the per-GB price is on the pricing page. Snapshots are free on every plan. NVMe volumes are in build.
Are snapshots backups?
No. A snapshot protects you from your own mistakes, not from hardware failure. Use backup space, or a bucket with versioning, for real protection.