We built this because of a bill.
A file storage account starts at twenty dollars a month. Nobody negotiates it; it is too small to negotiate. Then the folder tree grows, the share links go into email signatures and client onboarding docs, and three years of structure accumulates that nobody wants to rebuild.
That is the moment the price moves. Not by ten percent. By a multiple. And it keeps moving, because the vendor has correctly worked out that migrating is more expensive than paying.
By the time it is a thousand dollars a month, the product has not improved. What changed is that leaving got harder.
This is not pricing. It is a toll on work you have already done, collected because you cannot easily stop paying it.
We are not going to name the vendor. We do not have the invoices any more, and the specific company matters less than the pattern - which is common enough that most people reading this recognise it without being told who.
Illustrative, not attributed to any single vendor.
Four promises, and how you would catch us breaking them.
Anyone can promise not to do this. What follows is each promise, the thing in the product that enforces it, and what you should watch for.
- 01Promise
One price for the whole workspace.
MechanismMembers are not metered. There is no seat count in the billing system to increase, because seats are not a billable unit.
How you'd catch usA per-user line item appearing on an invoice. A "seats" field in your billing settings. Any pricing page with a "per user / month" figure on it.
- 02Promise
One plan. No tier above you.
MechanismThere is one paid plan. Every feature is on it - permissions, versioning, audit logs, branding, connected storage.
How you'd catch usA feature you already use moving behind an upgrade. A comparison table appearing on our own pricing page with three columns.
- 03Promise
We cannot bill you for storage you did not switch on.
MechanismAdditional storage is off by default and requires an affirmative action to enable. Until you take it, there is no mechanism to charge you for it.
How you'd catch usA storage charge you did not authorise. Any billing change that makes extra capacity opt-out rather than opt-in.
- 04Promise
If you leave, you leave with your files.
MechanismThirty days of export access after cancellation, written into the Terms rather than offered as a courtesy. Or connect your own storage bucket from the start, in which case the files were never on our infrastructure to hold.
How you'd catch usExport access ending sooner than the Terms say. Any change that makes leaving harder than arriving.
The export commitment is in Terms § 12 and § 20. Keeping the files on storage you already own is connecting your own bucket.
The things a page like this usually leaves out.
Every company's About page lists what it does. This is the other list. If any of it is a dealbreaker, we would rather you found out here than three weeks into procurement.
- 01 · Attestations
We are not SOC 2 audited, and we are not close.
A SOC 2 Type II report requires a completed independent audit over an observation period. We have not started one. It is expensive, and we would rather tell you that than imply otherwise.
Our infrastructure runs on providers who hold their own SOC 2 attestations. That is their audit, not ours, and we will not present it as ours. What we can offer is specificity: the security measures we commit to contractually are published in full, and we will answer a security questionnaire in detail.
- 02 · Encryption
We can read your files.
Your files are encrypted at rest with AES-256 and in transit with TLS 1.3. That protects them from someone intercepting traffic or walking off with a disk.
It does not mean we cannot see them. We hold the keys. End-to-end encryption - where only you hold the key and we are mathematically unable to read your content - is a different thing, and we do not have it. We are not going to describe ourselves as end-to-end encrypted, because the features you are paying for depend on us being able to read the file: version history, previews, search, and connecting your own bucket all require it.
If your threat model requires that your vendor genuinely cannot read your data, we are the wrong product and you should buy a zero-knowledge one.
- 03 · Health data
We are not a HIPAA solution.
Protected health information may only be uploaded under a Business Associate Agreement executed with us. Absent one, we are not your business associate and the Service is not configured for PHI.
- 04 · Uptime
There is no service level agreement.
The Service is provided as-is. We do not publish an uptime commitment or offer service credits. When something breaks we tell you by email.
- 05 · Track record
We are new, and small.
If you need a vendor with a decade of references and a named account team, that is a reasonable requirement and we do not meet it.
The company
FileBackerz.com, LLC is a Texas limited liability company registered at 3723 Greenville Avenue, Suite 19910, Dallas, Texas 75206. That is the entity on your invoice, the entity bound by the Terms, and the entity liable under them.