Start with the per month storage rate
Object storage bills two things separately: the space you keep and the traffic you move out. The first number to write down is the monthly rate per gigabyte, because that cost grows quietly with every upload. Across the providers DeployCue tracks, per month per gigabyte pricing runs €0 to €20, so a cheap-looking headline can still turn expensive once a bucket fills up.
SberCloud lists a per month rate of RUB 814.68 for stored data. Aruba sells storage through its object storage product, with egress published separately at €0.05. Those two figures answer different questions, which is the first trap in this category. Storage price is what you pay to keep bytes. Egress price is what you pay to send them out. A provider can sit at the cheap end of one and the dear end of the other.
The Object storage ranking puts the full list side by side so you can see where a candidate lands on both numbers before reading a single product page. Compare on the pair, never on one alone.
Treat egress as its own decision
Egress is where most surprises live. Once you calculate a rate, look at how much outgoing traffic the plan includes before you calculate anything else. Both brands here include a generous allowance, and the gap between them is large enough to change the architecture.
Aruba includes 40 TB per month with the entry package at no extra charge, and lists a per gigabyte rate of €0.05 beyond that. SberCloud includes 10 TB of outgoing traffic per month and prices additional traffic at RUB 1.15 per gigabyte. Neither figure is small for a small team, but a team shipping media, backups or analytics extracts will clear it faster than most.
For context, per gigabyte egress across the tracked market runs €0 to €0.29. Put your own monthly transfer volume against the included allowance first, then against the per gigabyte rate. If your traffic stays inside the allowance, the per gigabyte number is largely irrelevant. If it does not, the allowance size matters more than the storage rate. The SberCloud review and the Aruba review break down how each of these plans is billed and what the free tier covers.
Check whether the API is the one you already use
Migrating object storage means rewriting every call that touches a bucket. Before comparing prices at all, confirm the provider speaks the interface your code and your tools already assume. This is a compatibility question, not a preference question.
SberCloud offers an S3-compatible endpoint, and its storage types cover object storage. Aruba runs its own object storage product rather than describing itself through an S3 label, so tools built around S3 semantics deserve a closer look before a commitment. Integrations such as lifecycle rules, multipart uploads and third party backup agents are where a non S3 implementation tends to reveal gaps.
Also read the request and function pricing lines as a bundle. SberCloud publishes a request rate of RUB 14.34, a per gigabyte second rate of RUB 0.0013, and a free request allowance of 1,000,000. Heavy API traffic against small objects can outrun the storage charge itself. Details like these show up in the HostKey review and the Alibaba Cloud review as well, since request pricing recurs across the category.
Read the free tier as a real allowance, not a headline
Free credits and free traffic are useful for evaluation, and useless as a cost model. Read the allowance, then read the expiry, then decide whether the workload you care about fits inside it.
SberCloud runs a free tier and hands out bonus credit, larger for legal entities and sole proprietors than for individuals. A free control plane is listed as no, and there is a separate control plane charge of RUB 2.98 for managed Kubernetes. Aruba bundles its included traffic with the entry package, which is the 40 TB per month with the entry package figure above, so there is no separate credit to track. SberCloud also reports DDoS protection as included.
A trial period tells you about speed of setup and API shape. It tells you nothing about how the invoice behaves under a real traffic curve. Estimate that curve first, then use the free tier to confirm the migration works.
Price the surrounding services you will need
Object storage is rarely a standalone purchase. Backups, compute that feeds a pipeline, a container platform and support all land on the same invoice, and their billing units are easy to misread.
SberCloud bills compute hourly and also offers per-minute billing for its GPU capacity, with a GPU rate starting at RUB 240 and supported GPU models including B300, H100 and A100. Its interconnect options are listed as Infiniband for the machine learning service depending on configuration, NVLink and Direct Connect. That matters if stored data feeds a training pipeline and the traffic between compute and storage has to stay inside the provider.
Aruba publishes monthly billing and an entry plan of 1 vCPU, 1 GB RAM, 20 GB storage at €1.99, plus 2 TB/month of included bandwidth on its virtual server plan. Read the billing unit next to the amount every time, since a per hour figure and a per month figure are not comparable at a glance. Providers such as Vultr and UCloud publish the same kind of unit data, so lining the units up across reviews makes the comparison tractable.
Weigh compliance and footprint before you sign
Regulatory requirements narrow the field faster than price does. If your data carries a certification obligation or a residency rule, the shortlist usually becomes very short very quickly.
SberCloud holds ISO/IEC 27001:2022, ISO/IEC 27701:2019 and ISO/IEC 27017:2015. Aruba holds ISO 27001, ISO 9001 and ISO 14001. Different lists mean different audit conversations, and the right question is which standard your own compliance regime names.
Footprint and reliability come next. SberCloud is headquartered in RU with availability in RU and 9 locations, and it publishes an uptime commitment of 99.9%. Aruba is headquartered in IT and was founded in 1994. Check whether a published uptime commitment exists for the region you actually deploy into, and see how the larger providers in the Google Cloud review handle the same question for comparison.
A working order of comparison
Put the work in a fixed order so the decision is repeatable. Confirm the API compatibility you need, set the monthly stored volume and apply the per month per gigabyte rate, set the monthly outgoing volume and check it against the included allowance and then the per gigabyte rate, add the adjacent services you will really use while matching billing units, apply the compliance and residency filter, and read the provider review for the operational details the pricing pages leave out.
Keep every figure as a rate with its unit attached, and rerun the estimate at your projected growth rather than your current one. Storage costs are forgiving early and unforgiving late, because objects accumulate and nobody notices until the bill arrives.