S3-compatible storage that stays home.

The object store your apps already speak — versioned, replicated and sovereign, with none of the request-pricing arithmetic.

Full S3 APIMulti-AZ durabilityNo request pricing

Talk to us All Storage

Capabilities

Objects, the way your tools expect

Built for compatibility, durability and seamless data management.

S3 compatibility

Existing SDKs, CLIs and backup tools work unchanged.

Works with what you use →

Versioning & replication

Object versioning with cross-AZ replication for durability.

Built to outlast anything →

Policy-based access

Bucket policies, scoped keys and presigned URLs.

Scoped, signed, controlled →

Lifecycle to archive

Objects tier automatically into Archive Storage as they cool.

Cools itself down →

Object lock

WORM-style retention on any bucket — versions that ransomware and mistakes cannot rewrite.

Ransomware-proof versions →

Encrypted by default

Server-side encryption on every object, with keys held in-country and BYOK via the platform HSM.

Keys held in-country →

Event notifications

Bucket events trigger functions, queues and pipelines the moment objects land.

Pipelines trigger themselves →

CDN delivery

Front any bucket with the regional edge for public assets — one switch, no separate origin.

One switch to the edge →

Multipart & large objects

Parallel multipart uploads and range reads keep multi-GB transfers fast and resumable.

Multi-GB without babysitting →

Usage visibility

Per-bucket capacity and access reporting into Obersva — growth is never a surprise.

Growth is never a surprise →

Resilient by designBuilt to continue, even when hardware fails.

Predictable performanceConsistent I/O for the apps that matter.

Efficient at scaleOne flat fee. Scale without waste.

Backed by humansReal experts. Real support. Every time.

Compare the tiers

Standard, replicated, or delivered

One S3 endpoint, three durability and delivery profiles — pick per bucket, change when the workload changes.

ProductionEdgeComing soon

TIER 01Start here

Standard Objects

The everyday bucket

Versioned, in-zone object storage with the full S3 API — the default home for application assets, uploads and backup targets.

Best for

App assets & uploadsBackup targetsStatic content

Where it runs

Dubai AZ1Dubai AZ2RiyadhBahrainMumbaiSingaporeAbu DhabiMilanFrankfurtNairobi

Plans

BucketVersioning · scoped keys · lifecycle rulesSign in →Bucket PlusAdds object lock and event notificationsSign in →CustomAny capacity, policy and key structureSign in →

TIER 02

Replicated Objects

Durability across zones

Cross-zone replication for data that must survive a zone, with the same endpoint and tooling your apps already use.

Best for

Regulated datasetsCross-zone recoveryData lakes

Where it runs

Dubai AZ1Dubai AZ2RiyadhBahrainMumbaiAbu DhabiFrankfurtNairobi

Plans

ReplicatedAsynchronous cross-AZ replicationSign in →Replicated PlusReplication + object lock + audit trailSign in →CustomAny replication topology and RPOSign in →

TIER 03

Published Objects

Objects on the edge

Buckets fronted by CDN with signed URLs and instant invalidation — for content your users pull, not just your applications.

Best for

Media & downloadsPublic assetsSoftware distribution

Where it runs

Dubai AZ1RiyadhMumbaiSingaporeAbu DhabiMilanFrankfurtLagosNairobi

Plans

PublishedCDN-fronted · signed URLs · purge APISign in →Published PlusCustom domains · cache rules · WAF readySign in →CustomAny delivery, cache and origin policySign in →

Two ways to buy

Capacity you size, or capacity that grows

Both are flat-fee and free of per-request pricing. The difference is how growth is handled.

Sized CapacityFixed poolAn agreed capacity pool shared across every bucket, re-baselined when you approve it.

One figure for all buckets

No request or egress meters

Alerting before the pool fills

Best for:Steady, known datasets

Explore Sized Capacity plans

Growth CapacityElastic poolCapacity that steps up at thresholds you set, for platforms whose data volume only goes one way.

Steps agreed in advance, not discovered

Lifecycle rules push cold data to Archive

Reporting on growth per bucket

Best for:User-generated content and lakes

Explore Growth Capacity plans

Who decides, who runs it

What each group gets from Object Storage

Four groups shape a cloud decision. Pick the one you belong to — the platform reads differently from each seat.

“S3 economics without S3 surprises”

The object layer your teams already build against, priced on capacity and placed under your own jurisdiction.

GovernedSovereignPredictable

FAQs

Is it really S3-compatible?

Yes — standard S3 API, so SDKs, CLIs, backup tools and static-site pipelines work without modification.

Are requests or egress charged?

No. Capacity is the only line; there is no per-request or per-gigabyte meter to reconcile.

How durable is a bucket?

Erasure-coded in-zone by default, with cross-zone replication available per bucket on the Replicated tier.

Can objects tier to Archive automatically?

Yes. Lifecycle rules move cooling objects into Archive Storage on a schedule you define.

Can we serve content publicly from a bucket?

Yes — the Published tier fronts buckets with CDN, signed URLs and instant invalidation.

How is the flat fee different from public cloud pricing?

Everything inside the plan you opt for is included — no additional charge for the components that make it up. Public clouds meter each component on consumption, so the bill moves with usage. Here the plan is reserved for you and the figure you agreed is the figure you pay.

Can we drive it from Terraform and CI?

Yes. Every operation is exposed through the REST API, CLI and a maintained Terraform provider, with scoped API keys per team. If the console can do it, your pipeline can do it.

How do limits and quotas work?

Quotas are yours to shape — carve capacity per team or project and delegate inside it. Hard ceilings are a conversation, not a wall; the estate re-baselines at thresholds you approve.

Can security services be included in my plan?

Yes. Endpoint security, firewalls and WAF are scoped into the same flat fee when you add them — one figure, no separate security invoice.

Better together