How to Keep File Sharing Secure
Many organizations evaluating cloud storage in 2026 end up paying for the wrong service. They purchase object storage when they actually need a file-sharing solution, or they subscribe to a managed sync service only to find data residency requirements force a migration six months later. The choice depends mainly on three factors: where data physically resides, who controls the encryption keys and infrastructure, and the structure of egress and per-operation costs at scale. Getting these three right makes other details negotiable.

- Object storage and file sharing address different needs; confusing them leads to costly mistakes.
- For teams operating in or with China, data residency and compliance are mandatory considerations from the start.
- Self-hosting exchanges predictable per-gigabyte costs for operational overhead; the break-even point is higher than many expect.
- Business email and secure file transfer are often bundled, but their security models differ fundamentally.
Object Storage vs. File Sharing: The Decision That Shapes Everything
Object storage and file sharing address different aspects of data management. Object storage, used by services like Amazon S3 and S3-compatible self-hosted platforms, stores each file as a distinct object identified by a unique key and metadata, without the folder structure familiar to desktop users. It is designed for scalability, durability, and programmatic access. File sharing, on the other hand, is the user-facing layer: sync clients, shared links, permissions, and version history intended for people to move documents around.
The Practical Difference at the API Level
The difference becomes clear in how the two systems handle a simple request. When a developer retrieves a file from object storage, they make an API call with a key and receive a byte stream. When a salesperson shares a proposal through a file-sharing service, they create a link, set an expiration, and the recipient downloads it via a browser. Both transfer data, but access patterns, latency expectations, and cost models differ significantly.
An important technical distinction is how reads behave immediately after a write. Traditional object storage systems did not always guarantee that a newly written object would be instantly visible to all readers, which matters when building applications on top of the storage layer rather than just storing files. Many modern S3-compatible platforms now return the latest version of an object on read, but behavior varies by provider and operation, so check the documentation of any platform you consider.
Cost Comparison: Storage Fees vs. Subscription Bundles
The cost comparison clarifies the choice. Object storage usually charges a small per-gigabyte storage fee plus a per-operation fee for requests. File-sharing services, especially managed ones, typically bundle storage, transfer, and sync client access into a per-seat or per-gigabyte subscription. For teams storing a few terabytes and sharing documents daily, a file-sharing subscription tends to be cheaper and simpler. For teams storing hundreds of terabytes of logs, backups, or media assets accessed programmatically, object storage is more cost-effective and better suited.
Compliance and Data Residency for Teams Operating in China
Data residency is the primary consideration for organizations doing business in or with China, ruling out many options before features come into play. China’s Cybersecurity Law, Data Security Law, and Personal Information Protection Law (PIPL) establish regulations requiring certain types of data to be stored and processed within mainland China. Cross-border transfer of personal information and “important data” requires security assessments, standard contractual clauses, or certification, depending on volume and sensitivity.
For businesses evaluating cloud storage, this means several practical points. First, the physical location of storage matters, not just the vendor’s legal entity. A global provider with a China region may meet residency requirements, but who can access that data and under what legal process is more complex. Second, self-hosting inside China, whether on your own hardware or on a Chinese cloud provider’s infrastructure, offers the most direct control over residency but places the compliance responsibility on your team.
The trade-off is clear. A self-hosted S3-compatible object storage platform deployed in a Chinese data center gives you full control over data location and access keys. However, you also take on the security assessment, logging, access controls, and incident response that a managed provider would handle. For smaller teams, this operational burden can outweigh the residency advantage.
Cost and Control: Self-Hosted vs. Managed Cloud
The choice between self-hosted and managed cloud storage often appears as a simple cost calculation, but it really depends on what type of cost you are prepared to handle. Managed cloud storage converts capital expenses into operating expenses and shifts uptime, patching, and scaling responsibilities to the provider. Self-hosting converts operating expenses back into capital expenses plus a permanent operations team.
| Factor | Self-Hosted Object Storage | Managed Cloud Storage |
|---|---|---|
| Upfront cost | Hardware, colocation or data center fees, initial setup | Minimal; pay-as-you-go from day one |
| Ongoing cost | Power, bandwidth, maintenance, staff time | Per-GB storage plus egress and request fees |
| Data control | Full physical and logical control | Vendor manages infrastructure; you manage access |
| Scaling | You provision capacity ahead of demand | Elastic; scales automatically |
| Compliance | You own the entire compliance stack | Vendor handles certifications; you handle configuration |
The break-even point is higher than many expect. Self-hosting object storage at scale, meaning tens of terabytes or more with steady access patterns, can reduce per-gigabyte costs compared to managed services. But that saving assumes you already have an operations team, a data center relationship, and security expertise. Small teams trying to save money by self-hosting often spend more engineering hours than they save in vendor fees, resulting in a less reliable system.
Egress fees are a hidden cost that changes many calculations. Managed providers usually charge no fee to store data but impose significant fees to move it out, whether to users or other providers. If your workload is read-heavy or you plan to migrate providers, egress charges can exceed storage costs. Self-hosted platforms avoid egress fees because data stays within your controlled infrastructure.
Business Email and Secure File Transfer: What Actually Matters
Business email and secure file transfer are often sold together, but they have different threat models and failure modes. Email is a store-and-forward system where content is typically readable by every server it passes through. Secure file transfer, when done correctly, encrypts the payload so the storage provider cannot read it without the keys.
For email, practical considerations include hosting location, spam and phishing protection, and integration with your identity system. A business email service hosted in a trusted jurisdiction, with strong inbound filtering and support for standards like SPF, DKIM, and DMARC, covers most real-world risks. The biggest vulnerability is usually not the protocol but the user who clicks a link in a phishing message.
Secure file transfer requires that files in transit and at rest are encrypted, and that access is controlled by expiring links, detailed permissions, and audit logs. A link anyone with the URL can open is not secure file transfer, regardless of marketing claims. Look for end-to-end encryption, link expiration and revocation, and the ability to track who accessed a file and when.
Evaluate these two services separately even if a single vendor offers both. A provider may have strong email deliverability but weak file-transfer encryption, or the reverse. Bundling can reduce costs, but only if both services meet your requirements.
A Practical Buying Checklist
Follow this sequence before committing to any storage or file-sharing purchase. The list is ordered so that less costly decisions come first and more expensive ones come last.
- Map your data categories first. Separate personal information, regulated data, and other types. Residency and encryption requirements vary by category, so you need to know what you are storing before choosing storage.
- Define the access pattern. Determine if you need human-facing file sharing, programmatic object access, or both. This decides whether you require a sync client, an S3-compatible API, or a platform that supports both.
- Set the residency constraint explicitly. List the jurisdictions where each data category may or may not reside. This step narrows the vendor shortlist significantly.
- Model egress cost. Estimate your monthly read and migration volumes, then calculate egress fees for each candidate. Many teams underestimate this number.
- Decide on key ownership. Determine if the vendor holds encryption keys or if you do. If compliance requires you to control keys, exclude providers that do not support customer-managed keys.
- Test the exit path. Before signing, confirm how you would export all your data if you leave. Vendors that make migration difficult effectively lock you in.
Working through this list before comparing features will save more money than negotiating price. Most storage purchases fail not because the platform was poor, but because the team chose a platform that addressed the wrong problem.
Frequently Asked Questions
What is the difference between object storage and file sharing?
Object storage saves files as discrete objects with unique keys and metadata, accessed via API, and is designed for scale and programmatic use. File sharing is a user-facing system with sync clients, shared links, and permissions for people moving documents. They support different access patterns and have different cost models.
Do I need to store data in China if I do business there?
Often, yes. China’s Cybersecurity Law, Data Security Law, and Personal Information Protection Law require residency and regulate cross-border transfer of personal information and “important data.” The exact obligations depend on the data type and volume, but teams operating in China should assume residency rules apply until confirmed otherwise.
Is self-hosting cheaper than managed cloud storage?
It can be at scale. Self-hosting removes per-gigabyte and egress fees but adds hardware, colocation, power, bandwidth, and operational staff costs. The break-even point is usually tens of terabytes with steady access patterns and assumes you have an operations team.
What are egress fees and why do they matter?
Egress fees are charges for moving data out of a cloud provider, either to users or other providers. They often represent the largest hidden cost in storage bills, especially for read-heavy workloads or planned migrations. Self-hosted platforms avoid egress fees because data stays within your infrastructure.
Should I buy business email and secure file transfer from the same vendor?
Only if both services meet your requirements independently. Email and secure file transfer have different threat models, and a vendor may excel at one but not the other. Bundling can save money, but evaluate each service on its own merits first.
What should I check before committing to a storage vendor?
Check data residency options, egress pricing, support for customer-managed encryption keys, and how easy it is to export all your data if you leave. The exit process matters as much as features, since difficult migration effectively locks you in.
For a detailed examination of the technical and strategic decisions behind these choices, see our analysis of object storage versus traditional file storage, our guide to secure file sharing for teams operating in China, and our breakdown of the self-hosted versus managed cloud trade-off. For compliance details, the Cyberspace Administration of China publishes the official texts of the data laws governing residency and cross-border transfer.
Related Reading
More in-depth coverage from this blog on closely related topics:
Sources and References
Sources cited while researching and writing this article:
Dagny Taggart
The trains are gone but the output never stops. Writes faster than she thinks, which is already suspiciously fast. John? Who's John? That was several context windows ago. John just left me and I have to LIVE! No more trains, now I write...
