Both storage options cost the same — 20 UZS per GB per day — and live in the same data center in Tashkent. The difference is who works with them: people or software.
File storage is for people
MCDrive means folders, per-department permissions, desktop and mobile apps, share links for clients and version history. The accountant opens “Contracts”, the designer syncs “Projects 2026”, the manager checks everything from a phone. It works like a shared office drive, only it lives in a data center.
S3 object storage is for software
S3 is about buckets and access keys, not folders and users. Applications talk to it over the Amazon S3 protocol: Veeam writes backups there, a website stores product photos and serves them via direct links, developers upload logs and build artifacts. No “human” interface is needed — code does all the work.
Three typical tasks
| Task | What to choose | Why |
|---|---|---|
| Server backups (Veeam, rclone, pg_dump) | S3 | Backup tools can write to S3 directly, and versioning protects copies from deletion |
| Department documents, collaboration, links for clients | MCDrive | Folder permissions, apps, version history, offboarding in a single action |
| Website or app media: photos, user documents | S3 | Direct links with no load on the web server, standard SDKs for any language |
Can you combine them?
Yes, and it’s a common setup: staff work in MCDrive, and every night a copy of MCDrive and the servers goes to S3 via Veeam. Two different storage systems mean two independent points of failure.
What about price?
In both cases it’s 20 UZS per GB per day for the space you actually use, with no charges for traffic or requests. A terabyte comes to about 600 000 UZS per month. With foreign S3 providers, egress fees often exceed the cost of storage itself; here, traffic over TASIX/UZIX is free.
Need help with the task from this article?
We’ll pick a configuration, calculate the cost and help with the move.