object storage

Blober Path Templates: Organize Files During Transfer

Jul 20, 2026

What Path Templating Means in Blober

A file transfer normally answers two questions: what should move, and where should it go. Blober adds a third: what destination path should each file receive?

That matters because copying a disorganized source without thinking about paths creates a disorganized backup. A bucket containing clip001.mp4, invoice.pdf, DSC_4821.ARW, and years of nested project folders can be copied exactly as it is, filtered to a useful subset, or rearranged into a new structure while it moves.

Blober path templates are destination rules. They combine ordinary folder text with variables such as {file_ext}, {file_created_date}, and {filename}. Blober evaluates the template separately for every matching file and creates that file's relative destination path.

media/{file_ext}/{file_created_date}/{filename}

For a video named GX015742.MP4 with a reported creation date of July 18, 2026, the relative result is:

media/mp4/2026-07-18/GX015742.MP4

If the selected destination folder is studio-archive, the complete destination becomes:

studio-archive/media/mp4/2026-07-18/GX015742.MP4

No separate organizer, database, script, or integration platform is involved. The organization happens as part of the copy or move.

Where the Feature Is in the App

Path setup spans three numbered sections in the workflow editor. For the step-by-step app reference, see the Workflows guide.

1. Source Configuration

Choose the source provider, authenticate it, then click Browse Files and Folders. You can select individual files, multiple files, folders, or an entire storage root when the provider supports it.

If at least one folder is selected, Advanced Filters (Optional) appears. It can restrict files by:

File extension
Created-date range
File-size range
Whether subdirectories are included
Include glob pattern
Exclude glob pattern

Source selection defines where Blober looks. Filters define which files inside that scope qualify.

2. Destination Configuration

Choose the destination provider and Select Destination Folder. Once the destination is complete, expand Advanced Path Template (Optional).

The Template Pattern field is appended beneath the destination folder. The variable list below the field can be clicked to add placeholders. Blober also shows an example output while the pattern is being edited.

3. Preview & Summary

The preview shows active filters, the destination template, source items, and expected destination paths. This is where a path rule becomes understandable before files move.

Do not treat preview as decoration. A template can deliberately flatten a hierarchy, split files into new folders, or rename every destination. Preview is the check that the rule means what you think it means.

The Three Path Modes

Mode 1: Copy the Structure As-Is

Leave Advanced Path Template empty and keep Include Subdirectories enabled. Blober automatically retains the relative directory structure beneath the selected folder.

Selected folder:

Projects/
  Client-A/
    Final/
      film.mp4

Destination result:

Client-A/Final/film.mp4

This is the right mode for a faithful backup. You do not need a template merely because templates exist.

Mode 2: Flatten the Selection

Leave the template empty and disable Include Subdirectories. Files are placed by filename without their relative source folders.

This can be useful when collecting documents into one destination, but duplicate filenames from different source folders may target the same destination name. Preview the result carefully.

Mode 3: Build a Custom Path

Enter a path template. The template takes control of the relative destination path. Automatic subdirectory preservation no longer adds the source hierarchy behind the scenes.

That rule is easy to miss:

{file_created_date}/{filename}

organizes by date but does not preserve source subfolders.

To retain relative source folders inside a custom path, explicitly include {file_dir}:

{file_created_date}/{file_dir}/{filename}

Read the dedicated {file_dir} guide before relying on it. Its value depends on whether a file or folder was selected and how deeply the file sits beneath that selected folder.

Every Available Variable

Variable	Meaning	Example
`{current_date}`	Current processing date	`2026-07-20`
`{current_datetime}`	Current processing date and time	`2026-07-20_14-30-00`
`{file_created_date}`	Source-reported creation date	`2026-07-18`
`{file_created_datetime}`	Source-reported creation date and time	`2026-07-18_09-15-30`
`{file_modified_date}`	Source-reported modification date	`2026-07-19`
`{file_modified_datetime}`	Source-reported modification date and time	`2026-07-19_16-45-22`
`{file_accessed_date}`	Source-reported access date	`2026-07-20`
`{file_accessed_datetime}`	Source-reported access date and time	`2026-07-20_12-00-15`
`{filename}`	Complete filename	`GX015742.MP4`
`{filename_no_ext}`	Filename without extension	`GX015742`
`{file_ext}`	Extension without the dot	`mp4`
`{file_size}`	Exact size in bytes	`1572864`
`{file_size_mb}`	Exact size in MB, rounded to two decimals	`1.50`
`{file_dir}`	Relative directory beneath the selected folder	`Day-2/Camera-A`

These are deterministic metadata substitutions, not AI classifications. Blober does not inspect an image and infer a client, location, or subject. If Client-A is not present in a selected path, filename, or available variable, a template cannot invent it.

How Template Evaluation Works

Suppose the destination folder is:

Archive

The selected source folder is:

Shoots

and one matching file is:

Shoots/Wedding-2026/Camera-A/DSC_4821.ARW

For that file:

{file_dir} = Wedding-2026/Camera-A
{filename} = DSC_4821.ARW
{filename_no_ext} = DSC_4821
{file_ext} = arw

This template:

originals/{file_dir}/{filename}

produces:

Archive/originals/Wedding-2026/Camera-A/DSC_4821.ARW

This template:

by-type/{file_ext}/{filename}

produces:

Archive/by-type/arw/DSC_4821.ARW

The second rule intentionally discards the source folder hierarchy because it does not contain {file_dir}.

Variables and Filters Solve Different Problems

Filters decide whether a file participates. Variables decide where a participating file lands.

For example:

Include pattern: **/*.{jpg,png}
Exclude pattern: **/thumbnails/**
Template: images/{file_created_date}/{filename}

The include pattern rejects non-image extensions. The exclude pattern removes thumbnails. The path template organizes the remaining files by creation date.

Keeping those concepts separate makes workflows easier to reason about:

Select a source boundary.
Filter the files inside it.
Build the destination path for each match.
Preview.
Copy or move.

Important Metadata Limits

Path templates use metadata supplied by the source provider or filesystem. Not every backend describes dates and sizes in exactly the same way.

A cloud object may expose upload or modification time rather than the camera's original capture time.
Access time may be unavailable or unhelpful on object storage.
Unknown file size becomes NO_SIZE or NO_SIZE_MB when used in a template.
{file_size_mb} creates an exact numeric folder such as 142.53; it does not automatically create human categories such as small or large.
File extensions come from filenames. A misleading extension is not content inspection.

These limits do not make templates unreliable. They define what the rule can truthfully know. Use preview to inspect real metadata from the selected source.

Copy and Move

Use Copy when:

Creating a backup
Testing a new destination structure
Building a second organized library
Keeping the source as the working location

Use Move when:

The destination has been verified
The source should be cleaned up
Files are being retired from expensive active storage

A move deletes the source after successful transfer. For any new path rule, run a representative copy first.

Blober can also reorganize between supported locations on the same provider, but source and destination cannot overlap. Do not place a destination inside the selected source tree. Choose a separate folder, bucket, container, or account.

Detailed Guides in This Series

A Safe First Workflow

Create a new workflow and choose Copy.
Select one folder containing several levels, file types, and sizes.
Choose a separate destination folder.
Enter {file_ext}/{file_dir}/{filename}.
Inspect every example in Preview & Summary.
Save and run the workflow.
Verify the actual destination before scaling up.

That small test reveals exactly how the source provider reports dates, extensions, sizes, and relative folders. Once the output is correct, the same saved workflow can handle a much larger selection.

Download Blober at blober.io to organize files as they move between cloud storage, object storage, local disks, and network drives.

Organize Blob and Object Storage Without File Search

Jul 20, 2026

Object Storage Is Not a Digital Asset Manager

S3-compatible object storage and Azure Blob Storage are excellent at durable, scalable storage. Their basic model is intentionally simple: a bucket or container holds objects identified by keys.

That model creates a familiar pain. The data is safe, but finding a useful subset can be difficult.

A typical bucket may contain:

Camera originals and edited exports
Client deliverables and internal drafts
Application uploads with generated names
Logs, reports, backups, and temporary artifacts
Years of prefixes created by different teams

Provider consoles commonly support listing by prefix and basic properties. They are not necessarily designed for visual multi-folder selection, reusable include/exclude rules, or reorganizing objects into a new human structure.

Blober does not turn object storage into full-text or AI search. It solves a narrower, practical problem: identify files from paths and metadata, then copy or move them into a better layout.

The Blober Model

An organization workflow has four layers:

Browse and select a scope. Choose a bucket area, folder-like prefix, several folders, or specific files.
Filter the scope. Restrict by extension, creation age, size, recursive inclusion, or glob rules.
Choose a destination. Use another provider, bucket, container, account, local disk, NAS, or supported non-overlapping folder.
Build paths. Preserve the hierarchy or create a custom destination with metadata variables.

The source provider does not need a native integration with the destination provider. Blober connects to both endpoints locally.

What This Can and Cannot Search

Blober can target:

Paths and filenames
File extensions
Source-reported created date
Source-reported file size
Folder depth through recursive selection
Include and exclude glob patterns

Blober path workflows do not provide:

OCR inside scanned documents
Full-text search inside PDFs
Face, object, or scene recognition
Speech transcription
Semantic search such as "all beach videos"

That boundary matters. If filenames and paths contain useful conventions, Blober can act on them immediately. If the only useful information exists inside file contents, a dedicated indexing system is still required.

Example: Recover a Flat Media Bucket

Suppose a bucket contains:

uploads/GX015742.MP4
uploads/GOPR0001.JPG
uploads/DSC_4821.ARW
uploads/contract.pdf
uploads/proxies/GX015742-low.mp4

Select uploads, then configure:

Include: **/*.{mp4,mov,jpg,jpeg,arw,dng}
Exclude: **/proxies/**
Template: media/{file_ext}/{file_created_date}/{filename}

The destination becomes browseable by extension and source-reported creation date. The source can remain unchanged if the action is Copy.

Example: Extract Business Records

A company bucket mixes customer uploads, generated reports, and temporary processing artifacts.

Selected prefix: production
Include: **/*.{pdf,csv,xlsx,json}
Exclude: **/{tmp,temp,cache,failed}/**
Template: records/{file_modified_date}/{file_dir}/{filename}

This creates a separate records archive while retaining relative source context.

Example: Split Active and Archive Storage

Large inactive files can remain expensive in active storage.

Create a workflow that:

Selects completed project prefixes
Filters to large files
Excludes current working or proxy folders
Copies to a lower-cost archive provider
Preserves {file_dir}/{filename}

Verify the archive before considering a move or source cleanup.

Reorganizing on the Same Provider

Where the adapter supports the selected source and destination action, Blober can copy or move between separate locations on the same provider.

The destination cannot be the same as the source or nested inside a selected source folder. That overlap could make the scan loop over its own output or overwrite files. Choose a sibling prefix, separate bucket/container, or separate account.

For example:

Source: messy-imports
Destination: organized-archive
Template: {file_ext}/{file_created_date}/{file_dir}/{filename}

Copy first. Compare counts and sample files. Move only when deleting the source is intentional.

Why Not Build an Index First?

A search index is appropriate when users need ongoing content discovery. It also introduces ingestion, synchronization, schemas, permissions, infrastructure, and recurring cost.

Blober is useful when the immediate pain is operational:

"Copy every final MP4 but not proxies."
"Move PDFs older than the working set into an archive."
"Separate RAW files from exports."
"Preserve every project subfolder while changing the top-level layout."
"Collect large files into cheaper storage."

Those are transfer-and-path problems. They do not need a permanent search service.

Make the Destination Easier to Search Next Time

Organization during transfer can encode the metadata users actually browse:

archive/{file_ext}/{file_created_date}/{file_dir}/{filename}

The destination now supports useful prefix browsing:

Start at type
Narrow to a date
Retain project hierarchy
End at the original filename

This is not semantic search, but it converts an opaque dump into predictable paths using information already available.

Safe Rollout

Choose one painful prefix rather than the whole bucket.
Use Copy.
Add the smallest useful include/exclude rule.
Add a path template only if the preserved structure is insufficient.
Review Preview & Summary.
Run and verify object counts and samples.
Expand the selection after the rule proves itself.

See selection and glob filters for pattern details and the complete path-template guide for destination behavior.

Cloud Storage Ingress vs Egress Fees: Which Providers Are Free?

Jun 29, 2026

Ingress is data going into a cloud. Egress is data coming out of a cloud. That sounds simple until you move data between providers: the source sees egress, the destination sees ingress, and both sides may also charge for requests, retrieval, minimum storage duration, or storage-class transitions.

For a migration from AWS S3 to Cloudflare R2, for example, AWS is the egress side and R2 is the ingress side. R2's zero-egress pricing helps after the move, but it does not erase the source provider's charge for reading data out. A direct transfer avoids a relay and a second full local copy; it does not make source egress disappear.

Ingress Is Usually Free, Egress Is Not

Most object-storage providers make network ingress free, or close to it. Uploading data is how they get storage revenue, so they rarely put a bandwidth toll at the door. But writes can still create API, PUT, multipart, replication, or storage-class charges. AWS S3, for example, says S3 costs include request, retrieval, data transfer, transfer acceleration, replication, transform, and query components, and it separately calls out per-request ingest charges for some writes and lifecycle transitions^[1].

Egress is the expensive side. It is what you pay when users download files, an app serves media, a backup restore reads data out, or a migration leaves a provider. Azure lists data transfer in as free, but internet egress from Azure data centers is priced by zone and volume^[2]. Google Cloud Storage lists inbound data transfer as free, while general outbound transfer to the internet is billable after any free-tier allowance^[3].

Use that difference to decide what to optimize for:

Prioritize ingress for backup targets, one-time imports, camera dumps, and upload-heavy workflows.
Prioritize egress for public assets, media delivery, AI training reads, frequent restores, and any data you may need to leave with later.
Prioritize both when the same bucket is active in both directions: teams moving data between clouds, hot archives, shared datasets, or migration staging buckets.

Provider Groups by Transfer Pricing

Pricing changes, and providers define "free" differently. Use this as a map, then verify the current pricing page before committing production data.

Group	Providers	What is free or included	Watch for
Zero-egress or no separate egress line	Cloudflare R2, Wasabi, Synology C2, Impossible Cloud, Telnyx	R2 publishes no egress bandwidth charges^[4]. Wasabi publishes no egress or API request fees, with minimum storage rules^[5]. Synology C2 advertises free data retrieval and no API request or deletion fees^[6]. Impossible Cloud publishes free egress and API calls^[7]. Telnyx markets Cloud Storage as an S3-compatible alternative with zero egress fees^[8].	Operation fees, retrieval processing fees, minimum storage duration, support tiers, and fair-use terms can still matter. Impossible Cloud's docs say monthly egress should not exceed active storage volume under its fair-use policy^[9].
Allowance-based free egress	Backblaze B2, MEGA S4, IDrive e2, Storadera, Rabata Backup	Backblaze B2 includes free egress up to 3x average monthly stored data, then bills additional egress^[10]. MEGA S4 describes up to 5x average monthly stored data as free egress^[11]. IDrive e2 says there are no additional ingress, egress, deletion, or API-request charges, but its page also notes charges beyond free egress limits^[12]. Storadera allows downloads equal to stored amount under fair use^[13]. Rabata Backup has no additional egress fee, with egress expected to stay under 2x stored amount^[14].	These can be excellent for backups and normal restores, but not for unlimited media delivery. Read the multiplier, overage price, and fair-use language.
Bundled outbound transfer	DigitalOcean Spaces, Vultr Object Storage	DigitalOcean Spaces includes 1 TiB outbound transfer, then charges additional transfer^[15]. Vultr Object Storage pricing bundles selected storage with selected bandwidth, then charges for additional transferred data^[16].	Good for predictable app storage when the included bandwidth matches your traffic. Less good if traffic can spike far beyond the bundle.
Paid egress baseline	AWS S3, Azure Blob, Google Cloud Storage	Uploading data is usually the easier side, but outbound data transfer is a major pricing dimension. AWS S3 data transfer pricing has explicit in/out components^[17]. Azure data transfer in is free, while internet egress is priced by region and volume^[18]. Google Cloud Storage inbound data transfer is free, while general outbound transfer is priced by destination and volume^[19].	These platforms can be the right choice for deep ecosystem integration, analytics, identity, compliance, and managed services. Do not pick them on storage price alone if your workload reads heavily.

When Ingress Should Decide

Ingress matters most when your workload mostly writes data and rarely reads it back. Examples:

Nightly backups into object storage.
Camera, drone, or GoPro footage uploaded after shoots.
One-time imports into a long-term archive.
Logs and machine-generated data flowing into cold storage.
Migration into a destination you plan to keep using.

Free ingress is useful, but it is rarely enough by itself. For upload-heavy work, also check the provider's region list, multipart upload limits, request pricing, small-object behavior, and minimum storage duration. A provider with free uploads but a distant region may still be slower and less reliable than a provider close to your source.

If the upload is a one-time migration, the destination's ingress policy is only half the bill. The source provider's egress and read/retrieval charges are usually the part that hurts.

When Egress Should Decide

Egress matters when data leaves storage often. Examples:

Public downloads, app assets, images, and videos.
CDN origin storage.
AI or analytics jobs that repeatedly read training datasets.
Backup restores that are tested often.
Customer exports and data portability.
Any archive you may need to leave later.

This is where zero-egress and allowance-based providers earn attention. Cloudflare R2 is built around no egress bandwidth charges. Backblaze B2's 3x allowance is generous for many backup and archive patterns. Wasabi, Synology C2, Impossible Cloud, and similar providers can make bills easier to predict, but their minimums and fair-use terms decide whether they fit your exact workload.

If you serve a 10 TB media library once a month, a 1x egress fair-use policy may be enough. If users download the same 10 TB library ten times a month, you need true zero egress, a CDN strategy, or a negotiated plan.

When You Need Both

Some workloads are both write-heavy and read-heavy:

Active media teams ingest footage, review it, deliver it, and archive it.
AI teams upload new datasets and read them repeatedly during experiments.
Agencies move client files in and out of storage every week.
Multi-cloud teams use an object store as a staging area between providers.
Backup teams run frequent restore tests instead of treating backups as write-only.

For these, compare the whole transfer loop:

Source egress and read/retrieval fees.
Destination ingress, write, and operation fees.
Storage cost and minimum retention.
Destination egress for future reads, restores, or exits.
Tool cost and whether it adds a relay hop.

The common mistake is optimizing only for the first upload. A cheap destination that charges heavily when you read data back may be fine for a legal archive and wrong for a media workflow.

How Blober Fits

Blober does not charge per GB and does not relay your files through Blober servers. It runs on your machine, reads from the source, and writes to the destination. That keeps the route local and avoids an extra transfer-service bill.

Provider fees still apply. If the source charges egress, you pay the source. If the destination charges PUT requests, retrieval, or storage, you pay the destination. The value of a direct desktop transfer is that it avoids an additional middle service, keeps your credentials local, and lets you choose the storage provider whose ingress and egress model fits the job.

Frequently Asked Questions

Does free ingress mean a migration is free? No. Free ingress only describes the destination side. The source can still charge egress, retrieval, or read requests.

Does zero egress mean there are no storage costs? No. You still pay for storage, operations, retrieval processing if the provider has it, minimum duration, and any add-on services. Zero egress means the provider does not bill outbound bandwidth as a separate line item.

Should backups optimize for ingress or egress? Both, but for different reasons. You write backups often, so ingress performance matters. You restore rarely but urgently, so egress cost and restore speed matter when something goes wrong.

Can a transfer tool avoid egress fees? Not source-provider egress. A tool can avoid an extra relay, subscription, or duplicate local staging step, but the source provider still sees data being read out.

Get Blober

Compare providers on the bill that matters, then move the data directly. Blober connects S3, S3-compatible storage, Azure Blob, Dropbox, Google Drive, GoPro Cloud, and more without per-GB transfer fees.

Download Blober at blober.io

Best S3-Compatible Object Storage Specialists (Independent Clouds)

Jun 28, 2026

Some clouds do one thing: S3-compatible object storage, priced and tuned for it. These are the specialists to compare when you want predictable storage costs without the egress surprises of the hyperscalers. This page lists the independent object-storage clouds, their endpoint formats, and how to connect each one.

This is one category in our complete list of S3-compatible storage providers. Several of these have a preconfigured connector in Blober; the rest use the generic S3-Compatible connector. Confirm endpoints in each provider's dashboard, since regions change over time. The endpoint formats below come from each provider's own documentation, cross-checked against current S3 client references^[1].

Each entry lists an addressing style. Virtual-hosted puts the bucket in the subdomain (https://my-bucket.s3.example.com); path-style puts it in the URL path (https://s3.example.com/my-bucket). Most providers here use virtual-hosted, and Blober picks the style from the endpoint field you fill in. The endpoint formats below show hostnames; in Blober, include https:// in the endpoint field. The endpoint setup notes explain it in full.

Wasabi Hot Cloud Storage

Wasabi is flat-rate object storage with no egress fees and no API request charges, popular for backups and media archives.

Endpoint format: s3.<region>.wasabisys.com (for example s3.wasabisys.com for US East 1, s3.eu-central-1.wasabisys.com).
Regions: Virginia (US East 1 and 2), Texas, Oregon, San Jose, Toronto, Amsterdam, Frankfurt, London (two regions), Paris, Milan, Tokyo, Osaka, Singapore, and Sydney^[2].
Addressing: virtual-hosted.
Notes: egress and API requests are not separately billed under Wasabi's published pricing terms, but minimum storage rules still matter: a 1 TB minimum and a 90-day minimum storage duration apply^[3]. Blober has a preconfigured Wasabi connector.

Backblaze B2 Cloud Storage

Backblaze B2 is among the lowest per-GB object storage prices, with an S3-compatible API alongside its native one.

Endpoint format: s3.<region>.backblazeb2.com (for example s3.us-west-004.backblazeb2.com).
Regions: US West, US East, and EU Central account regions; copy the exact endpoint from the bucket's Endpoint field, since Backblaze says an account is associated with a single region and S3 endpoints use s3.<region>.backblazeb2.com^[4].
Addressing: virtual-hosted.
Notes: free egress is up to 3x average monthly data stored, then additional egress is billed per GB^[5]. Blober has a preconfigured Backblaze B2 connector. See also How to Switch Wasabi to Backblaze B2.

Cloudflare R2

Cloudflare R2 is object storage with zero egress fees, served from Cloudflare's global edge network.

Endpoint format: <account-id>.r2.cloudflarestorage.com.
Regions: buckets are automatically distributed; the region is set to auto.
Addressing: virtual-hosted.
Notes: Cloudflare documents auto as the S3 API bucket region, with empty and us-east-1 accepted as aliases for compatibility^[6]. R2 has no egress bandwidth charges, though operation and Infrequent Access retrieval charges can still apply^[7]. Blober has a preconfigured Cloudflare R2 connector. See How to Move Azure Blob to Cloudflare R2.

Rabata

Rabata is S3-compatible secure cloud storage with flat, transparent pricing and no API request fees.

Endpoint format: s3.<region>.rabata.io (for example s3.eu-west-2.rabata.io).
Regions: US East (us-east-1, N. Virginia) and EU West (eu-west-2, London); Rabata's quickstart examples use s3.us-east-1.rabata.io, and its billing page maps Hot Storage to us-east-1 and Backup to eu-west-2^[8].
Addressing: virtual-hosted.
Notes: two flat-priced tiers. Hot Storage (us-east-1) is $0.01/GB and Backup (eu-west-2) is $49 per 10 TB block, with no API request charges and free ingress. Backup has no egress fees, with egress capped at 2x your stored volume^[9]. Blober has a preconfigured Rabata connector.

Storj

Storj is decentralized cloud storage with an S3-compatible hosted gateway. Data is encrypted and erasure-coded across a global network of nodes.

Endpoint format: gateway.storjshare.io (plus regional gateways gateway.eu1.storjshare.io, gateway.us1.storjshare.io, gateway.ap1.storjshare.io).
Regions: global; set S3-compatible tools to global when they require a region^[10].
Addressing: virtual-hosted.
Notes: S3 credentials come from an access grant. Storj's S3 compatibility table calls out partial support for some listing and multipart-copy behavior, so treat advanced S3 semantics as provider-specific and verify workflows that depend on exact listing order, ListMultipartUploads, or UploadPartCopy^[11]. Storj also appears on our decentralized storage page.

IDrive e2

IDrive e2 is low-cost S3-compatible object storage with free egress allowances, aimed at backup and archive.

Endpoint format: <region>.idrivee2-XX.com, where the host is shown in your console (for example q9d9.la12.idrivee2-5.com).
Regions: many across the US, Europe, and Asia-Pacific^[12].
Addressing: virtual-hosted.
Notes: the endpoint host is account- and region-specific, so copy it from the IDrive e2 dashboard.

Cubbit DS3

Cubbit DS3 is a geo-distributed, S3-compatible object storage platform with European data residency.

Endpoint format: s3.cubbit.eu, or s3.<tenant>.cubbit.eu for a custom tenant.
Regions: geo-distributed; Cubbit describes DS3 as an S3-compatible object-storage platform that fragments data across its distributed network, so confirm the current region and tenant endpoint in your Cubbit console^[13].
Addressing: virtual-hosted.
Notes: if you use a custom tenant endpoint, you must use the tenant-specific host; the generic one will not work in that case^[14].

Impossible Cloud

Impossible Cloud is a European S3-compatible object storage provider with regions in Europe and the US.

Endpoint format: <region>.storage.impossibleapi.net (for example eu-central-2.storage.impossibleapi.net).
Regions: Frankfurt (eu-central-2), Amsterdam (eu-west-1), London (eu-west-2), Paris (eu-west-3), Poznan (eu-east-1), Copenhagen (eu-north-1), and New York (us-east-1)^[15].
Addressing: virtual-hosted.
Notes: the public limitations page documents bucket/object limits and object-name conflict rules, not a blanket transfer problem. Browse, upload, download, and copy should be fine for ordinary transfers, but validate workflows that depend on exact AWS-only edge behavior or conflicting folder/object keys^[16].

Seagate Lyve Cloud

Seagate Lyve Cloud is enterprise-grade S3-compatible storage from Seagate.

Endpoint format: s3.<region>.<account>.lyve.seagate.com, where the account name is part of the host (for example s3.us-west-1.global.lyve.seagate.com).
Regions: US West (California), EU West (Ireland), and more.
Addressing: virtual-hosted.
Notes: the distinctive setup detail is the account-specific host: copy the S3 endpoint from Lyve Cloud for your account and region instead of treating lyve.seagate.com as a generic endpoint^[17].

Synology C2 Object Storage

Synology C2 is S3-compatible object storage from the NAS maker, with no API request fees, download fees, or deletion penalties.

Endpoint format: <region>.s3.synologyc2.net (for example eu-001.s3.synologyc2.net, us-001.s3.synologyc2.net).
Regions: Europe and the US; Synology documents these data centers on its object-storage overview and exposes C2 Object Storage through C2 OneStorage pricing^[18].
Addressing: virtual-hosted.
Notes: no charge for egress or API requests is listed for C2 Object Storage under C2 OneStorage pricing^[19]. It is a natural pairing for Synology NAS owners who want an off-site S3 copy.

MEGA S4 Object Storage

MEGA S4 is an S3-compatible object store with regional endpoints and a published free-egress allowance.

Endpoint format: s3.<region>.megas4.com (for example s3.eu-amsterdam.megas4.com).
Regions: Amsterdam, Luxembourg, Paris, Barcelona, Montreal, Vancouver, Tokyo^[20].
Addressing: virtual-hosted.
Notes: MEGA says buckets are not restricted to one region; pick the endpoint closest to your users or workloads. MEGA's object-storage page describes up to 5x average monthly stored data as free egress, so check the current plan terms before using it for high-volume delivery^[21].

Tebi

Tebi is a geo-distributed S3-compatible object store with a global endpoint and optional regional endpoints.

Endpoint format: s3.tebi.io.
Regions: global endpoint via GeoDNS, plus Germany, US East, US West, and Singapore regional S3 endpoints^[22].
Addressing: virtual-hosted.
Notes: Tebi storage classes control where data is physically stored and how many copies are kept; use the console settings for current placement and performance choices^[23].

Storadera

Storadera is a European S3-compatible object storage provider with flat, simple pricing.

Endpoint format: <region>.s3.storadera.com (for example eu-east-1.s3.storadera.com).
Regions: Europe; confirm the current regional endpoint in the console.
Addressing: virtual-hosted.
Notes: Storadera publishes no upload charges and no download charges under fair use, where the allowed monthly download amount equals the stored amount^[24].

Telnyx Cloud Storage

Telnyx Cloud Storage is S3-compatible object storage from the communications platform Telnyx.

Endpoint format: <region>.telnyxcloudstorage.com (for example us-central-1.telnyxcloudstorage.com).
Regions: US Central, US East, US West, and EU Central^[25].
Addressing: virtual-hosted.
Notes: Telnyx billing is based on stored bytes and API operation counts; its docs list separate US and EU storage/operation pricing^[26].

Tigris

Tigris is a globally distributed S3-compatible object store (built with Fly.io) that routes through a single endpoint.

Endpoint format: t3.storage.dev.
Regions: San Jose, Chicago, Ashburn, Amsterdam, Frankfurt, London, Singapore, Tokyo. Set the region to auto; the same page also lists additional Fly.io locations, so check the docs for the current list^[27].
Addressing: virtual-hosted.
Notes: buckets can be global, multi-region, dual-region, or single-region; the single endpoint handles routing.

FileLu S5

FileLu S5 is an S3-compatible object store with a single global endpoint and regional options.

Endpoint format: s5lu.com (global), with us.s5lu.com, eu.s5lu.com, ap.s5lu.com, and me.s5lu.com for regions.
Regions: Global, US East, EU Central, AP Southeast, ME Central^[28].
Addressing: not explicitly documented; start with path-style in the generic connector unless your FileLu client configuration confirms virtual-hosted support.
Notes: predictable pricing with no separate transfer or API charges.

Petabox

Petabox is S3-compatible object storage with regions across several continents and free ingress.

Endpoint format: s3.<region>.petabox.io (for example s3.us-east-1.petabox.io), or s3.petabox.io for US East.
Regions: Virginia, Frankfurt, Singapore, Bahrain, Sao Paulo.
Addressing: virtual-hosted.
Notes: confirm the regional endpoint in the Petabox console^[29].

Zata

Zata is an S3-compatible object storage gateway with a focus on South Asia.

Endpoint format: idr01.zata.ai.
Regions: Indore, India (South Asia endpoint).
Addressing: virtual-hosted.
Notes: confirm the endpoint in the Zata console^[30].

Filebase

Filebase is an S3-compatible gateway that stores objects on decentralized networks (IPFS and others) behind a familiar S3 API.

Endpoint format: s3.filebase.io.
Regions: single global endpoint; Filebase uses region auto for SigV4 signing.
Addressing: both path-style (https://s3.filebase.io/<bucket>/<key>) and virtual-hosted (https://<bucket>.s3.filebase.io/<key>) are supported^[31].
Notes: public-bucket reads should use the virtual-hosted URL. Filebase also appears on our decentralized storage page.

Frequently Asked Questions

Which S3-compatible specialist has no egress fees? Several limit or remove separate egress charges, but the details differ. Cloudflare R2, Wasabi, Synology C2, Impossible Cloud, and Telnyx publish zero-egress or no-separate-egress positioning; Backblaze B2 includes free egress up to 3x average monthly stored data; MEGA S4 publishes up to 5x; Rabata Backup and Storadera use fair-use caps. See Cloud Storage Ingress vs Egress Fees for the split.

Are these as reliable as AWS S3? Durability and availability are each provider's own design, and many publish strong durability figures. Compatibility refers to the API, not to a guarantee of identical reliability, so check the provider's SLA for your use case.

Can I migrate from AWS S3 to one of these specialists? Yes. Because they share the core S3 API, Blober copies directly from S3 to the specialist by setting the source and destination endpoints. Validate provider-specific behavior if you rely on advanced S3 features.

Which preconfigured connectors does Blober include? For this category, Wasabi, Backblaze B2, Cloudflare R2, and Rabata are preconfigured. The rest connect through the generic S3-Compatible connector.

Get Blober

Connect to any S3-compatible specialist by URL and move data in or out directly, without filling your local disk.

Download Blober at blober.io

Decentralized and Web3 S3-Compatible Storage (Storj, Filebase, and More)

Jun 28, 2026

Decentralized storage spreads your data across a network of independent nodes instead of one company's data centers. What makes them usable day to day is the S3-compatible gateway: it puts a standard S3 API in front of the decentralized backend, so your existing S3 tools write to IPFS, Sia, or a node network without touching the underlying protocol. This page lists the decentralized and Web3 S3-compatible providers and how to connect each one.

This is one category in our complete list of S3-compatible storage providers. These connect to Blober through the generic S3-Compatible connector when the gateway supports the common S3 operations Blober uses: you point it at the gateway endpoint with the keys the network issues.

Storj

Storj is decentralized cloud storage where files are encrypted, split, and erasure-coded across thousands of independent nodes worldwide. Its S3-compatible hosted gateway makes all of that invisible to S3 tools.

Endpoint format: gateway.storjshare.io, with regional gateways gateway.eu1.storjshare.io, gateway.us1.storjshare.io, and gateway.ap1.storjshare.io.
Addressing: virtual-hosted.
Notes: S3 credentials are generated from an access grant in the Storj console. Storj is globally distributed by default; when an S3-compatible tool requires a region, set it to global^[1]. Use a large multipart cutoff for very large files. Storj also appears on our object storage specialists page.

Filebase

Filebase is an S3-compatible gateway that stores objects on decentralized networks (IPFS, and historically Sia and Storj) while presenting a familiar S3 API and console.

Endpoint format: s3.filebase.io.
Addressing: both path-style (https://s3.filebase.io/<bucket>/<key>) and virtual-hosted (https://<bucket>.s3.filebase.io/<key>) are supported.
Notes: Filebase uses a single global endpoint and region auto; public-bucket reads should use the virtual-hosted URL served by the Filebase CDN^[2].

4everland

4everland is a Web3 infrastructure platform whose Bucket service offers an S3-compatible API backed by IPFS and Arweave.

Endpoint format: endpoint.4everland.co.
Addressing: virtual-hosted.
Notes: designed for hosting and pinning assets to decentralized networks while keeping the S3 workflow. Generate keys in the 4everland dashboard; the documented S3-compatible endpoint is https://endpoint.4everland.co^[3].

Akave

Akave provides decentralized object storage with an S3-compatible interface (Akave O3) aimed at data availability for AI and Web3 workloads.

Endpoint format: the S3-compatible gateway endpoint issued in your Akave account.
Addressing: virtual-hosted.
Notes: confirm the current endpoint host and credentials in the Akave console, as the production gateway address is account-specific. Akave's docs list akave-network as the region value for its decentralized S3 interface and show hosted endpoints such as https://o3-rc2.akave.xyz for specific environments^[4].

How the Gateway Pattern Works

Most decentralized networks were not designed around the S3 API. What makes them usable from ordinary tools is a gateway that translates S3 calls into the network's native operations: pinning to IPFS, contracts on Sia, erasure-coding across Storj nodes, and so on. From your side, it is just an endpoint and a pair of keys.

That is the same reason Blober can treat a decentralized gateway like a normal S3 target for common object operations. You do not interact with the network protocol; you point the S3-Compatible connector at the gateway and transfer as usual.

A few practical points for decentralized targets:

Server-side copy may be limited. Some gateways do not implement S3 server-side copy. Blober falls back to streaming the copy through, so transfers still work.
Listing and metadata can differ. Treat these stores as S3-compatible for the common operations (browse, upload, download) and confirm any advanced behavior with the provider.
Encryption is often built in, but check where it happens. Networks like Storj encrypt and erasure-code data before it leaves the hosted gateway, but the gateway still handles the upload. Add client-side encryption if your threat model requires the gateway itself not to see plaintext.

Frequently Asked Questions

Is decentralized storage really S3-compatible? The storage networks themselves are not S3, but their gateways are. You connect to the gateway endpoint with S3 keys, and standard S3 tools work. That is what "S3-compatible" means here.

Can I move data from AWS S3 to Storj or Filebase? Yes. Because the gateways speak S3, Blober copies directly from an S3 bucket to the decentralized gateway by setting the source and destination endpoints.

Do these keep my data private? Several encrypt data before it is distributed (Storj is a notable example). Check each provider's encryption model, since the details differ between networks.

Why might a transfer behave differently than to AWS? Some gateways limit server-side copy or return listings differently. Blober handles the copy fallback automatically, so the transfer completes even when native copy is unavailable.

Get Blober

Connect Blober to a decentralized S3 gateway by URL and move data between Web3 storage and the rest of your clouds directly, without filling your local disk.

Download Blober at blober.io

Enterprise and On-Premises S3-Compatible Storage Systems

Jun 28, 2026

Behind the cloud services, there is a large market of enterprise storage platforms that expose an S3-compatible endpoint inside the data center. These are the systems that hold petabytes for media companies, banks, research labs, and government, and they all speak S3 so that standard tools can read and write to them. This page lists the enterprise and on-premises S3-compatible platforms and how to connect each one.

This is one category in our complete list of S3-compatible storage providers. All of these connect to Blober through the generic S3-Compatible connector: you point it at the system's S3 endpoint (often a data VIP or load-balanced address inside your network) with your keys. Most on-premises systems prefer path-style addressing. The endpoint notes below come from each vendor's own documentation, cross-checked against current S3 client references^[1]. The endpoint setup notes explain path-style and virtual-hosted addressing.

NetApp StorageGRID

NetApp StorageGRID is a widely deployed enterprise object store with a mature S3 implementation, used for backup targets, archives, and data lakes.

Endpoint format: your StorageGRID gateway or load-balancer address (your own deployment).
Addressing: both styles are supported; path-style is common on-prem.
Notes: StorageGRID supports S3 features like versioning, object lock, and lifecycle, which makes it a strong compliance and ransomware-recovery target^[2].

NetApp ONTAP S3

NetApp ONTAP, the operating system behind FAS and AFF arrays and Cloud Volumes ONTAP, includes an S3 object server.

Endpoint format: the S3 server address you configure on the ONTAP system.
Addressing: path-style is the safe default.
Notes: beginning with ONTAP 9.8, you can enable an ONTAP S3 object storage server in an ONTAP cluster and manage it with System Manager or the ONTAP CLI^[3].

Dell ECS and ObjectScale

Dell ECS (Elastic Cloud Storage) and its containerized successor ObjectScale are enterprise object platforms with a full S3 API.

Endpoint format: your ECS or ObjectScale data node or load-balancer address.
Addressing: both styles; path-style is common on-prem.
Notes: designed for multi-site, geo-distributed deployments with active-active access^[4].

Cloudian HyperStore

Cloudian HyperStore is an S3-native enterprise object store sold as software or as an appliance, known for close S3 API fidelity.

Endpoint format: your HyperStore S3 endpoint (data VIP or load balancer).
Addressing: both styles supported.
Notes: Cloudian markets very high S3 API compatibility, including object lock for immutability^[5].

Pure Storage FlashBlade

Pure Storage FlashBlade is a high-performance, all-flash platform with an S3-compatible object store.

Endpoint format: https://<s3-data-vip> (the FlashBlade S3 data VIP).
Addressing: path-style works everywhere; virtual-hosted needs DNS so that bucket.<endpoint> resolves to the data VIP.
Notes: supports ListObjectsV2, multipart with AWS-compatible ETags, versioning, and advanced checksums on recent Purity releases^[6].

Hitachi Content Platform (HCP)

Hitachi Content Platform is an enterprise object store for long-term retention and compliance, with an S3-compatible API.

Endpoint format: https://<your-hcp-host>.
Addressing: path-style is the safe default.
Notes: HCP supports namespace access through REST, the Hitachi API for Amazon S3, WebDAV, CIFS, and NFS; in the S3-compatible API, namespaces are called buckets^[7].

Spectra Logic BlackPearl

Spectra Logic BlackPearl is an on-premises S3-compatible gateway that tiers data to disk, tape, and public clouds under one namespace.

Endpoint format: https://<your-blackpearl-host>.
Addressing: path-style.
Notes: popular for media archives and backup where tape economics matter^[8].

Scality RING and ARTESCA

Scality RING is a petabyte-scale software-defined object store; ARTESCA is its lighter, cloud-native sibling. Both expose S3.

Endpoint format: your RING or ARTESCA S3 endpoint (load balancer or connector address).
Addressing: both styles supported.
Notes: Scality also maintains the open-source Zenko CloudServer, so the S3 lineage runs deep^[9].

Quantum ActiveScale

Quantum ActiveScale (formerly Western Digital ActiveScale) is an enterprise object system tuned for large-capacity archives and cold data.

Endpoint format: your ActiveScale S3 endpoint (load-balanced address).
Addressing: path-style is common.
Notes: often paired with tape for very long-term retention^[10].

DataCore Swarm (formerly Caringo Swarm)

DataCore Swarm is an object storage platform with an S3-compatible gateway, used for archives and content repositories.

Endpoint format: your Swarm S3 gateway address.
Addressing: path-style is common.
Notes: focuses on long-term data protection and large media libraries^[11].

Nutanix Objects

Nutanix Objects is the S3-compatible object service in the Nutanix hyperconverged platform.

Endpoint format: the Objects store endpoint you configure in Prism.
Addressing: both styles supported.
Notes: integrates object storage into existing Nutanix clusters^[12].

VAST Data

VAST Data is an all-flash, scale-out platform that exposes S3 alongside file protocols.

Endpoint format: your VAST S3 endpoint (virtual IP or load balancer).
Addressing: path-style is the safe default.
Notes: aimed at high-throughput analytics and AI pipelines^[13].

WekaFS (Weka)

Weka is a high-performance data platform with an S3 protocol front end over its parallel file system.

Endpoint format: your Weka S3 endpoint (cluster address).
Addressing: path-style is common.
Notes: built for GPU and HPC workloads that also need object access^[14].

Zadara

Zadara is fully managed, enterprise-grade S3-compatible storage with on-prem, hybrid, and cloud deployment options.

Endpoint format: https://<vsa-id>.zadarazios.com (for example https://vsa-00000001-public-zadara-cloud-01.zadarazios.com).
Addressing: virtual-hosted, with us-east-1 as the default region.
Notes: fetch the endpoint and region from the Zadara Object Storage management interface^[15].

A Note on IBM Cloud Object Storage and MinIO On-Premises

Two systems span the cloud and on-prem worlds. IBM Cloud Object Storage (covered on the cloud providers page) is also sold as on-premises software descended from Cleversafe. MinIO (covered on the self-hosted page) is deployed in many enterprises as a production object tier, not just for testing. Both connect to Blober the same way: point the generic S3-Compatible connector at the endpoint.

Frequently Asked Questions

Can Blober connect to an on-premises storage array? Yes, as long as the array exposes an S3 endpoint your machine can reach. Use the system's data VIP or load-balanced address with your keys, and pick path-style addressing if browsing fails.

Do enterprise systems support S3 object lock and versioning? Many do (StorageGRID, Cloudian, Dell ECS, and others), which is why they are used as immutable backup and compliance targets. Confirm the specific features with your vendor.

Why do these prefer path-style addressing? Virtual-hosted addressing needs DNS so that every bucket.<endpoint> name resolves to the storage. On-prem systems often skip that, so path-style (bucket in the URL path) is the reliable default.

Can I move data from an on-prem array to the cloud? Yes. Blober copies directly between your on-prem S3 endpoint and cloud S3 endpoints that support the normal object operations it uses, or to non-S3 targets like Azure Blob, without staging a full copy on your disk.

Get Blober

Connect Blober to your enterprise S3 endpoint by URL and move data between on-prem storage and the cloud directly, without filling your local disk.

Download Blober at blober.io

S3-Compatible Cloud Object Storage Providers (Hyperscalers and Regional Clouds)

Jun 28, 2026

The large platform clouds all run object storage, and most expose an Amazon S3-compatible endpoint alongside their native API. That means you can point an S3 client at Alibaba, Tencent, Huawei, IBM, Oracle, Google, Yandex, and many regional clouds by changing the endpoint URL and keys. This page lists the cloud S3-compatible services, their endpoint formats, and how to connect each one.

This is one category in our complete list of S3-compatible storage providers. For independent object-storage clouds, hosting platforms, self-hosted servers, enterprise appliances, and decentralized storage, see the other category pages linked at the end.

These services are intended to connect through Blober's generic S3-Compatible connector when they support the common S3 operations Blober uses. Paste the endpoint and keys, then browse to confirm. Confirm the exact endpoint in each provider's console, since regions and hostnames change over time. The endpoint formats below come from each provider's own documentation, cross-checked against current S3 client references^[1].

Each entry notes an addressing style. Virtual-hosted puts the bucket in the subdomain (https://my-bucket.s3.example.com); path-style puts it in the URL path (https://s3.example.com/my-bucket). Almost every cloud here uses virtual-hosted. The endpoint formats below show hostnames; in Blober, include https:// in the endpoint field. The endpoint setup notes explain how Blober picks the right one.

Alibaba Cloud OSS (Object Storage Service)

Alibaba Cloud Object Storage Service, formerly Aliyun OSS, is the dominant object store in China and across Alibaba's global regions.

Endpoint format: oss-<region>.aliyuncs.com (for example oss-cn-hangzhou.aliyuncs.com, oss-us-east-1.aliyuncs.com, oss-eu-central-1.aliyuncs.com).
Regions: dozens across mainland China, plus Singapore, Tokyo, Frankfurt, London, Dubai, Silicon Valley, and Virginia.
Addressing: virtual-hosted (bucket in subdomain).
Notes: OSS offers Standard, Infrequent Access, Archive, and Cold Archive tiers. Use the matching regional endpoint for your bucket^[2].

Tencent Cloud COS (Cloud Object Storage)

Tencent Cloud Object Storage is the object store behind much of China's app ecosystem, with a global region footprint.

Endpoint format: cos.<region>.myqcloud.com (for example cos.ap-guangzhou.myqcloud.com, cos.ap-singapore.myqcloud.com, cos.na-ashburn.myqcloud.com).
Regions: Beijing, Shanghai, Guangzhou, Chengdu, Hong Kong, Singapore, Mumbai, Seoul, Bangkok, Tokyo, Silicon Valley, Virginia, Toronto, Frankfurt.
Addressing: virtual-hosted.
Notes: there is also a Global Acceleration endpoint (cos.accelerate.myqcloud.com). Standard, Infrequent Access, and Archive tiers are available^[3].

Huawei Cloud OBS (Object Storage Service)

Huawei Cloud OBS is a high-capacity object store with an S3-compatible interface, used widely across Asia, Latin America, and EMEA.

Endpoint format: obs.<region>.myhuaweicloud.com (for example obs.af-south-1.myhuaweicloud.com, obs.ap-southeast-3.myhuaweicloud.com).
Regions: Johannesburg, Bangkok, Singapore, Hong Kong, Shanghai, Beijing, Guangzhou, plus Latin America (Sao Paulo, Mexico City, Santiago, Buenos Aires, Lima) and Moscow.
Addressing: virtual-hosted.
Notes: OBS underpins several rebranded regional clouds (Open Telekom Cloud and SberCloud, listed below), so the connection pattern is similar^[4].

IBM Cloud Object Storage (COS)

IBM Cloud Object Storage, descended from Cleversafe, disperses data across locations and is accessed through an S3-compatible API. It is also sold as on-premises software.

Endpoint format: s3.<region>.cloud-object-storage.appdomain.cloud (for example s3.us-east.cloud-object-storage.appdomain.cloud, s3.eu-de.cloud-object-storage.appdomain.cloud).
Regions: US East and South, EU (Frankfurt, Amsterdam, Milan), Great Britain, plus single-site endpoints in many cities. Private endpoints exist for in-cloud traffic.
Addressing: virtual-hosted.
Notes: IBM COS supports IAM API-key authentication in addition to HMAC access keys. Storage classes include Standard, Vault, Cold Vault, and Smart Tier^[5].

Oracle Cloud Infrastructure (OCI) Object Storage

Oracle Cloud Infrastructure Object Storage offers an Amazon S3 Compatibility API in front of its native object store.

Endpoint format: <namespace>.compat.objectstorage.<region>.oci.customer-oci.com for path-style, or <bucket>.vhcompat.objectstorage.<region>.oci.customer-oci.com for virtual-hosted. The <namespace> is your tenancy's unique Object Storage namespace.
Regions: Ashburn, Phoenix, Frankfurt, London, Tokyo, and the rest of OCI's global regions.
Addressing: both path and virtual-hosted are supported.
Notes: authenticate with a Customer Secret Key (an access key and secret pair). If your tool cannot set the region identifier, set it to us-east-1 or leave it blank to use your home region. SigV2 is not supported^[6].

Google Cloud Storage (XML / S3 Interoperability)

Google Cloud Storage is not S3 by default, but its XML API has an S3-compatible interoperability mode that works with HMAC keys.

Endpoint format: storage.googleapis.com.
Regions: global; the endpoint is single, and the bucket's location is set when you create it.
Addressing: virtual-hosted.
Notes: create an HMAC key for a service account to get an access key and secret. Object versioning listing and a few advanced behaviors differ from AWS, so treat GCS as S3-compatible for the common operations (browse, upload, download, copy) rather than a perfect clone^[7].

Yandex Object Storage

Yandex Cloud's object storage is S3-compatible and popular across Russia and the CIS.

Endpoint format: storage.yandexcloud.net.
Regions: ru-central1 and its availability zones; the endpoint is single.
Addressing: virtual-hosted.
Notes: Standard (hot) and Cold storage classes are available. Use static access keys generated for a service account^[8].

VK Cloud Object Storage (formerly Mail.ru Cloud Solutions)

VK Cloud, previously Mail.ru Cloud Solutions, runs Hotbox and Icebox object storage tiers behind an S3-compatible endpoint.

Endpoint format: hb.bizmrg.com (Hotbox) and ib.bizmrg.com (Icebox), with newer hb.<region>.vkcs.cloud hosts.
Regions: Moscow.
Addressing: virtual-hosted.
Notes: Hotbox is the hot tier, Icebox the cold tier. Confirm the current endpoint in the VK Cloud console.

Baidu AI Cloud BOS (Baidu Object Storage)

Baidu Object Storage provides an S3-compatible interface for one of China's major clouds.

Endpoint format: s3.<region>.bcebos.com (for example s3.bj.bcebos.com for Beijing, s3.gz.bcebos.com for Guangzhou).
Regions: Beijing, Baoding, Suzhou, Guangzhou, Hong Kong, and more.
Addressing: virtual-hosted.
Notes: Standard, Infrequent Access, Cold, and Archive tiers are available.

JD Cloud Object Storage (OSS)

JD Cloud, the cloud arm of JD.com, exposes an S3-compatible object storage service.

Endpoint format: s3.<region>.jdcloud-oss.com (for example s3.cn-north-1.jdcloud-oss.com).
Regions: North China, East China, and South China.
Addressing: virtual-hosted.
Notes: confirm the regional endpoint in the JD Cloud console.

China Mobile Ecloud EOS (Elastic Object Storage)

China Mobile's Ecloud Elastic Object Storage is a large, region-dense S3-compatible service across mainland China.

Endpoint format: eos-<city>-1.cmecloud.cn (for example eos-wuxi-1.cmecloud.cn, eos-beijing-1.cmecloud.cn).
Regions: dozens, from Suzhou and Shanghai to Chengdu, Guiyang, and Xian.
Addressing: virtual-hosted.
Notes: the location constraint must match the endpoint when creating buckets^[9].

Kingsoft Cloud KS3

Kingsoft Cloud Standard Storage Service (KS3) is an S3-compatible object store widely used in China.

Endpoint format: ks3-<region>.ksyuncloud.com or ks3-<region>.ksyun.com (for example ks3-cn-beijing.ksyuncloud.com).
Regions: Beijing, Shanghai, Guangzhou, Hong Kong, and international points.
Addressing: virtual-hosted.
Notes: confirm the current endpoint host in the Kingsoft console.

China Telecom CTYun OOS

China Telecom's CTYun (Tianyi Cloud) Object-Oriented Storage is an S3-compatible service across China Telecom's regions.

Endpoint format: oos-<region>.ctyunapi.cn (for example oos-sccd.ctyunapi.cn).
Regions: many across mainland China.
Addressing: virtual-hosted.
Notes: confirm the regional endpoint in the CTYun console.

NAVER Cloud Object Storage

NAVER Cloud Platform, South Korea's major cloud, runs an S3-compatible object storage service.

Endpoint format: <region>.object.ncloudstorage.com (for example kr.object.ncloudstorage.com).
Regions: Korea, plus other NAVER Cloud regions.
Addressing: virtual-hosted.
Notes: generate API keys in the NAVER Cloud console.

Open Telekom Cloud OBS

Open Telekom Cloud, operated by T-Systems on Huawei technology, exposes Huawei OBS under its own endpoints.

Endpoint format: obs.<region>.otc.t-systems.com (for example obs.eu-de.otc.t-systems.com).
Regions: Germany (Biere, Magdeburg), the Netherlands, and Switzerland.
Addressing: virtual-hosted.
Notes: the OBS lineage means it behaves like Huawei OBS, with European data residency.

SberCloud OBS

SberCloud Advanced (Cloud.ru) runs object storage on Huawei OBS technology with Russian endpoints.

Endpoint format: obs.<region>.hc.sbercloud.ru (for example obs.ru-moscow-1.hc.sbercloud.ru).
Regions: Moscow.
Addressing: virtual-hosted.
Notes: behaves like Huawei OBS with Russian data residency.

Netease NOS (Netease Object Storage)

Netease Object Storage offers an S3-compatible interface used by Netease's services and third parties.

Endpoint format: regional NOS endpoints (for example nos-eastchina1.126.net).
Regions: several across China.
Addressing: virtual-hosted (path-style addressing is disabled by the provider).
Notes: confirm the exact endpoint in the Netease console.

A Note on Microsoft Azure Blob Storage

Azure Blob Storage is the obvious omission here, and it is deliberate. Azure Blob uses its own API, not the S3 API, so it is not S3-compatible in the drop-in sense. The concepts line up (a container maps to a bucket, a blob to an object), but an S3 client cannot talk to Azure Blob without a translation gateway. If you need to move data between S3 and Azure, Blober bridges the two directly. See How to Transfer AWS S3 to Azure Blob.

Frequently Asked Questions

Is Google Cloud Storage S3-compatible? Through its XML API interoperability mode, yes, for the common operations. You create an HMAC key and point your S3 client at storage.googleapis.com. A few advanced behaviors differ from AWS S3.

Is Alibaba OSS the same as AWS S3? OSS speaks the S3 API, so S3 tools work against it by changing the endpoint and keys. It is run by Alibaba, not Amazon, and its tier names and some features are its own.

Why do Open Telekom Cloud and SberCloud look like Huawei OBS? Because they are built on Huawei OBS technology and rebranded for their regions. The S3-compatible connection pattern is the same, with different endpoints and data residency.

Can Blober move data from one cloud's object storage to another? Yes. Point Blober at a source endpoint and a destination endpoint and it copies between them directly for normal object transfers. Provider-specific S3 feature gaps can still matter for advanced workflows.

Get Blober

Connect to any cloud's S3-compatible object storage by URL and move data between providers directly, without filling your local disk.

Download Blober at blober.io

S3-Compatible Object Storage from Web Hosts and VPS Providers

Jun 28, 2026

If you already rent servers from a hosting or VPS company, there is a good chance they also sell S3-compatible object storage right next to your droplets, instances, or dedicated boxes. Keeping storage with your compute reduces latency and often avoids cross-provider egress. This page lists the hosting and VPS object-storage services, their endpoint formats, and how to connect each one.

This is one category in our complete list of S3-compatible storage providers. DigitalOcean Spaces has a preconfigured connector in Blober; the rest use the generic S3-Compatible connector. Confirm endpoints in each provider's console, since regions change over time. The endpoint formats below come from each provider's own documentation, cross-checked against current S3 client references^[1].

Each entry notes an addressing style. Virtual-hosted puts the bucket in the subdomain (https://my-bucket.s3.example.com); path-style puts it in the URL path (https://s3.example.com/my-bucket). Almost every host here uses virtual-hosted. The endpoint formats below show hostnames; in Blober, include https:// in the endpoint field. The endpoint setup notes explain how Blober picks the right one.

DigitalOcean Spaces

DigitalOcean Spaces is S3-compatible object storage with a built-in CDN, sold alongside DigitalOcean droplets.

Endpoint format: <region>.digitaloceanspaces.com (for example nyc3.digitaloceanspaces.com, fra1.digitaloceanspaces.com).
Regions: NYC3, SFO2, SFO3, AMS3, FRA1, SGP1, SYD1, BLR1, ATL1, LON1, TOR1, and more.
Addressing: virtual-hosted.
Notes: Blober has a preconfigured DigitalOcean Spaces connector. Spaces has no built-in cross-region replication; see DigitalOcean Spaces Regions, Replication, and Backup^[2].

Linode / Akamai Object Storage

Linode (now part of Akamai) offers S3-compatible object storage across many global regions.

Endpoint format: <region>.linodeobjects.com (for example us-east-1.linodeobjects.com, eu-central-1.linodeobjects.com).
Regions: Newark, Atlanta, Chicago, Los Angeles, Miami, Seattle, Washington DC, Amsterdam, Frankfurt, London, Madrid, Milan, Paris, Stockholm, Chennai, Jakarta, Osaka, Singapore, Sao Paulo, Melbourne.
Addressing: virtual-hosted.
Notes: one of the widest region footprints among VPS providers^[3].

Vultr Object Storage

Vultr Object Storage is S3-compatible storage with a CDN, billed with generous included transfer.

Endpoint format: <region>.vultrobjects.com (for example ewr1.vultrobjects.com, ams1.vultrobjects.com).
Regions: New Jersey, Silicon Valley, Amsterdam, Singapore, Bangalore, Delhi, and more.
Addressing: virtual-hosted.
Notes: includes an archival storage tier with lifecycle policies. Confirm the regional host in the Vultr console^[4].

OVHcloud Object Storage

OVHcloud offers S3-compatible object storage across its European, North American, and Asia-Pacific regions.

Endpoint format: s3.<region>.io.cloud.ovh.net (for example s3.gra.io.cloud.ovh.net for Gravelines, s3.de.io.cloud.ovh.net for Frankfurt). US regions use io.cloud.ovh.us.
Regions: Gravelines, Roubaix, Strasbourg, Paris, Frankfurt, London, Warsaw, Beauharnois, Toronto, Singapore, Sydney, Mumbai, plus US (Virginia, Oregon) and a cold archive region.
Addressing: virtual-hosted.
Notes: storage classes include Standard, High Performance, Standard Infrequent Access, and archive tiers^[5].

Hetzner Object Storage

Hetzner Object Storage is low-cost S3-compatible storage in Hetzner's European data centers.

Endpoint format: <region>.your-objectstorage.com (for example hel1.your-objectstorage.com, fsn1.your-objectstorage.com, nbg1.your-objectstorage.com).
Regions: Helsinki, Falkenstein, Nuremberg.
Addressing: virtual-hosted.
Notes: a popular budget option for European workloads^[6].

Scaleway Object Storage

Scaleway Object Storage is S3-compatible storage from the French cloud provider, with a Glacier cold tier.

Endpoint format: s3.<region>.scw.cloud (for example s3.nl-ams.scw.cloud, s3.fr-par.scw.cloud, s3.pl-waw.scw.cloud).
Regions: Amsterdam, Paris, Warsaw.
Addressing: virtual-hosted.
Notes: the GLACIER storage class uploads directly to Scaleway's cold tier; restore before reading^[7].

Contabo Object Storage

Contabo Object Storage is budget S3-compatible storage (built on Ceph) with included transfer.

Endpoint format: <region>.contabostorage.com (for example eu2.contabostorage.com, usc1.contabostorage.com, sin1.contabostorage.com).
Regions: Europe, United States, and Asia.
Addressing: virtual-hosted.
Notes: unlimited inbound and generous outbound transfer are included in the flat monthly rate. Confirm your exact endpoint in the Contabo console^[8].

Exoscale SOS (Simple Object Storage)

Exoscale Simple Object Storage is S3-compatible storage from the Swiss cloud provider, with European zones.

Endpoint format: sos-<zone>.exo.io (for example sos-ch-gva-2.exo.io, sos-de-fra-1.exo.io).
Regions: Geneva, Zurich, Frankfurt, Munich, Vienna, Sofia.
Addressing: virtual-hosted.
Notes: strong fit for Swiss and EU data residency^[9].

UpCloud Object Storage

UpCloud Object Storage is S3-compatible storage from the Finnish cloud provider.

Endpoint format: <region>.upcloudobjects.com (the exact host is shown in your console).
Regions: several across Europe, the US, and Asia-Pacific.
Addressing: virtual-hosted.
Notes: confirm the per-region endpoint host in the UpCloud control panel.

IONOS Cloud S3 Object Storage

IONOS S3 Object Storage is S3-compatible storage from the German provider IONOS.

Endpoint format: s3-<region>.ionoscloud.com (for example s3-eu-central-1.ionoscloud.com).
Regions: Frankfurt, Berlin, Logrono (Spain), Lenexa (USA).
Addressing: virtual-hosted.
Notes: generate keys in the Data Center Designer under the Object Storage Key Manager^[10].

Gcore Object Storage

Gcore Object Storage is S3-compatible storage from Gcore, with a wide global edge footprint.

Endpoint format: regional S3 endpoint shown in the Gcore console (for example a s3.<region> style host).
Regions: many across Europe, the Americas, Asia, and the Middle East.
Addressing: virtual-hosted.
Notes: confirm the current endpoint host for your region in the Gcore console.

DreamHost DreamObjects

DreamObjects is DreamHost's S3-compatible object storage, built on Ceph.

Endpoint format: objects-<region>.dream.io (for example objects-us-east-1.dream.io).
Regions: US.
Addressing: virtual-hosted.
Notes: leave the region blank and set the endpoint, as with other Ceph-based services^[11].

RackCorp Object Storage

RackCorp Object Storage is an S3-compatible platform with anycast and many regional endpoints.

Endpoint format: <region>.s3.rackcorp.com (for example au-nsw.s3.rackcorp.com), or s3.rackcorp.com for the global anycast endpoint.
Regions: Australia (several), plus Asia, Europe, North America, and New Zealand.
Addressing: virtual-hosted.
Notes: useful where other providers lack a nearby region^[12].

cloudscale.ch

cloudscale.ch is a Swiss provider with S3-compatible object storage and strong data-residency guarantees.

Endpoint format: objects.<region>.cloudscale.ch (for example objects.rma.cloudscale.ch, objects.lpg.cloudscale.ch).
Regions: Rumlang and Lupfig, Switzerland.
Addressing: virtual-hosted.
Notes: all data stays in Switzerland^[13].

Fuga Cloud Object Store

Fuga Cloud is a European OpenStack-based provider with an S3-compatible object store.

Endpoint format: core.fuga.cloud.
Regions: the Netherlands.
Addressing: virtual-hosted.
Notes: confirm the endpoint and any newer hosts in the Fuga console.

Infomaniak Public Cloud

Infomaniak, a Swiss provider, offers S3-compatible object storage on its OpenStack-based Public Cloud.

Endpoint format: s3.<region>.infomaniak.cloud (for example s3.pub1.infomaniak.cloud).
Regions: Switzerland.
Addressing: virtual-hosted.
Notes: Swiss data residency and renewable-energy hosting.

Outscale OOS (Object Storage)

OUTSCALE, a Dassault Systemes brand, offers enterprise-grade S3-compatible object storage.

Endpoint format: oos.<region>.outscale.com (for example oos.eu-west-2.outscale.com).
Regions: Paris, New Jersey, California, SecNumCloud (Paris), Tokyo.
Addressing: virtual-hosted.
Notes: includes a SecNumCloud-qualified region for sensitive French workloads^[14].

Liara Object Storage

Liara is an Iranian platform with S3-compatible object storage.

Endpoint format: storage.iran.liara.space.
Regions: Iran.
Addressing: virtual-hosted.
Notes: leave the region blank and set the endpoint^[15].

ArvanCloud Object Storage

ArvanCloud offers S3-compatible object storage with regions in Iran.

Endpoint format: s3.<region>.arvanstorage.ir (for example s3.ir-thr-at1.arvanstorage.ir), also seen as s3.arvanstorage.com.
Regions: Tehran, Tabriz.
Addressing: virtual-hosted.
Notes: confirm the current endpoint host in the ArvanCloud console^[16].

BizflyCloud Simple Storage

Bizfly Cloud Simple Storage is an S3-compatible service with regions in Vietnam.

Endpoint format: <region>.ss.bfcplatform.vn (hn.ss.bfcplatform.vn for Hanoi, hcm.ss.bfcplatform.vn for Ho Chi Minh City).
Regions: Hanoi, Ho Chi Minh City.
Addressing: virtual-hosted.
Notes: match the region to the endpoint^[17].

Selectel and Servercore Object Storage

Selectel and its international brand Servercore offer S3-compatible object storage with triple-redundant storage.

Endpoint format: s3.<region>.storage.selcloud.ru (for example s3.ru-1.storage.selcloud.ru), plus s3.<region>.srvstorage.uz and s3.<region>.srvstorage.kz for Servercore in Central Asia.
Regions: St. Petersburg, Moscow, Kazakhstan, Uzbekistan.
Addressing: virtual-hosted (the provider recommends vHosted, not path-style).
Notes: confirm the endpoint for your region in the console^[18].

Fastly Object Storage

Fastly Object Storage is S3-compatible storage from the edge-cloud provider Fastly, with mandatory server-side encryption.

Endpoint format: <region>.object.fastlystorage.app (for example us-east.object.fastlystorage.app).
Regions: US East, US West, US Central, EU Central, EU South, EU West, UK East, JP Central, AU East.
Addressing: virtual-hosted.
Notes: server-side encryption is always on^[19].

Leaseweb Object Storage

Leaseweb offers S3-compatible object storage alongside its dedicated and cloud hosting.

Endpoint format: the regional S3 endpoint shown in the Leaseweb customer portal.
Regions: Europe, the US, and Asia-Pacific.
Addressing: virtual-hosted.
Notes: confirm the exact endpoint host in the Leaseweb portal.

Frequently Asked Questions

Why use a host's object storage instead of a specialist? Keeping storage with your compute reduces latency and often avoids cross-provider egress charges. If you already run servers at OVHcloud, Hetzner, or Vultr, their object storage is the path of least resistance.

Do these all use the AWS S3 API? Yes. Every provider here exposes an S3-compatible endpoint, so the same S3 tools and SDKs work by changing the endpoint and keys.

Can I move data from DigitalOcean Spaces to another host's object storage? Yes. Blober copies directly between S3 endpoints that support the normal object operations it uses. Set the source and destination and it transfers without staging a full copy on your disk.

Which of these connect to Blober without setup? DigitalOcean Spaces has a preconfigured connector. Every other provider on this page uses the generic S3-Compatible connector: paste the endpoint and keys.

Get Blober

Connect to any host's S3-compatible object storage by URL and move data between providers directly, without filling your local disk.

Download Blober at blober.io

S3-Compatible Storage Providers: The Complete List (90+ Providers)

Jun 28, 2026

This is a practical list of well-known S3-compatible storage providers. If a service speaks the Amazon S3 API, the same tools, SDKs, and apps that work with AWS S3 usually work with it by changing two things: the endpoint URL and the access keys. That portability is why so many S3-compatible services exist, from global clouds to storage you run on your own hardware.

We have grouped them into six categories so the list stays usable. Each provider below links to a detailed entry with its endpoint format, regions, addressing style, and notes. Whatever S3-compatible store you are searching for, there is a good chance it is on this page.

Every endpoint format here comes from the provider's own documentation, cross-checked against current S3 client references and the per-provider sources in the category pages^[1]. The tables show endpoint hostnames for readability. In Blober, enter the full URL with https:// unless you are connecting to a local/self-hosted server that explicitly uses http://.

What S3-Compatible Means Here

S3-compatible means the service exposes the same HTTP API as Amazon S3, so an S3 client points at it by URL. It does not mean the service is run by Amazon, and it does not promise every advanced feature is identical. For the full explanation, see What S3-Compatible Really Means.

For common S3 operations, the custom endpoint is the portability layer. Once your tool can set that endpoint, the provider becomes much easier to swap.

How Blober Connects to Any of These

Blober has preconfigured connectors for the most common S3 services (Amazon S3, Wasabi, Cloudflare R2, Backblaze B2, DigitalOcean Spaces, and Rabata). For everything else on this list, Blober has a single generic S3-Compatible connector: you paste the endpoint URL and keys, and Blober can use the common browse, upload, download, copy, and delete operations when the provider implements them.

That connector covers both addressing styles (bucket in the subdomain, or bucket in the path), single-bucket or full-account access, a custom region, and a free-text storage class, so it reaches the long tail of providers, self-hosted servers, and local test setups. You point Blober at a source and a destination and it copies between them directly, without staging a full copy on your disk.

The Six Categories

Category	What is in it	Open the list
Cloud object storage	S3 services from large platform clouds (Alibaba, Tencent, Huawei, IBM, Oracle, Google, Yandex, and more)	Cloud providers
Object storage specialists	Independent clouds built only for object storage (Wasabi, Backblaze, Storj, IDrive e2, Cubbit, and more)	Specialists
Hosting and VPS object storage	S3 storage bundled with a hosting or VPS platform (DigitalOcean, Linode, Vultr, OVHcloud, Hetzner, Scaleway, and more)	Hosting and VPS
Self-hosted and open source	S3 servers you run yourself (MinIO, Ceph, SeaweedFS, Garage, and more)	Self-hosted
Enterprise and on-premises	Appliances and enterprise platforms (NetApp StorageGRID, Dell ECS, Cloudian, Pure FlashBlade, and more)	Enterprise
Decentralized and Web3	Object storage backed by decentralized networks (Storj, Filebase, 4everland, and more)	Decentralized

Master Index of S3-Compatible Providers

Every provider, alphabetical, with its endpoint format. The endpoint is the host you give your S3 client; the bucket name is then added either as a subdomain or in the path. Replace any bracketed value (<region>, <account>, <namespace>) with your own. A check in the last column means Blober ships a preconfigured connector; everything else uses the generic S3-Compatible connector. When you enter one of these in Blober, include the URL scheme, for example https://s3.example.com.

Provider	Endpoint format	Preconfigured
Alibaba Cloud OSS	`oss-<region>.aliyuncs.com`
Amazon S3	`s3.<region>.amazonaws.com`	Yes
Apache Ozone	self-hosted S3 Gateway
ArvanCloud	`s3.<region>.arvanstorage.ir`
Backblaze B2	`s3.<region>.backblazeb2.com`	Yes
Baidu AI Cloud BOS	`s3.<region>.bcebos.com`
BizflyCloud	`<region>.ss.bfcplatform.vn`
Ceph (RADOS Gateway)	self-hosted
China Mobile Ecloud EOS	`eos-<city>-1.cmecloud.cn`
China Telecom CTYun OOS	`oos-<region>.ctyunapi.cn`
Cloudflare R2	`<account>.r2.cloudflarestorage.com`	Yes
Cloudian HyperStore	appliance or software
cloudscale.ch	`objects.<region>.cloudscale.ch`
Contabo Object Storage	`<region>.contabostorage.com`
Cubbit DS3	`s3.cubbit.eu`
DataCore Swarm	on-premises
Dell ECS / ObjectScale	on-premises
DigitalOcean Spaces	`<region>.digitaloceanspaces.com`	Yes
DreamHost DreamObjects	`objects-<region>.dream.io`
Exaba	self-hosted
Exoscale SOS	`sos-<zone>.exo.io`
Fastly Object Storage	`<region>.object.fastlystorage.app`
FileLu S5	`s5lu.com`
Filebase	`s3.filebase.io`
4everland	`endpoint.4everland.co`
Fuga Cloud Object Store	`core.fuga.cloud`
Garage	self-hosted
Gcore Object Storage	regional endpoint
Google Cloud Storage	`storage.googleapis.com`
Hitachi Content Platform	on-premises
Hetzner Object Storage	`<region>.your-objectstorage.com`
Huawei Cloud OBS	`obs.<region>.myhuaweicloud.com`
IBM Cloud Object Storage	`s3.<region>.cloud-object-storage.appdomain.cloud`
IDrive e2	`<region>.idrivee2-XX.com`
Impossible Cloud	`<region>.storage.impossibleapi.net`
Infomaniak Public Cloud	`s3.<region>.infomaniak.cloud`
Intercolo Object Storage	`de-fra.i3storage.com`
IONOS Cloud S3	`s3-<region>.ionoscloud.com`
JD Cloud Object Storage	`s3.<region>.jdcloud-oss.com`
Kingsoft Cloud KS3	`ks3-<region>.ksyuncloud.com`
Leaseweb Object Storage	regional endpoint
Leviia	`s3.leviia.com`
Liara	`storage.iran.liara.space`
Linode / Akamai	`<region>.linodeobjects.com`
MEGA S4	`s3.<region>.s4.mega.io`
MinIO	self-hosted
NAVER Cloud Object Storage	`<region>.object.ncloudstorage.com`
NetApp StorageGRID	on-premises
NetApp ONTAP S3	on-premises
Netease NOS	`nos-<region>.126.net`
Nutanix Objects	on-premises
OpenIO	self-hosted
OpenStack Swift (s3api)	self-hosted
Open Telekom Cloud OBS	`obs.<region>.otc.t-systems.com`
Oracle Cloud OCI	`<namespace>.compat.objectstorage.<region>.oci.customer-oci.com`
Outscale OOS	`oos.<region>.outscale.com`
OVHcloud Object Storage	`s3.<region>.io.cloud.ovh.net`
Petabox	`s3.<region>.petabox.io`
Pure Storage FlashBlade	on-premises
Qiniu Kodo	`s3-<region>.qiniucs.com`
Quantum ActiveScale	on-premises
Rabata	`s3.<region>.rabata.io`	Yes
RackCorp	`<region>.s3.rackcorp.com`
Riak CS	self-hosted
Scality RING / ARTESCA	on-premises
Scaleway Object Storage	`s3.<region>.scw.cloud`
Seagate Lyve Cloud	`s3.<region>.<account>.lyve.seagate.com`
SeaweedFS	self-hosted
Selectel	`s3.<region>.storage.selcloud.ru`
Servercore	`s3.<region>.storage.selcloud.ru`
SberCloud OBS	`obs.<region>.hc.sbercloud.ru`
Spectra Logic BlackPearl	on-premises
Storadera	`<region>.s3.storadera.com`
Storj	`gateway.storjshare.io`
Synology C2	`<region>.s3.synologyc2.net`
Tebi	`s3.tebi.io`
Telnyx Cloud Storage	`<region>.telnyxcloudstorage.com`
Tencent Cloud COS	`cos.<region>.myqcloud.com`
Tigris	`t3.storage.dev`
UpCloud Object Storage	`<region>.upcloudobjects.com`
US3 (UCloud)	`s3-<region>.ufileos.com`
VAST Data	on-premises
Versity Gateway	self-hosted
VK Cloud Object Storage	`hb.bizmrg.com`
Vultr Object Storage	`<region>.vultrobjects.com`
Wasabi	`s3.<region>.wasabisys.com`	Yes
Yandex Object Storage	`storage.yandexcloud.net`
Zadara	`<vsa-id>.zadarazios.com`
Zata	`idr01.zata.ai`

This index is a starting point. Providers add regions and change hostnames over time, so always confirm the exact endpoint in your provider's console before you connect. The detailed group articles explain each provider's regions, addressing style (path or subdomain), and any quirks.

Subdomain vs Path: The One Setting That Trips People Up

S3 supports two ways of putting the bucket name into the request:

Virtual-hosted (bucket in the subdomain): https://my-bucket.s3.example.com. This is the AWS default and what most hosted providers expect.
Path-style (bucket in the path): https://s3.example.com/my-bucket. This is what MinIO, Ceph, and most self-hosted servers expect.

If browsing or uploads fail against a self-hosted server, switch to path-style. In Blober, you pick the style implicitly by which endpoint field you fill in. Everything else is the same.

Frequently Asked Questions

How many S3-compatible storage providers are there? There is no official registry. This page indexes more than ninety well-known hosted providers, hosting platforms, self-hosted servers, enterprise systems, and decentralized gateways across six categories.

Is Azure Blob Storage S3-compatible? Not natively. Azure Blob uses its own API. The concepts map across (a container is like a bucket, a blob like an object), but an S3 tool needs a translation layer to talk to it. See How to Transfer AWS S3 to Azure Blob for moving data between the two.

Can I move data between two different S3-compatible providers? Yes. Because they share the core API, moving between them is usually a straightforward copy. Blober connects to a source and a destination and transfers directly between them. Check provider-specific feature gaps if your workflow depends on object lock, lifecycle, metadata edge cases, or server-side copy.

Do I need a preconfigured connector, or does the generic one work? The generic S3-Compatible connector works with S3-compatible endpoints that support the common operations Blober uses. The preconfigured connectors (S3, Wasabi, R2, B2, Spaces, Rabata) just save you from pasting the endpoint.

Which S3-compatible provider is the cheapest? It depends on your access pattern. Flat-rate, zero-egress providers win for data you read often; the lowest per-GB storage rate wins for cold archives. The pricing model (egress fees and minimum storage duration) usually matters more than the headline storage rate.

Get Blober

Connect to S3-compatible stores on this list and move data between them directly, without filling your local disk. Blober handles S3, Wasabi, R2, B2, Spaces, Rabata, and generic S3 endpoints by URL, plus non-S3 services like Azure Blob, Dropbox, and Google Drive.

Download Blober at blober.io

Self-Hosted and Open-Source S3-Compatible Storage (MinIO, Ceph, and More)

Jun 28, 2026

You do not need a cloud account to get an S3 endpoint. A whole category of open-source software gives you S3-compatible storage on your own hardware, in your own data center, or on a laptop for testing. These servers expose the same core S3 object-storage API shape as AWS, so the same tools can point at http://localhost:9000 as easily as at a cloud. This page lists the self-hosted and open-source S3 servers and how to connect each one.

This is one category in our complete list of S3-compatible storage providers. All of these connect to Blober through the generic S3-Compatible connector. Self-hosted servers almost always want path-style addressing (bucket in the path), so use the path endpoint field in Blober if browsing or uploads fail. The endpoint and compatibility notes below come from each project's own documentation, cross-checked against current S3 client references^[1]. The endpoint setup notes explain the difference between path-style and virtual-hosted addressing.

MinIO

MinIO is the most widely deployed self-hosted S3 server: a single Go binary that exposes an S3-compatible API, used for everything from local testing to large production clusters.

Endpoint format: http://<host>:9000 (for example http://localhost:9000).
Addressing: path-style.
Notes: for a quick local test, the default keys are often minioadmin / minioadmin. MinIO is also the reference target for "does this tool support custom S3 endpoints," and it is a common front end for other storage backends^[2].

Ceph (RADOS Gateway / RGW)

Ceph is an open-source distributed storage system; its RADOS Gateway (RGW) exposes an S3-compatible object interface on top of a Ceph cluster.

Endpoint format: https://<your-rgw-host> (your own gateway address).
Addressing: path-style is the safe default.
Notes: Ceph powers many commercial object stores (DreamObjects and Contabo among them). Leave the region blank and set the endpoint. Older Ceph (pre-Jewel) may need v2 signatures^[3].

SeaweedFS

SeaweedFS is a fast distributed storage system for blobs and files, with an S3-compatible gateway. It can also cache a remote S3 store with asynchronous write-back.

Endpoint format: http://<host>:8333 (for example http://localhost:8333).
Addressing: path-style.
Notes: lightweight and quick to stand up; good for edge and on-prem caching in front of a remote bucket^[4].

Garage

Garage, from Deuxfleurs, is a lightweight, self-hosted S3-compatible object store designed for geo-distributed deployments on modest hardware.

Endpoint format: http://<your-garage-host>:3900 (your own configured address).
Addressing: path-style.
Notes: built for resilience across home-server-grade nodes; a popular choice for self-hosters and small co-ops^[5].

Zenko CloudServer

Zenko CloudServer (formerly Scality S3 Server) is an open-source Node.js S3 server that can store locally or proxy to cloud backends.

Endpoint format: http://<host>:8000 (your own configured address).
Addressing: path-style.
Notes: part of the wider Zenko project, which targets multi-cloud data management with an S3 front end^[6].

Versity Gateway (VersityGW)

Versity Gateway is an open-source S3 gateway with pluggable backends, letting you put an S3 API in front of a POSIX file system or other stores.

Endpoint format: http://<your-gateway-host>:7070 (your own configured address).
Addressing: path-style.
Notes: useful for exposing existing file storage (including tape-backed archives) over S3^[7].

s3proxy

s3proxy is an open-source proxy that presents an S3 API backed by a local file system or by other cloud stores, including Azure Blob and Google Cloud Storage.

Endpoint format: http://<your-proxy-host>:80 (your own configured address).
Addressing: path-style.
Notes: a common way to give non-S3 backends an S3 face. If you specifically need S3 in front of Azure, this is one of the standard tools^[8].

Apache Ozone

Apache Ozone is a distributed object store for big-data and Kubernetes workloads, with an S3 Gateway component.

Endpoint format: the S3 Gateway address you deploy (commonly port 9878).
Addressing: path-style.
Notes: designed to scale to billions of objects alongside Hadoop and Spark^[9].

OpenStack Swift (with the s3api middleware)

OpenStack Swift is the object storage component of OpenStack. With the s3api middleware enabled, it accepts S3 API calls in addition to its native Swift API.

Endpoint format: your Swift proxy address with s3api enabled (your own deployment).
Addressing: path-style.
Notes: many regional and academic clouds run Swift; if yours has s3api turned on, you can connect over S3^[10].

OpenIO

OpenIO is an open-source object storage platform (now part of OVHcloud) with an S3-compatible gateway.

Endpoint format: your OpenIO S3 gateway address (your own deployment).
Addressing: path-style.
Notes: designed for grid-style scaling on heterogeneous hardware^[11].

LeoFS

LeoFS is an open-source distributed object store with an S3-compatible interface.

Endpoint format: your LeoFS gateway address (your own deployment).
Addressing: path-style.
Notes: confirm the gateway endpoint and credentials from your LeoFS configuration^[12].

Riak CS

Riak CS (Cloud Storage) layers S3-compatible object storage on top of a Riak key-value cluster.

Endpoint format: your Riak CS proxy address (your own deployment).
Addressing: path-style.
Notes: suited to multi-tenant, highly available deployments^[13].

Rclone Serve S3

Rclone can serve any of its remotes over the S3 protocol with rclone serve s3, turning anything rclone supports into a temporary S3 endpoint.

Endpoint format: http://<host>:8080 (your own configured address).
Addressing: path-style.
Notes: handy for bridging an odd backend to S3 tools for a one-off transfer^[14].

Exaba

Exaba is an on-premises, S3-compatible storage server for service providers and enterprises, with a free container edition.

Endpoint format: http://<host>:9000 (your own configured address; the admin runs on a separate port).
Addressing: path-style.
Notes: set up the container through the admin interface first, then use the S3 service port^[15].

A Note on Gateways: S3 in Front of Something Else

Several tools here (s3proxy, Versity Gateway, Zenko, MinIO, and SeaweedFS) can act as gateways: they present an S3 API in front of a different backend, such as a local file system, tape, or even a non-S3 cloud like Azure Blob. If your goal is to make a non-S3 store look like S3, a gateway is the usual answer. If your goal is simply to move data between an S3 store and a non-S3 store, Blober already bridges S3, Azure Blob, Dropbox, Google Drive, and more directly, with no gateway to run.

Frequently Asked Questions

Which self-hosted S3 server should I start with? MinIO, for most people. It is a single binary, well documented, and the de facto standard for a local or on-prem S3 endpoint. Ceph RGW suits larger clusters; Garage and SeaweedFS suit lightweight or distributed setups.

Why do uploads fail against my self-hosted server? Almost always because the tool is using virtual-hosted (subdomain) addressing. Self-hosted servers want path-style. In Blober, use the path endpoint field, for example http://localhost:9000.

Can Blober connect to a server on my own machine? Yes. Point it at http://localhost:9000 (or your server's address) with path-style addressing and your keys, and browse to confirm.

Can I put an S3 API in front of Azure or Google Drive? You can with a gateway like s3proxy. But to just move data between those services and an S3 store, Blober connects to each one natively, so you do not need a gateway.

Get Blober

Connect Blober to MinIO, Ceph, SeaweedFS, Garage, or any self-hosted S3 server by URL, and move data between your own storage and the cloud directly, without filling your local disk.

Download Blober at blober.io

Archiving Large Research and Scientific Datasets Across Clouds

Jun 24, 2026

The Shape of Research Data

Research datasets are large, occasionally needed years later, and often spread across storage paid for by different grants or collaborators. Archiving them well means picking durable storage, moving the data without a scripting project, and using transfers that resume when a multi-day run gets interrupted.

Anyone who has managed a lab's data knows the pattern. A dataset lives on a cluster's object store, a copy sits in a collaborator's account, and the grant that funded the original storage is ending. The data has to move, it is enormous, and nobody wants to own the migration.

Choose Storage That Suits an Archive

Active analysis and long-term archive have different needs. For the archive, the priorities are durability and a cost model that fits data you read back rarely:

Object storage such as Backblaze B2, Wasabi, or Cloudflare R2 is built for exactly this: large objects, high durability, S3-compatible so your existing tools work.
Compare on egress and minimum storage duration, not the headline rate. For an archive you touch a few times a year, those terms decide the real cost far more than the storage price.
Keep a second copy. A single archive is one copy. Durable does not mean infallible, and a second location is what the 3-2-1 rule is for.

Moving the Data Without a Scripting Project

The usual options at this scale are command-line tools and custom scripts, which is fine if you have an engineer to spare and a problem when you do not. The bottleneck is rarely the copy itself. It is listing millions of small files, keeping throughput up with parallelism, and resuming cleanly when a run that takes days gets interrupted.

Blober handles those parts from a desktop app. It connects to S3, B2, Wasabi, R2, DigitalOcean Spaces, Azure Blob, and local storage, copies between them directly without staging a full copy on disk, runs transfers in parallel, and has skip-existing so a paused or failed run picks up where it left off instead of starting over. For a dataset larger than any one machine's disk, that combination is the difference between a finished archive and an abandoned one.

Document What You Moved

An archive nobody can navigate is only half useful. As you move data, keep a simple record: what went where, when, and the rough file count, so a future you or a future student can find a dataset without reverse-engineering the folder tree. A short README in the destination bucket pays for itself the first time someone needs the data after you have moved on.

Frequently Asked Questions

Where should I archive large research datasets? Durable object storage such as Backblaze B2, Wasabi, or Cloudflare R2, chosen on egress and minimum storage duration rather than the headline rate, with a second copy in another location.

How do I move a multi-terabyte dataset between clouds? Use a tool that transfers directly, runs in parallel, and resumes. Blober copies between object stores and local storage from a desktop app, with skip-existing so interrupted runs continue rather than restart.

What makes large transfers fail? At scale, listing millions of small files and surviving interruptions are the hard parts, not the copy. Parallelism and resumable, skip-existing transfers are what get a multi-day run to finish.

Is object storage good for research archives? Yes. It is durable, built for large objects, and usually S3-compatible, so existing tools work. Keep a second copy elsewhere to satisfy 3-2-1.

Get Blober

Move multi-terabyte datasets between object stores and local storage without a scripting project. Blober transfers in parallel, preserves structure, and resumes interrupted runs.

Download Blober at blober.io

Cloudflare R2 for AI Training Data: Why Zero Egress Changes the Math

Jun 24, 2026

Why Egress Is the Hidden Tax on Training Data

Training a model means reading the same dataset over and over, once per epoch, often from GPUs that sit outside your storage provider's network. On most object stores you pay an egress fee every time that data leaves the bucket. Cloudflare R2 does not charge egress fees, so reading a dataset a hundred times costs the same in transfer as reading it once. For read-heavy AI work, that quietly changes the math.

People size storage by the price per terabyte and then get surprised by the transfer line on the bill. For an archive you rarely open, egress barely matters. For a training set you stream through a data loader thousands of times, egress is the cost.

What Makes Training Data Different From an Archive

Training data has a few traits that make egress the deciding factor:

It is read many times. Every epoch reads the whole set again. Hyperparameter sweeps and multiple runs multiply that.
It is large. Image, video, audio, and text corpora run to terabytes, and embeddings pile on more.
The compute is often elsewhere. GPUs in another cloud or a rented cluster mean the data crosses a network boundary on every read, which is exactly what egress charges for.

Put those together and a metered-egress store can cost more to read than to hold.

Why R2 Fits the Job

Two properties do the work. First, R2 does not charge egress fees, so repeated reads from outside Cloudflare do not accumulate transfer cost. Second, R2 is S3-compatible, so the data loaders, SDKs, and tools your pipeline already uses point at it by changing the endpoint and the keys. You do not rewrite your training code to adopt it.

A couple of honest caveats, because the math is not free in every direction. R2 has its own operation and request considerations, and throughput depends on how your loader and network are set up. If your training compute lives in the same cloud as your current data, reads inside that cloud may already avoid egress, so R2's advantage is largest when storage and compute would otherwise sit on different networks. Confirm Cloudflare's current terms before you commit a pipeline to them.

Getting a Dataset Into R2

A training corpus rarely starts life in one place. It is scraped to a local disk, staged in an S3 bucket, or scattered across a few accounts from different collaborators. Consolidating it into one R2 bucket is the setup step.

Blober moves data into R2 directly from AWS S3, Backblaze B2, Wasabi, DigitalOcean Spaces, Azure Blob, Dropbox, Google Drive, or local storage. It copies in parallel, keeps the folder structure intact, and has skip-existing, so the first run stages the whole corpus and later runs only carry the new files as the dataset grows. You are not downloading the set to a laptop and pushing it back up, which matters when the corpus is bigger than any one machine's disk.

A Practical Setup

Choose R2 as the dataset home if your training compute reads it repeatedly from outside Cloudflare.
Stage the corpus into an R2 bucket with Blober, in parallel and with structure preserved.
Point your S3-compatible data loader at the R2 endpoint and train.
Re-run Blober with skip-existing as you add data, so only the new files move.

Keep a second copy somewhere else as well. One bucket is one copy, and the 3-2-1 rule applies to a dataset you cannot easily recreate just as much as to family photos.

Frequently Asked Questions

Does Cloudflare R2 charge egress fees? No. R2 does not charge egress fees for reading your data out, which is its main draw for read-heavy workloads like model training. Confirm the current terms on Cloudflare's site before committing.

Is Cloudflare R2 good for machine learning datasets? Yes, especially when your training compute reads the dataset repeatedly from outside Cloudflare's network. Zero egress removes the per-read transfer cost that dominates training storage bills.

Is R2 S3-compatible for data loaders? Yes. R2 exposes an S3-compatible API, so existing S3 data loaders, SDKs, and tools work by changing the endpoint and credentials.

How do I move my training data into R2? Use a tool that transfers directly and in parallel. Blober stages datasets into R2 from S3, B2, Wasabi, Spaces, Azure Blob, and local storage, with skip-existing for incremental updates.

Get Blober

Stage your training data into R2 without a scripting project. Blober moves datasets into R2 from S3, B2, Wasabi, Spaces, Azure Blob, and local storage, in parallel and with structure intact.

Download Blober at blober.io

What S3-Compatible Really Means (and Why It Matters When You Switch)

Jun 24, 2026

What "S3-Compatible" Actually Means

S3-compatible means a storage service speaks the same API language as Amazon S3. Tools, SDKs, and apps built for S3 can usually work with it for common object operations by changing endpoint and credentials. It does not mean the service is run by Amazon, and it does not promise every feature is identical.

The S3 API became a de facto standard. Once enough tools spoke it, new providers had a choice: invent their own interface and ask everyone to re-tool, or speak S3 and work on day one with the entire existing ecosystem. Most chose S3.

The API Is the Standard, Not the Company

Think of it like a power socket. The plug shape is the standard, and a device built for that plug can draw power without caring which utility generated the electricity. S3 compatibility is the plug shape for object storage. Backblaze B2, Wasabi, Cloudflare R2, and DigitalOcean Spaces all expose an S3-compatible endpoint, so tools such as aws s3, rclone, and desktop transfer apps can point at them by changing the endpoint and the keys.

Why It Matters When You Switch

The real value of S3 compatibility is that it makes providers more swappable. If your app reads and writes through the common S3 operations, moving from one S3-compatible store to another is mostly a matter of changing the endpoint and the credentials, not rewriting code. That keeps you from being locked in by your tooling, and it means a provider's pricing model or a new egress policy does not trap your data with them.

What Compatibility Does Not Guarantee

Compatible is not identical. A few things still vary between S3-compatible providers, so check them before you commit:

Feature coverage. Lifecycle rules, versioning, object lock, and multipart limits differ. Most common operations are covered; the long tail is not always.
Performance and consistency. Throughput, latency, and edge-case consistency behavior are the provider's own.
Regions and durability. Where your data physically sits, and how many copies are kept, is a provider decision.
The pricing model. Egress and minimum storage duration are where S3-compatible providers differ most, and those terms decide the real cost of an archive far more than the headline storage rate.

A Note on Azure Blob

Azure Blob Storage uses its own API rather than the S3 API, so it is not S3-compatible in the same drop-in way. The concepts line up (an S3 bucket maps to a container, an object to a blob), but a tool pointed at S3 will not talk to Azure Blob without a translation layer. That is worth knowing if your stack assumes S3 everywhere.

When you do need S3-compatible applications to run against Azure, an S3 gateway sits in front of Azure Blob and converts S3 API calls to Azure Blob calls on the fly:

Flexify.IO runs an S3 gateway in front of Azure Blob Storage^[source].
s3proxy is an open-source proxy that presents an S3 API backed by Azure Blob and other stores^[source].
VersityGW is an open-source S3 gateway with pluggable backends^[source].
MinIO is S3-compatible storage that has been used to put an S3 API in front of other backends^[source].

For .NET projects, FluentStorage takes a different route. Rather than a gateway, it is a polymorphic cloud storage abstraction layer, so one codebase targets S3, Azure Blob, and other stores without per-provider code^[source].

Moving Between S3-Compatible Stores

Because the core API is shared, moving data between S3-compatible providers is usually straightforward. Blober connects to S3, Backblaze B2, Wasabi, Cloudflare R2, and DigitalOcean Spaces, and its generic S3 connector points at other S3-compatible endpoints by URL when they support the common operations Blober uses. It also bridges to non-S3 services like Azure Blob, Dropbox, and Google Drive. You point it at a source and a destination and it copies between them directly, without staging a full copy on your disk.

There are dozens of well-known S3-compatible services, plus self-hosted servers and enterprise systems you can run yourself. For a practical roster with endpoints and setup, see The Complete List of S3-Compatible Storage Providers.

Frequently Asked Questions

Is Backblaze B2 S3-compatible? Yes. B2 exposes an S3-compatible API, so S3 tools and SDKs work against it by changing the endpoint and keys.

Is Azure Blob Storage S3-compatible? Not natively. Azure Blob uses its own API. The concepts map across (container for bucket, blob for object), but S3 tools need a translation layer to talk to it.

Does S3-compatible mean exactly the same as AWS S3? No. It means the same API language. Features like lifecycle rules and versioning, plus performance, regions, and the pricing model, vary by provider.

Can I switch S3-compatible providers without changing my app? Usually yes, if your app uses the S3 API. You change the endpoint and credentials. Check that the specific features you rely on are supported by the new provider first.

Get Blober

Switch object-storage providers without the re-tooling headache. Blober moves data between S3, B2, Wasabi, R2, Spaces, and more, directly and without filling your local disk.

Download Blober at blober.io

DigitalOcean Spaces: Regions, Cross-Region Replication, and Backup

Jun 9, 2026

Spaces Regions and the Replication Question

The problem: people assume DigitalOcean Spaces replicates across regions the way Amazon S3 can, so a single Space feels like a backup. It is not. A Space lives in one region, and DigitalOcean does not copy it to another region for you.

The short answer: pick the region closest to your users when you create a Space, and if you want a second copy in another region or another provider, you have to make it yourself. This page lists the regions, explains what Spaces does and does not replicate, and shows how to create a real backup copy.

DigitalOcean Spaces Regions

Each Space is tied to one datacenter region, chosen at creation and fixed afterward. The current Spaces regions and their locations:

Region code	Location
NYC3	New York City, United States
SFO3	San Francisco, United States
AMS3	Amsterdam, Netherlands
FRA1	Frankfurt, Germany
SGP1	Singapore
SYD1	Sydney, Australia
BLR1	Bangalore, India

DigitalOcean adds regions over time, so check their documentation for the latest availability. The practical rule is unchanged: choose the region nearest the people who read the data most, because a Space only serves from its own region's endpoint.

Does DigitalOcean Spaces Do Cross-Region Replication?

No. DigitalOcean Spaces does not offer built-in cross-region replication. There is no setting that mirrors a Space in NYC3 to a Space in FRA1, and no automatic failover to another region.

This is the main difference from Amazon S3, which has Cross-Region Replication (CRR) as a bucket feature. On Spaces, if you want the same objects in two regions, you copy them there yourself and keep them in sync by re-copying when things change.

A few consequences worth knowing:

A region outage affects a single Space directly. With no replica, you cannot fail over to another region automatically.
Compliance or latency in a second geography means creating a second Space and populating it yourself.
There is no native "backup to another region" button. Backup is something you set up, not something Spaces does for you.

The CDN Is Not a Backup

DigitalOcean Spaces includes a built-in CDN that caches your objects at edge locations for faster delivery. This is easy to mistake for replication, but it is not. The CDN caches copies for performance and can expire them at any time. The authoritative copy still lives in one region, and if that object is lost, the cache does not protect you. Edge caching speeds up reads; it does not give you a durable second copy.

How to Copy a Space to Another Region or Provider

Since Spaces will not replicate for you, the job is a straightforward copy, and Blober handles it without scripts or AWS-CLI loops.

Spaces to another Spaces region. Connect your DigitalOcean account in Blober. It detects every Space across all regions in one view, so you can copy objects from a Space in one region into a Space you create in another. Run it again later to refresh the copy, skipping objects that already exist.
Spaces to another provider. Use the same flow to copy a Space to AWS S3, Backblaze B2, Wasabi, Cloudflare R2, Azure Blob, Google Drive, Dropbox, or local and NAS storage, for an offsite backup that does not depend on DigitalOcean at all.
Resumable. Large copies survive a dropped connection and continue where they stopped.

This gives you the second copy that Spaces does not provide on its own, in whichever region or provider you choose.

Migrating Off DigitalOcean

If the goal is not a backup but a move, the steps are the same, just pointed at one destination. The most common move is to Amazon S3, which has the storage tiers and ecosystem Spaces lacks. There is a full walkthrough in How to Migrate from DigitalOcean Spaces to AWS S3, including how Blober detects Spaces across all seven regions and maps them to S3 storage classes.

For very large Spaces with millions of objects, see Migrating 100 Million Files from DigitalOcean to Backblaze.

Frequently Asked Questions

Does DigitalOcean Spaces support cross-region replication? No. There is no built-in cross-region replication. To have a Space's objects in a second region, you copy them yourself, which Blober can do across all regions in one workflow.

Which regions can I create a Space in? Currently NYC3, SFO3, AMS3, FRA1, SGP1, SYD1, and BLR1. DigitalOcean occasionally adds regions, so confirm on their site.

Can I move a Space from one region to another? Not in place. You create a new Space in the target region and copy the objects over. Blober copies between regions directly without downloading everything to your computer first.

Is the Spaces CDN a backup? No. The CDN caches objects at the edge for faster delivery and can evict them at any time. The durable copy still sits in one region. For a backup, make a separate copy in another region or provider.

How do I migrate from DigitalOcean to AWS? Connect both in Blober, set DigitalOcean as the source and S3 as the destination, and run. The DigitalOcean Spaces to AWS S3 guide covers it step by step.

Get Blober

Make the second copy that DigitalOcean Spaces will not make for you, to another region or another provider. Blober is a one-time purchase with no per-GB fees.

Download Blober at blober.io

Data Holders: How Blober Fits Your Workflow

Mar 14, 2026

Who Are Data Holders?

Data holders are individuals and organizations that accumulate, manage, and preserve large volumes of digital files as a core part of their work. They aren't just storing files - they're responsible for keeping data accessible, organized, and safe across years and even decades.

Data holders include:

Photographers and videographers with terabytes of RAW footage and project archives
Researchers and academics maintaining datasets, papers, and experimental outputs
Small businesses managing client records, invoices, contracts, and media assets
IT administrators responsible for infrastructure backups and compliance archives
Content creators with libraries of video, audio, and design files across platforms
Legal and medical professionals bound by retention requirements for sensitive records
Personal archivists preserving family photos, home videos, and documents

What unites them is a common problem: data grows, scatters, and becomes harder to manage over time.

The Data Holder's Problem

Most data holders didn't plan to end up with files in five different places. It happens organically:

Files start local - on a laptop, NAS, or external drive
Cloud adoption fragments storage - Google Drive for sharing, Dropbox for syncing, an S3 bucket for backups
Platform lock-in creeps in - GoPro Cloud holds your footage, iCloud holds your photos, OneDrive holds your documents
Manual management breaks down - folder naming conventions drift, backups become inconsistent, some files have three copies while others have none

The result is a scattered, fragile data footprint where no single tool gives you visibility across all your storage.

Symptom	Root Cause
"I know I have that file somewhere"	Files spread across 3-5 providers with no unified view
"My backup is months out of date"	Manual backup processes that require constant attention
"I'm paying for storage I barely use"	Redundant copies in expensive tiers that should be archived
"I can't move my data without paying egress"	Provider lock-in via egress fees and proprietary APIs
"Organizing everything would take weeks"	Flat folder structures with no metadata-driven automation

How Blober Solves This

Blober is a desktop application purpose-built for data holders who need to move, organize, and back up files across cloud providers and local storage - without recurring fees.

1. One Interface for All Your Storage

Blober connects to the storage providers data holders actually use:

Provider	Typical Use Case
AWS S3	Production infrastructure, enterprise backups
Backblaze B2	Affordable long-term archive
Wasabi	Hot storage with no egress fees
Cloudflare R2	CDN-adjacent delivery, zero egress
Google Cloud Storage	Workspace-integrated projects
Azure Blob Storage	Enterprise and compliance workloads
DigitalOcean Spaces	Dev team object storage
GoPro Cloud	Action camera footage (Blober exclusive)
Dropbox	File sharing and synchronization
Local / NAS	On-premise primary storage

No other single tool covers this range - especially GoPro Cloud, which Blober is the only application to support.

2. Direct Cloud-to-Cloud Transfers

Instead of downloading files to your machine and re-uploading them, Blober transfers data directly between providers. This matters for data holders because:

Saves time - a 2 TB migration doesn't bottleneck on your home internet
Saves bandwidth - your ISP data cap stays intact
Reduces failure points - no half-downloaded files sitting on your local disk

3. Metadata-Driven Organization

Data holders accumulate files over years. Manually sorting them into folders is unsustainable. Blober supports path templates that use file metadata to auto-organize during transfer:

/{year}/{month}/{camera_model}/{filename}

A flat dump of 50,000 files becomes a clean archive:

/2025/06/HERO13 Black/GX015742.MP4
/2025/06/Canon EOS R5/IMG_4521.CR3
/2026/01/iPhone 15 Pro/IMG_0032.HEIC

This works for any transfer - cloud-to-cloud, cloud-to-local, or local-to-cloud.

4. Scheduled and Resumable Transfers

Backup workflows for data holders need to be reliable, not heroic. Blober supports:

Resumable transfers - if your connection drops or your machine restarts, pick up where you left off
Incremental syncs - only transfer files that are new or changed since the last run
Large-file handling - multi-part uploads for files in the tens of gigabytes

No babysitting required. Set up a transfer, let it run, and come back to a completed job.

5. One-Time Pricing

Most cloud migration tools charge per-GB or require annual subscriptions with data caps. For data holders who move terabytes regularly, those costs compound:

Tool	Pricing Model	Cost for 10 TB/year
Flexify.io	~$0.03/GiB per migration	~$300+ (plus egress)
MultCloud	$99.98/year for 2.4 TB cap	~$400+ (need multiple renewals)
rclone	Free but manual	$0 (but hours of CLI configuration)
Blober	One-time purchase	One price, unlimited transfers

You buy Blober once. Transfer 1 TB or 100 TB - the price doesn't change.

Real-World Workflows

The Freelance Videographer

Setup: 8 TB of footage across GoPro Cloud, a local NAS, and Google Drive. Delivers finals via Dropbox.

With Blober:

Connects GoPro Cloud and pulls all footage to Backblaze B2 as a cold archive
Moves finished projects from local NAS to Cloudflare R2 for client delivery
Uses path templates to organize by project date and camera model
Runs periodic syncs from Google Drive to B2 to keep a second backup

Result: One tool replaces four manual processes. Total cost: one Blober license.

The Small Business IT Admin

Setup: 500 GB of compliance documents in Azure Blob Storage. Daily operational files in Google Workspace. Regulatory requirement for off-site backup.

With Blober:

Transfers compliance archive from Azure to Backblaze B2 as a secondary backup
Syncs critical Google Drive folders to a local NAS nightly
Uses Blober's incremental sync so only changed files move each day

Result: Meets audit requirements for geographic redundancy without provisioning a second enterprise cloud account.

The Research Lab

Setup: 12 TB of experimental datasets in AWS S3. New data generated weekly. Grants require data preservation for 10 years.

With Blober:

Migrates completed datasets from S3 Standard to Backblaze B2 (80% storage cost reduction)
Keeps active datasets in S3 for compute-adjacent access
Uses metadata templates to organize by experiment ID and date
Resumable transfers handle multi-GB dataset files without corruption

Result: Storage costs drop dramatically while preservation requirements are met.

Why Not Just Use rclone?

rclone is a powerful open-source CLI tool, and many data holders start there. But it has real limitations for ongoing data management:

Capability	rclone	Blober
GUI for browsing files	No (CLI only)	Yes
GoPro Cloud support	No	Yes (exclusive)
Dropbox support	Yes	Yes
Visual transfer progress	Limited	Full progress dashboard
Resumable multi-part uploads	Partial	Built-in
Path template organization	Manual scripting	Visual template builder
Error handling and retry	Config flags	Automatic
Setup time	Hours (config per remote)	Minutes (OAuth flows)

rclone is great for scripted, automated pipelines. Blober is built for data holders who want reliable transfers without writing shell scripts.

Getting Started as a Data Holder

Audit your storage - list every provider and local device where you keep files
Identify your archive tier - choose an affordable destination like Backblaze B2 or Wasabi for long-term storage
Connect everything in Blober - add each provider via OAuth or API key
Set up your first migration - pick a source, pick a destination, configure a path template
Let Blober handle the rest - resumable transfers, incremental syncs, and metadata organization do the heavy lifting

Your Data, Your Infrastructure

Data holders shouldn't need a subscription to manage their own files. Blober runs locally on your machine - your credentials never pass through third-party servers, your transfer bandwidth isn't metered, and your workflow isn't gated by monthly caps.

One license. Unlimited providers. Unlimited data.

Get Blober and take control of your data workflow.

Stop Paying Rent to Move Your Own Files

Mar 9, 2026

The Trap

You uploaded 2 TB of photos, videos, and backups to the cloud. Life was good - until you wanted to move them somewhere else.

Suddenly, you're hit with egress fees, per-GB migration charges, and the realization that your cloud provider has been counting on you never leaving. It's your data. But moving it costs real money - every single time.

AWS charges ~$0.09/GB for egress. That's $184 just to download 2 TB of your own files. Want to use a SaaS migration tool? That's another $10-20/month, with transfer caps. Prefer the open-source CLI route? Clear your afternoon - you'll need it for YAML configs, credential files, and provider-specific quirks.

The trap: cloud providers charge you egress fees, SaaS tools charge subscriptions, and CLI tools cost you hours of setup time

The Math

Let's talk real numbers. Over three years, here's what you'll pay using common approaches:

Approach	3-Year Cost	Catch
SaaS Migration Tool	~$360	Monthly sub + data caps
Per-GB Service	~$720+	$0.03/GB, billed every transfer
DIY with CLI	40+ hours	Config per provider, no UI, breaks silently
Blober	One payment	Unlimited transfers. Forever.

The subscription model is designed to extract value from you month after month. The per-GB model punishes you for having more data. The CLI path trades money for your time.

Blober breaks the cycle. Pay once. Transfer as much as you want, as many times as you want. No meter running. No renewal emails. No "upgrade to unlock more."

$Cost comparison over 3 years: SaaS tools cost $360, per-GB services cost $720+, DIY CLI costs 40+ hours, Blober costs one single payment$

The Escape

Blober is a desktop app - not a SaaS, not a CLI tool, not a cloud service. It runs on your Mac, Windows, or Linux machine and connects directly to your cloud providers:

AWS S3 - buckets and objects, any region
Azure Blob Storage - containers and blobs
Google Drive - files and folders, including shared drives
GoPro Cloud - back up your action footage locally or to any cloud
Backblaze B2 - the affordable S3 alternative
Dropbox - personal and business accounts
Cloudflare R2 - zero-egress object storage
Wasabi - hot storage without the cold fees
DigitalOcean Spaces - all regions, auto-detected
Local Disk - any folder on your machine

Your files never touch a middleman server. Blober streams directly between your machine and the provider APIs. Browse your cloud storage visually, select what you want, pick a destination - done.

If a transfer gets interrupted (bad WiFi, laptop closed, provider hiccup), Blober picks up where it left off. No re-uploading. No duplicate files.

Blober connects many cloud providers in one app: AWS S3, Azure Blob, Google Drive, GoPro Cloud, Backblaze B2, Dropbox, Cloudflare R2, Wasabi, DigitalOcean Spaces, local disk, and more

The Move

Here's what switching to Blober actually looks like:

Before: You're juggling browser tabs, CLI sessions, and a spreadsheet tracking which files went where. A SaaS tool emails you that you've hit your 1.2 TB monthly cap. You Google "rclone config azure" for the third time.

After: You open Blober. Connect your accounts. Drag from source to destination. Walk away. It just works.

No internet needed for local-to-local moves. No data ever leaves your machine unless you're sending it to a cloud provider you chose.

Before and after comparison: monthly subscriptions, data caps, and files routed through servers vs. one-time payment, unlimited transfers, and 100% local execution with Blober

Who Is This For?

Photographers & videographers moving terabytes of footage from GoPro Cloud or Google Drive to cheaper archival storage
Developers & DevOps engineers migrating between S3-compatible providers without writing scripts
Small businesses consolidating cloud storage without paying an enterprise migration service
Privacy-conscious users who want their files transferred directly, not through a third-party cloud
Anyone tired of paying monthly fees to tools that move files you already own

Get Blober

Your data. Your machine. Your rules.

One payment. Unlimited transfers. No expiration.

Download Blober => blober.io

Migrating 100M+ Files from DigitalOcean Spaces to Backblaze B2

Feb 28, 2026

The Scenario

A media company has 25TB of data spread across 120 million files in DigitalOcean Spaces. Monthly bill: roughly $500/month. They want to move everything to Backblaze B2 to cut costs and get more flexibility.

This is a real-world pattern we see a lot. Let's walk through what it actually takes.

What It Costs

Item	Details	Estimated Cost
Blober License	One-time purchase, no subscription	See pricing
DigitalOcean Egress	~24TB billable at $0.01/GiB (first 1TB free)	~$240
Backblaze Ingress	Free. Backblaze never charges for uploads	$0
Backblaze API Calls	Uploads are free Class A calls, minor listing costs	~$2
Total (excluding license)		~$242

After migrating, the monthly bill drops from ~$500 on DigitalOcean to ~$150 on Backblaze B2. With a one-time license and no per-GB transfer fees, the move pays for itself within the first month.

About Egress Fees

This is where it gets interesting. Backblaze actively wants people to switch to their platform and they back that up with real programs:

Free egress up to 3x your average monthly storage on B2, which means once you're on Backblaze, downloading your own data doesn't cost extra in most scenarios.
Unlimited free egress through CDN and compute partners like Cloudflare, Fastly, Bunny.net, and Vultr.
Assisted data migration is listed as a standard B2 feature on their pricing page.
Universal Data Migration is available for larger committed contracts (50TB+ on pay-as-you-go, or included with B2 Reserve annual plans).

Backblaze explains their philosophy well in this blog post: Cloud Egress Fees: What They Are and How to Reduce Them. The short version is that they believe egress fees are vendor lock-in, and they want to make switching easy.

Even if your dataset is under the 50TB threshold, it's worth contacting their sales team. With a 25TB dataset and willingness to commit for 12 months, there's a solid chance they'll help reduce or cover the DigitalOcean egress fees to get you onboarded.

How Long Does It Take

Let's be honest here. 25TB is a lot of data.

Every file needs its own set of API calls: list from the source, download, then upload to the destination. Each round-trip carries network latency regardless of file size. When you multiply that per-object overhead across 120 million files with 25TB of bandwidth on top, the aggregate time adds up fast.

For a client-side migration where data streams through your local machine, you're looking at:

Several weeks of continuous runtime depending on your connection speed and latency
Your machine needs to stay on and connected the entire time
If your ISP has a monthly data cap, 25TB will almost certainly exceed it
16GB+ RAM recommended for handling the file listing at this scale

This isn't a Blober limitation. Any client-side tool (rclone, Cyberduck, whatever) will face the same physics. Data has to travel from DigitalOcean's datacenter to your machine, then from your machine to Backblaze's datacenter. That's two full trips through your ISP.

The Smart Approach: Two Phases

Phase 1: Let the Datacenters Do the Heavy Lifting

Contact Backblaze's sales team and ask about their assisted migration options. For datasets at this scale, they partner with migration services that can move data directly between datacenters at speeds your home connection can't match. What takes weeks on a home connection can take hours on a datacenter link.

Reach out here: Backblaze Sales

Phase 2: Use Blober for Everything After

Once the initial bulk migration is done, Blober becomes your daily tool for managing files across providers. New uploads, folder syncs, log rotations, moving files between buckets, all handled from your desktop with no per-GB fees and no subscriptions. Your credentials stay on your machine and never touch a third-party server.

Monthly Cost Comparison (Post-Migration)

	DigitalOcean Spaces	Backblaze B2
Storage (25TB)	~$500/mo	~$174/mo
Egress (3TB/mo)	~$30/mo	Free (within 3x allowance)
Total	~$530/mo	~$174/mo
Annual	~$6,360/yr	~$2,088/yr

That's about $4,200 saved per year, every year.

Bottom Line

For large-scale one-time migrations, use Backblaze's own migration programs. They want your business and they'll often help you get there.

For everything after that, Blober gives you a one-time license to manage, sync, and move files across any supported provider, with no recurring costs and no third party ever touching your credentials.

What Is Blober? Cloud File Transfer Made Simple

Feb 23, 2026

The Problem

Transferring files between cloud providers today means monthly subscriptions, surprise transfer fees, and wrestling with CLI config files. Most tools are either expensive SaaS platforms or developer-only terminals with steep learning curves.

The Solution

Blober is a desktop app that connects all your cloud storage in one place. AWS S3, Azure Blob Storage, Google Drive, GoPro Cloud, Backblaze B2, Wasabi, local disk, and more - all supported out of the box. No CLI. No config files. Just a beautiful, intuitive interface.

Meet Blober: one app to move files between AWS S3, Azure Blob, Google Drive, GoPro Cloud, Backblaze B2, Wasabi, local disk, and more

The Value

Buy once, transfer forever. No subscriptions. No transfer fees. Blober runs natively on Mac, Windows, and Linux - and it works offline too.

Blober: buy once, transfer forever. No subscriptions, no transfer fees, beautiful UI, works offline, runs on Mac, Windows, and Linux

Get Blober

Stop renting your tools. Download Blober =>

The True Cost of Cloud Data Migration in 2026

Feb 15, 2026

The Hidden Tax on Moving Your Own Data

Moving data between cloud providers should be simple. You own the files - you just want them somewhere else. But the cloud industry has turned data migration into a profit center, layering fees at every step: egress charges, per-GB migration fees, monthly subscriptions, and data traffic caps.

Here's what cloud data migration actually costs in 2026, and why Blober's one-time pricing model is a fundamentally better deal for anyone who transfers data more than once.

The Three Cost Models

1. Per-GB Fees (Flexify.io)

Flexify charges a per-GiB fee for every migration, on top of your cloud provider's egress charges.

Migration Size	Flexify Fee (~$0.03/GiB)	Provider Egress (AWS ~$0.09/GB)	Total
100 GB	$3	$9	~$12
1 TB	$30	$92	~$122
10 TB	$307	$922	~$1,229
100 TB	$3,072	$9,216	~$12,288

These are per-job costs. Run the same migration next month? Pay again. Sync regularly? The meter never stops.

Flexify does offer managed migrations for 10+ TB where provider egress may be avoided through direct peering - but those require contacting sales and negotiating custom pricing.

2. Annual Subscriptions with Data Caps (MultCloud)

MultCloud charges an annual subscription that includes a fixed amount of transfer traffic:

Plan	Annual Cost	Data Allowance	Cost Per TB Transferred
Free	$0	5 GB/month	N/A (60 GB/year cap)
1,200 GB plan	$59.99/year	1,200 GB/year	~$50/TB
2,400 GB plan	$99.98/year	2,400 GB/year	~$42/TB

Hit the cap? Transfers stop until you renew. Need to move 5 TB? You'll need to buy the top-tier plan and wait over two years to exhaust the quota - or pay for multiple years upfront.

Over three years, MultCloud costs $180-$300 in subscriptions alone, and you're still capped on how much data you can actually move.

3. One-Time License (Blober)

Blober charges a one-time license fee. No per-GB charges. No annual renewal. No data caps.

Migration Size	Blober Cost	Provider Egress (your standard cloud fees)
100 GB	✅ One-time license	Standard egress only
1 TB	✅ Same license	Standard egress only
10 TB	✅ Same license	Standard egress only
100 TB	✅ Same license	Standard egress only

The only variable cost is your cloud provider's standard egress fee - which you'd pay with any tool, including rclone. There is no Blober surcharge.

The Compounding Problem

Per-GB fees and subscriptions compound over time. If you migrate data regularly - monthly syncs, media archives, backup rotations - the cost gap widens fast:

Scenario	Flexify (per-GB)	MultCloud (subscription)	Blober (one-time)
One 1 TB migration	~$122	$59.99/year	✅ One-time
Monthly 500 GB sync	~$732/year	Exceeds cap	✅ One-time
3 years of regular use	$2,196+	$180-$300	✅ One-time

For users who transfer data as part of their regular workflow - not a one-time event - subscription and per-GB models are an ongoing tax. Blober eliminates it.

What About rclone?

rclone is free and open-source. On raw cost, nothing beats free.

But rclone's cost is measured in time, not money:

Setup time - configuring remotes, flags, and cron jobs
Debugging time - when a transfer fails silently or a flag is wrong
Maintenance time - updating scripts when providers change APIs

For engineers who already live in the terminal, rclone is excellent. For everyone else, the time cost is significant and ongoing. Blober trades a one-time purchase for a visual, persistent workflow engine that eliminates scripting overhead entirely.

Egress Fees: The Unavoidable Cost

Regardless of which tool you use, cloud provider egress fees apply when downloading data. These are charged by your cloud provider, not by Blober:

Provider	Storage (TB/mo)	Egress (per GB)	Notes
AWS S3	$26	$0.09	Egress-heavy workloads get expensive
Azure Blob Storage	$20	$0.08	First 100 GB/month free
Google Cloud Storage	$23	$0.11	Varies by region
Backblaze B2	$6.95	Free (up to 3x)	Free egress up to 3x stored
Wasabi	$6.99	Free	No egress fees ever
Cloudflare R2	$15	Free	Zero egress by design
DigitalOcean Spaces	$5 (250 GB)	$0.01	1 TB outbound included

Pro tip: If you're choosing a destination for long-term storage, providers like Backblaze B2 ($6.95/TB/mo, free egress), Wasabi ($6.99/TB/mo, no egress fees), and Cloudflare R2 (zero egress) offer significantly lower total cost of ownership than AWS, Azure, or GCS. Blober supports all of them.

TL;DR

Tool	Cost Model	Best For
Flexify.io	Per-GB + egress	Enterprise one-time migrations
MultCloud	Annual subscription	Light, occasional consumer transfers
rclone	Free (time cost)	Engineers comfortable with CLI
Blober	One-time license	Anyone who transfers data regularly, values simplicity, or needs GoPro Cloud support

If you transfer data more than once - or plan to - a one-time license pays for itself after a single job. No subscriptions. No per-GB surprises. No data caps.

Get Blober =>

Blober vs Flexify

Feb 1, 2026

Overview

Both Blober and Flexify.io solve the same core problem: moving large volumes of data between cloud storage providers. They approach the problem from fundamentally different architectural and economic philosophies.

Flexify.io (founded 2015, Tampa FL) is a managed, cloud-based migration and virtualization platform built for enterprises moving tens or hundreds of terabytes in controlled, one-time projects. Blober is a local-first desktop workflow engine designed for continuous, repeatable transfers, with no subscriptions, no per-GB fees, and no third-party servers touching your data.

Architectural Philosophy

Flexify.io

Cloud-hosted migration engines deployed on Flexify-managed infrastructure
Data routes through Flexify servers (or, for managed 10 TB+ migrations, direct cloud-to-cloud)
Usage-based pricing: you pay per GiB transferred
Emphasis on API virtualization: translates Amazon S3 API to Azure Blob Storage on-the-fly
Supports ~25 object-storage providers (S3-compatible, Azure, GCS, Alibaba, etc.)

Blober

Runs entirely on your local machine (Windows, macOS, Linux)
Transfers go directly between your machine and each storage provider - no intermediary servers
All credentials stored locally and never transmitted to a third party
Supports unique providers like GoPro Cloud that no other migration tool covers

This distinction matters for users who care about cost predictability, credential ownership, data sovereignty, and ongoing workflows rather than one-time migrations.

Pricing Model Comparison

Aspect	Blober	Flexify.io
Pricing style	✅ One-time license	Usage-based (per GiB)
Current cost	Discounted beta pricing	~$0.03/GiB Flexify fee + provider egress ($0.05-$0.09/GiB)
Subscription	✅ None	Sign-up required ($20 free credit)
Long-term cost	✅ Fixed forever	Grows with every transfer
1 TB migration	✅ One-time price	~$80 to $120+ in fees

For a single 1 TB migration from AWS S3 to Google Cloud Storage, Flexify's self-service rate is approximately $0.08 to $0.12 per GiB, which works out to $80 to $120+ for that one job. With Blober, only your provider's standard egress fees apply; there is no Blober per-GB charge.

Feature Comparison

Feature	Blober	Flexify.io
Cloud-to-cloud transfer	✅ Yes	Yes
Local filesystem integration	✅ Yes	Limited
GoPro Cloud support	✅ Yes	❌ No
Metadata-based path templating	✅ Yes	No
Persistent task history	✅ Yes	Managed dashboard
Workflow reuse	✅ Yes	Limited
Resumable workflows	✅ Yes	Yes
API access	No	Yes
Virtual S3 endpoint	No	Yes
Credential storage	✅ Local only	Cloud-managed
Data path	✅ Direct	Through Flexify servers

Data Sovereignty and Privacy

With Flexify, your storage credentials are stored on their servers and your data may transit through Flexify-managed infrastructure. For regulated industries, sensitive media archives, or personal data, this introduces a third-party dependency and potential compliance exposure.

Blober eliminates this concern entirely:

Credentials never leave your machine. No third-party vault, no OAuth token stored in a SaaS dashboard
Data flows directly between your local machine and each cloud provider
Blober works offline with a one-time license
Full control over when, where, and how your data moves

Unique Provider Coverage

Blober is the only migration tool that supports GoPro Cloud, letting GoPro users back up or transfer their media archives to any supported provider (AWS S3, Backblaze B2, Wasabi, local disk, etc.). Neither Flexify, rclone, nor MultCloud offer GoPro Cloud integration.

This makes Blober the go-to choice for photographers, videographers, and agencies managing GoPro footage across storage tiers.

Maturity and Risk Tradeoff

Flexify.io is a mature enterprise platform (since 2015) with production-scale deployments and petabytes migrated. Blober is newer and currently in beta, with faster iteration and less operational overhead.

Blober offsets its maturity gap with:

Aggressive beta pricing: lock in your license before prices go up
Rapid feature development with direct community influence on the roadmap
No lock-in to ongoing fees: one purchase, unlimited use
Desktop-native architecture that is inherently simpler and more predictable

When Blober Makes More Sense

Choose Blober if you:

Transfer data regularly, not just once
Want full control over credentials and data flow
Need GoPro Cloud support (only Blober has it)
Prefer a native desktop UI over enterprise SaaS dashboards
Want predictable lifetime pricing with no per-GB surprises
Care about data sovereignty, with no third-party servers touching your files

Download Blober at blober.io

Blober vs Flexify vs rclone

Feb 1, 2026

Overview

Three tools dominate cloud data transfer in 2026 - each solving the problem from a completely different angle. Here's how they compare.

High-Level Comparison Table

Dimension	Blober	Flexify.io	rclone
Architecture	✅ Local-first desktop	Managed SaaS	CLI utility
Pricing	✅ One-time license	Usage-based (~$0.03-$0.04/GiB + egress)	Free
Ease of use	✅ High (native GUI)	Medium (web dashboard)	Low (terminal only)
Provider count	9+ and growing	~25 (object storage)	70+
GoPro Cloud support	✅ Yes (exclusive)	❌ No	❌ No
Credential control	✅ Local only	Cloud-managed	Local config file
Data path	✅ Direct (no middleman)	Through Flexify servers	Direct (local)
Workflow persistence	✅ Built-in	Dashboard-based	None (manual scripts)
Task history & resume	✅ Built-in	Dashboard-based	Logs only
Metadata path templates	✅ Yes	No	Manual scripting
Automation	Limited	High	Very high
API virtualization	No	Yes (S3-to-Azure gateway)	No
Enterprise scale	High	High	High
Open source	No	No	Yes
Best for	Agencies, creators, engineers	Enterprises (petabyte migrations)	Engineers, sysadmins

Pricing at a Glance

Scenario	Blober	Flexify.io	rclone
100 GB migration	✅ One-time	~$8 - $12	Free
1 TB migration	✅ One-time	~$80 - $120+	Free
10 TB migration	✅ One-time	~$800 - $1,200+	Free
Recurring monthly	✅ $0	Compounds every run	Free

Flexify charges per GiB transferred plus cloud provider egress fees. Costs add up fast for recurring workflows. rclone is free but demands engineering time. Blober sits in the sweet spot: pay once, transfer forever.

Data Sovereignty

Concern	Blober	Flexify.io	rclone
Credentials stored	✅ Local only	Flexify servers	Local config file
Data transits 3rd party	✅ No	Yes (Flexify infra)	No
Account required	✅ No	Yes	No
Offline operation	✅ Yes	No	Yes

For regulated industries, sensitive media archives, or personal data - avoiding third-party intermediaries is not a preference, it is a requirement. Both Blober and rclone keep your data path clean. Flexify introduces a managed middleman.

The GoPro Factor

Blober is the only transfer tool that supports GoPro Cloud. Neither Flexify nor rclone can access GoPro's storage. If you manage GoPro footage - whether as a creator, agency, or production house - Blober is the only option for migrating that media to professional storage like Backblaze B2, AWS S3, or your local NAS.

Summary

rclone is the most powerful tool if you are deeply technical, automation-driven, and comfortable with terminal workflows. It is free and supports 70+ providers.
Flexify.io is ideal for enterprises running massive one-time migrations under strict SLAs, especially when virtual S3 endpoints or managed infrastructure are required. Budget accordingly - costs scale with data volume.
Blober fills the gap between them: professional-grade transfers with a native desktop GUI, local credential control, visual workflows, predictable one-time pricing, and exclusive GoPro Cloud support.

Blober's beta pricing locks in a lifetime license at a fraction of the cost competitors charge for a single large migration. For users who value simplicity, sovereignty, and long-term savings - Blober is the clear choice.

Blober vs MultCloud

Feb 1, 2026

Overview

MultCloud (founded 2012, Hong Kong) is a web-based platform for transferring, syncing, and managing files across 30+ cloud services. It is subscription-based and routes all data through MultCloud's servers.

Blober is a local-first desktop application that transfers data directly between your machine and cloud providers, with no middleman, no subscription, and no data caps.

Both tools target non-technical users who want cloud-to-cloud transfers without writing scripts. The difference lies in architecture, pricing, and trust.

Architectural Difference

MultCloud

Web-based SaaS: runs entirely in your browser
All data routes through MultCloud's servers in Hong Kong
Requires an account and OAuth access to your cloud accounts
Subscription required for meaningful use (free tier: 5 GB/month)

Blober

Native desktop application (Windows, macOS, Linux)
Data flows directly between your machine and each cloud provider
No intermediary servers. Your files never touch a third party
Credentials stored locally, never transmitted

Pricing Model Comparison

Aspect	Blober	MultCloud
Pricing style	✅ One-time license	Subscription (annual)
Free tier	N/A (beta pricing)	5 GB/month, 2 transfer threads
Mid-tier plan	-	$59.99/year for 1,200 GB/year
Top-tier plan	-	$99.98/year for 2,400 GB/year
Transfer threads	Automatic parallelism	Free: 2 threads, Paid: 10 threads
Data cap	✅ None	Capped per plan (5 GB to 2,400 GB/year)
Long-term cost (3y)	✅ One-time purchase	$180 to $300+

MultCloud's data traffic limits are a hard ceiling. Once you exhaust your annual quota, transfers stop until you renew. Blober has no transfer caps. Move as much data as your bandwidth allows.

Feature Comparison

Feature	Blober	MultCloud
Cloud-to-cloud transfer	✅ Yes	Yes
Local filesystem integration	✅ Yes	No (web-only)
GoPro Cloud support	✅ Yes (exclusive)	❌ No
Storage-optimized transfers	✅ Yes	Generic
Workflow persistence	✅ Yes	Scheduled tasks
Task history and logs	✅ Yes	Basic dashboard
Metadata path templates	✅ Yes	No
Resumable transfers	✅ Yes	Limited
Sync (two-way)	Planned	Yes
Email-to-cloud (PDF)	No	Yes
Credential storage	✅ Local only	MultCloud servers (OAuth)
Data path	✅ Direct	Through MultCloud servers

Data Sovereignty and Privacy

This is where the difference is starkest. MultCloud requires OAuth access to your cloud accounts and routes all transferred data through its own servers. Their privacy page states data is "temporarily cached" during operations.

Blober takes the opposite approach:

Credentials never leave your machine. No OAuth tokens stored on third-party servers
Data flows directly between your local machine and each cloud provider
No account needed. Blober works with a license key, offline
No data caching. Nothing is stored, buffered, or logged on remote servers

For users transferring personal photos, sensitive business documents, or media archives, the question is simple: do you want your data flowing through servers in Hong Kong, or directly from your machine to your cloud provider?

GoPro Cloud: Only on Blober

MultCloud supports 30+ consumer cloud services (Google Drive, Dropbox, OneDrive, etc.) but does not support GoPro Cloud. If you need to move GoPro footage to professional storage like Backblaze B2, AWS S3, or Wasabi, MultCloud cannot help.

Blober is the only transfer tool with native GoPro Cloud integration, which makes it essential for photographers, videographers, and agencies managing action camera footage.

When Blober is the Sharper Tool

Choose Blober if you:

Need to move large volumes of data without annual caps
Want predictable, one-time pricing, not $60 to $100/year forever
Prefer local execution over web-based SaaS
Require data sovereignty, with no files routing through third-party servers
Need GoPro Cloud support (only Blober has it)
Value detailed task history, resumable workflows, and metadata-based organization
Care about credential security, with no OAuth tokens stored in the cloud

Blober vs rclone

Feb 1, 2026

Overview

rclone is the industry-standard CLI tool for cloud storage automation among developers and sysadmins. It is extremely powerful, supports over 70 storage providers, and is completely free and open-source. Its tradeoff is complexity - every job requires flags, config files, and terminal expertise.

Blober is built for users who want rclone-level capability without managing flags, scripts, or terminal state. It replaces stateless CLI execution with persistent, visual workflows that anyone can set up and repeat.

Interface and Usability

rclone

Command-line only (experimental web GUI exists, but limited)
Configuration files and flags - every job requires manual setup
Excellent for scripting and cron-based automation
Steep learning curve for non-technical users
No built-in workflow persistence - you must manage your own scripts

Blober

Native desktop GUI (Windows, macOS, Linux)
Visual setup of sources, destinations, and filters
Saved workflows with one-click execution
Built-in task history with resumable state
Designed for repeatability and clarity - no terminal required

Feature Comparison

Feature	Blober	rclone
Interface	✅ GUI	CLI
Provider count	Growing	70+
GoPro Cloud support	✅ Yes	❌ No
Local filesystem	✅ Yes	Yes
Cloud-to-cloud	✅ Yes	Yes
Workflow persistence	✅ Yes	No (manual scripts)
Metadata path templates	✅ Yes	Manual scripting
Task history & resume	✅ Yes	Logs only
Encryption	Planned	Built-in
Automation	Limited	Extensive
Open source	No	Yes
Data path	✅ Direct	Direct (local)

GoPro Cloud: A Blober Exclusive

rclone supports over 70 providers - but GoPro Cloud is not one of them. If you shoot with GoPro cameras and want to move your media from GoPro's cloud to Backblaze B2, AWS S3, Wasabi, or your local NAS, rclone simply cannot help.

Blober is the only transfer tool with native GoPro Cloud integration, making it the obvious choice for photographers, videographers, action sports creators, and agencies managing GoPro media libraries.

Workflow Example

rclone requires upfront configuration, careful flag selection, and scripting discipline to safely repeat jobs:

rclone copy remote:bucket/path dest:bucket/path \
  --transfers 4 --checkers 8 --retries 3 \
  --filter-from filters.txt --log-file transfer.log

Forget a flag? Change a path? The job silently behaves differently. There is no built-in history of what ran, when, or whether it succeeded.

Blober stores each workflow as a durable configuration with immutable execution history. If a transfer is interrupted, Blober resumes based on stored state rather than re-running a stateless command.

This difference becomes critical for:

Long-running transfers over unreliable connections
Media archives with thousands of files
Users who run transfers infrequently and forget the exact flags
Teams where multiple people need to trigger the same workflow

Data Sovereignty

Both rclone and Blober are local-first tools - your credentials stay on your machine. This is a shared advantage over SaaS competitors like Flexify and MultCloud where credentials and potentially data flow through third-party servers.

Where Blober adds value over rclone:

No terminal exposure - credentials are managed in a secured desktop app, not plaintext config files
Encrypted credential storage - not a ~/.config/rclone/rclone.conf file on disk
Visual audit trail - every transfer logged with timestamps, file counts, and status

Cost and Support

Aspect	Blober	rclone
Cost	One-time license	Free
Support	Product support	Community forums
Updates	Included with license	Community-driven
Target user	Creators, agencies, engineers	Engineers, sysadmins

rclone being free is a genuine advantage. Blober earns its price by saving time, reducing errors, and opening cloud transfers to users who would never touch a terminal.

When Blober Makes More Sense

Choose Blober if you:

Prefer visual tools over terminal commands
Want repeatable workflows without writing scripts
Need GoPro Cloud support (only Blober has it)
Need clarity, task history, and one-click resumption
Transfer data occasionally but need it to work reliably every time
Value convenience and productivity over maximum flexibility
Want credentials stored securely - not in a plaintext config file

Download Blober at blober.io

object storage

What Path Templating Means in Blober

Where the Feature Is in the App

1. Source Configuration

2. Destination Configuration

3. Preview & Summary

The Three Path Modes

Mode 1: Copy the Structure As-Is

Mode 2: Flatten the Selection

Mode 3: Build a Custom Path

Every Available Variable

How Template Evaluation Works

Variables and Filters Solve Different Problems

Important Metadata Limits

Copy and Move

Detailed Guides in This Series

A Safe First Workflow

Object Storage Is Not a Digital Asset Manager

The Blober Model

What This Can and Cannot Search

Example: Recover a Flat Media Bucket

Example: Extract Business Records

Example: Split Active and Archive Storage

Reorganizing on the Same Provider

Why Not Build an Index First?

Make the Destination Easier to Search Next Time

Safe Rollout

Ingress Is Usually Free, Egress Is Not

Provider Groups by Transfer Pricing

When Ingress Should Decide

When Egress Should Decide

When You Need Both

How Blober Fits

Frequently Asked Questions

Related Guides

Get Blober

Wasabi Hot Cloud Storage

Backblaze B2 Cloud Storage

Cloudflare R2

Rabata

Storj

IDrive e2

Cubbit DS3

Impossible Cloud

Seagate Lyve Cloud

Synology C2 Object Storage

MEGA S4 Object Storage

Tebi

Storadera

Telnyx Cloud Storage

Tigris

FileLu S5

Petabox

Zata

Filebase

Frequently Asked Questions

Related Guides

Get Blober

Storj

Filebase

4everland

Akave

How the Gateway Pattern Works

Frequently Asked Questions

Related Guides

Get Blober

NetApp StorageGRID

NetApp ONTAP S3

Dell ECS and ObjectScale

Cloudian HyperStore

Pure Storage FlashBlade

Hitachi Content Platform (HCP)

Spectra Logic BlackPearl

Scality RING and ARTESCA

Quantum ActiveScale

DataCore Swarm (formerly Caringo Swarm)

Nutanix Objects

VAST Data

WekaFS (Weka)

Zadara