What this page is
CloudFiles appears in every comparison this blog publishes, so its own evidence lives here once instead of being restated in each one. Every head-to-head evidence post links back to the relevant section below for the full detail behind CloudFiles' score; the post itself carries only the score and the one fact that explains the difference.
CloudFiles sits on the same two-axis matrix as every product we compare, scored from the same weighted signals and Data Reliability check. For the method and each Enterprise Readiness item, see How We Compare Salesforce Document Apps; each feature is defined in How We Score Salesforce Document Management Apps.
Enterprise Readiness (X)
Scored 1–5 on how enterprise-oriented CloudFiles' product, sales and customer base are, from four weighted signals. Evidence is from CloudFiles' own site unless an item says otherwise.
Observed buyers
Who buys CloudFiles, judged from sources outside our own marketing: the organisations our AppExchange reviewers work for, and the customers we name in case studies and on logo walls.
AppExchange reviewer company sizes
Who buys CloudFiles, judged by where its AppExchange reviewers work.
Ten of CloudFiles' most-recent Document Management reviews were read (all 5★). All ten reviewers were matched to a real, named LinkedIn profile by cross-checking name, role and review date. No reviewer named their own employer inside the review text itself. Company size was confirmed for seven of the ten, including a Data Architect at a large Indian IT-services firm (10,001+) and an IT Technical Support Manager at a major US financial-services firm (10,001+); the remaining three resolved to a real person but too weakly linked to a company size to count.
The majority of reviewers who could be identified work at large organisations.
Identification is by public profile match, not a verified account link; several matches are plausible rather than certain.
Last read on 2026-09-22Source – 1
Named customers: modal profile
The most common profile among the customers CloudFiles names in public.
Twenty named customers appear across its homepage, product pages and seven case studies (three named, four anonymous by sector). Fourteen of the twenty, including a global food manufacturer, a business-information provider, an insurer, a financial-services co-operative and an industrial manufacturer, are enterprise or regulated organisations; two are mid-size and one is small.
A clear enterprise-modal profile.
Twenty sized names is enough to read a modal profile.
Where this leaves Observed buyers: Both signals point the same way: CloudFiles reads as enterprise-ready on who buys it and who it names as a customer.
| Metric | Score | Confidence |
|---|---|---|
| AppExchange reviewer company sizes | 4 · Leans high | Medium |
| Named customers: modal profile | 5 · Highly ready | High |
Commercial & service design
The commercial side of CloudFiles: how the Salesforce product is priced and packaged, the support customers can reach on each plan, and where CloudFiles appears across Salesforce's event calendar.
Pricing unit and tiers
CloudFiles' billing unit and tier structure, and what sits behind an enterprise ask.
CloudFiles' Salesforce line publishes no price: a single Enterprise plan per product, licensed per org or per user and sold through "Contact Us", with no tier, gate, minimum or trial stated. Pricing that goes through sales is a standard enterprise-software technique, chosen when deployments vary too much in scope for a flat seat price. CloudFiles also targets SMB customers through its HubSpot product, which has its own self-serve pricing; that line is not considered here.
Sales-led, quote-only pricing is a standard enterprise-software technique, so it reads Leans high even with no published figures.
The Salesforce line states no figures; only the separate line covers this product's own pricing.
Customer support
How customers reach CloudFiles support, and what's promised on each plan.
Live chat, email and free 45-minute scheduled onboarding calls are offered on every paid plan. No response time, severity tier, named account manager or premium support option above the standard offering is published anywhere.
Three channels, two of them real-time, on every plan: a strong offering, though nothing sits above the standard tier.
Support options come straight from CloudFiles' own pages, with nothing to corroborate and no figure to check, so Confidence isn't scored.
Conference and webinar presence
CloudFiles' presence at Salesforce events and in its own webinars.
CloudFiles has exhibited at six Salesforce flagship events in two years: Dreamforce 2024, 2025 and 2026, and the Agentforce World Tours in New York (2025 and 2026) and London (2025), usually with a booth and a theatre session. Salesforce's own Dreamforce account posted on LinkedIn that CloudFiles showcased end-to-end automation at World Tour New York.
Repeated flagship sponsorships with booths and theatre sessions are the rule's high case.
Salesforce's own Dreamforce account confirms one of the six events; the rest rest on CloudFiles' event pages and staff posts, with booth and session detail for five.
Where this leaves Commercial & service design: CloudFiles reads strongest on conference presence, with six flagship events and a Salesforce post confirming one; its pricing and support scores lean high but stop short of sFiles' published, gated Enterprise structure.
| Metric | Score | Confidence |
|---|---|---|
| Pricing unit and tiers | 4 · Leans high | Medium |
| Customer support | 4 · Leans high | N/A |
| Conference and webinar presence | 5 · Highly ready | Medium |
Technical design
The engineering and assurance behind CloudFiles: the certifications and controls that back its security claims, the documentation customers and developers rely on, and the document tools offered beyond file management.
Security & Compliances
CloudFiles' security certifications and the documents that back them.
CloudFiles says it is independently audited for SOC 2 Type II (report under NDA), holds ISO 27001, 27017 and 27018 certification, HIPAA compliance with BAAs for enterprise customers, and GDPR compliance backed by a public DPA and standard contractual clauses. Data residency options span the US, EU, UK and Australia, with TLS 1.2+/1.3 in transit and AES-256 at rest.
An audited SOC 2 Type II report, ISO and HIPAA certification, a public DPA and a Trust Portal together meet the rule's high bar.
The public DPA and an available Trust Portal are checkable outside CloudFiles' own word; the SOC 2 report itself is NDA-gated and no auditor or registry is named, which keeps this from going higher.
Help-doc architecture
The depth and organisation of CloudFiles' public help centre.
CloudFiles' help center spans 492 indexed pages across setup, admin, permissions, security and compliance, developer reference and release notes, with a searchable index and a 41-entry changelog. No page is dedicated to SSO.
Every documentation area the rule looks for is covered bar a dedicated SSO page, and the page count is the highest measured.
An exact page count, taken from the published sitemap and index.
API depth and gating
The developer surfaces CloudFiles publishes, and whether any plan restricts them.
CloudFiles publishes a REST API (20 endpoints across 7 groups) and an Apex client (60+ methods, plus platform events for files, resources, generation and AI), all ungated on every plan.
A REST API and an Apex client, open on every plan, is exactly what the rule scores highest.
The endpoint and method counts are CloudFiles' own published figures.
Document stack coverage
The document tools CloudFiles offers beyond file management.
CloudFiles ships document generation, document AI, migration tooling and a Sharing Add-On with link controls, engagement analytics and multi-storage datarooms, all in the product. AppExchange separately lists Document AI, Document Generation and an Agentforce app as CloudFiles' own listings, alongside Document Management. The one pillar missing is native e-signature.
Four of the five adjacent pillars are covered; e-signature is the only gap.
Two of the four pillars, Document AI and Document Generation, are confirmed independently by their own AppExchange listings.
Where this leaves Technical design: CloudFiles reads uniformly strong: compliance, documentation, API depth and document-stack breadth all land at Highly ready.
| Metric | Score | Confidence |
|---|---|---|
| Security & Compliances | 5 · Highly ready | High |
| Help-doc architecture | 5 · Highly ready | High |
| API depth and gating | 5 · Highly ready | High |
| Document stack coverage | 5 · Highly ready | High |
Messaging & ecosystem
What CloudFiles says about who it is for, and how that shows up elsewhere: the audience its marketing targets, the partners it works with, its team's mix and reach, and its review-site profiles.
Stated ICP and messaging focus
The industries and personas CloudFiles' own marketing targets.
CloudFiles names 19 target verticals on its homepage and Salesforce product page, including Financial Services, Healthcare & Life Sciences, Manufacturing, Government and Retail, alongside named customers, use cases (KYC verification, quote generation, compliance audit trails) and named integrations. No single vertical or persona is presented as the primary focus.
19 target verticals is "sell to everyone" breadth, spanning multiple segment types, not a focused enterprise niche.
The claim is precise even though the focus is wide.
Partner ecosystem
The partners CloudFiles works with, and who confirms the relationship.
CloudFiles runs a formal partner programme for Salesforce and HubSpot, with referral, implementation, reselling and OEM tracks, commissions and a four-step onboarding. Its partner page names nine implementation partners, three of them with staff quoted by name (Wunderbricks, CloudForia and Sitetracker), and lists Accenture, Deloitte, KPMG, Capgemini, HCLTech and Slalom as global firms it has worked alongside on shared customer projects. The one relationship confirmed on the partner's own channels is an IT consultancy whose blog walks through integrating CloudFiles with Salesforce, and which called itself "a partner of CloudFiles" in a conference social post.
A formal programme with several named partners reads Leans high, though its tracks are partner types rather than ranked tiers. The Big Four and global integrators are named as firms CloudFiles delivered alongside, not as partners, and none confirms it, so they do not lift the score to Highly ready.
Ten partners are named, so Precision is high, but only one confirms the relationship on its own channels; none of the nine on CloudFiles' page or the six global firms was found saying so.
Team mix
The functions and regions visible in CloudFiles' LinkedIn headcount.
CloudFiles lists 32 associated LinkedIn members, with Business Development, Marketing and Sales together making up 47% of the top five functions shown. The team is distributed across multiple regions globally, giving it round-the-clock coverage rather than a single time zone.
Strong Sales/BD/Marketing presence plus a globally distributed team gives round-the-clock coverage, regardless of the team's small absolute size.
Both the headcount band and the function split are read straight off CloudFiles' LinkedIn page.
Review-site profile richness
CloudFiles' presence across the three main B2B review sites.
CloudFiles' G2 profile is claimed and actively maintained, with a product video, 6+ images, several categories, a Top-Rated Alternatives comparison and 227 reviews. CloudFiles' Capterra listing dates from its earlier HubSpot product: 6 reviews at 4.8 stars, describing file sharing and tracking rather than the Salesforce app. A TrustRadius profile exists but is thin, at one review.
Real presence on all three platforms: a rich G2 profile, and thin but real Capterra and TrustRadius listings.
This item counts where CloudFiles has a profile rather than grading a claim, so neither Precision nor Corroboration applies.
Where this leaves Messaging & ecosystem: CloudFiles leans high: profiles on all three review sites and a broad, multi-region team and a partner programme with several named partners, only one of which confirms it, outweigh a broad, "any team" ICP claim.
| Metric | Score | Confidence |
|---|---|---|
| Stated ICP and messaging focus | 3 · Mixed | High |
| Partner ecosystem | 4 · Leans high | Low |
| Team mix | 5 · Highly ready | High |
| Review-site profile richness | 4 · Leans high | N/A |
Functionality (Y)
CloudFiles feature by feature, on the same Absent-to-Extended ladder every product is measured against. Cards show the rung reached and the reason for it, the Kano class, and an automation rating where one applies, all read from CloudFiles' own help documentation and product pages.
Storage Support
How CloudFiles works with the storage behind it: the platforms it reaches, the storage-specific features it can control, and how users browse the library and find files from Salesforce.
Storages Supported Kano · Dealbreaker
The storage platforms CloudFiles reaches, checked against the three ecosystems most customers run.
CloudFiles' help documentation names ten storage backends (SharePoint, OneDrive, Microsoft Teams and Azure Blob for the Microsoft ecosystem, Google Drive, and AWS S3 for Amazon) plus Box, Dropbox, SFTP Library and Azure Files beyond the three ecosystems the ladder requires. Two marketing pages corroborate a five-provider subset of the same list.
All three major ecosystems are covered, which is the Complete bar, and Box, Dropbox and SFTP on top take it to Extended.
A single storage parameter in both Flow and Apex spans seven backends, and events identify the storage behind each file, which goes past covering one platform; SFTP, Azure Files and Teams aren't confirmed.
Storage Depth Kano · Dial
How far CloudFiles reaches into storage-specific features instead of treating every storage alike.
Storage-specific controls are documented on three storages. On SharePoint, Flow actions create sites and drives from templates and search on SharePoint properties. On Google Drive, both My Drive and shared drives are supported, each addressed by its drive ID. On AWS S3, one bucket can serve several Salesforce orgs through separate folder prefixes, and changes in the bucket sync automatically. Much of each storage's own feature set is still not covered: SharePoint content types, the term store and document sets; S3 storage classes, encryption keys and object versioning; and nothing storage-specific is documented for Box, Dropbox or the other backends.
Real storage-specific control on SharePoint, Google Drive and S3 from inside Salesforce, but Complete asks for most storage-specific features on each storage supported, and each of the three covers only a part of its own.
SharePoint sites and drives can be created from templates, with design, language, admins and column defaults, from Flow or Apex, well beyond editing what already exists.
Browse Library Kano · Delighter
Whether CloudFiles opens up the entire library, and what can be done there.
A standalone Content Library tab browses six storage providers with nested folders; List Actions add checkbox-based bulk selection on top of the same file operations.
Browsing with file and folder operations covers Complete, and checkbox bulk selection is the extra that takes it to Extended.
Browsing happens on screen, so there's nothing here for a flow or code to do.
Search Kano · Dial
How CloudFiles search works inside Salesforce, and what it can filter on.
Beyond a sub-folder-aware search bar, a documented Flow action searches by resource metadata, filtering results by tag rather than filename alone.
Tag and metadata filters go beyond keyword matching, which is what earns the top rung.
Property-based search runs in Flow and Apex, and the REST API adds keyword search across twelve storages; keyword search from Flow or Apex itself would lift it to Extended.
Where this leaves Storage Support: CloudFiles reaches Extended on breadth, library browsing and search. Storage depth is its weak spot: storage-specific control stops at SharePoint site templates and property search. Automation reaches Extended on breadth and depth, and Complete on search.
| Feature | Kano | Rung |
|---|---|---|
| Storages Supported | Dealbreaker | L5 · Extended |
| Storage Depth | Dial | L3 · Limited |
| Browse Library | Delighter | L5 · Extended |
| Search | Dial | L5 · Extended |
Basic Ops
The routine file work CloudFiles handles inside Salesforce, from getting files into storage and back out again to previewing, opening, renaming, deleting and relocating them.
Ingestion Kano · Dealbreaker
How CloudFiles puts files and folders into connected storage.
Whole-folder drag-and-drop upload is backed by dedicated batch and async Flow automation, going beyond a single manual upload. Upload widgets accept every file type by default and can be limited to chosen formats, such as PDF or DOCX.
Folder uploads and batch automation are exactly the extras the top rung asks for.
Beyond plain upload and folder creation from Flow and Apex, it adds asynchronous folder creation, batch copies of Salesforce Files and choices for duplicate names.
Last read on 2026-09-24Sources – 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
Preview Kano · Delighter
What CloudFiles shows when a user opens a file without downloading it.
Inline preview inside Salesforce is the default, with thumbnails and an allowDownload control on the preview API. CloudFiles' documentation names the formats its viewer opens in the browser (PDF, PowerPoint, Word, Excel and video); other files, such as zip and .exe, download only.
An inline viewer inside Salesforce clears Complete; thumbnails and the download control are what push it to Extended.
Looking at a file is a person's job, not something to automate.
Last read on 2026-09-24Sources – 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
Original Access Kano · Dial
How quickly CloudFiles gets a user to the source file or folder.
A one-click Open in External Storage action covers files and folders, and a separate Open in Folder jump reaches storage directly. An App/Library toggle exists, but choosing the target editor is undocumented.
Files and folders both open in storage in one click, which meets Complete; a documented choice of target editor is what Extended would add.
Jumping to the source file is an interface action with nothing to automate.
Last read on 2026-09-08Source – 1
Download Kano · Dealbreaker
Pulling files out of connected storage through CloudFiles.
Single files download with no type or size limit, and a multi-select bulk action downloads several files or whole folders at once, shown in the documentation's own screenshots.
Single-file download with no limits is Complete; downloading whole folders or many files at once earns Extended.
Scored as a person retrieving a file, so automation isn't rated.
Last read on 2026-09-08Source – 1
Rename Kano · Delighter
Changing file and folder names in storage through CloudFiles.
Rename is a native dropdown action for both files and folders. CloudFiles' own documentation limits it to one item at a time, so there is no bulk rename. CloudFiles can also be extended with List Actions, custom widget buttons that run a Salesforce Flow on several selected files or folders at once, which an admin can use to build a bulk rename; as a customer-built extension it does not change the rung.
Both files and folders rename natively, which meets Complete; renaming one item at a time rules out Extended, which looks for bulk rename.
Flow, Apex and the REST API all rename files and folders; with nothing beyond a plain rename, it stops at Complete.
Delete Kano · Delighter
How CloudFiles deletes files and folders in connected storage.
Both files and folders can be deleted permanently from the record widget, as a demo in the documentation shows. Bulk delete is deliberately left out of the widget's multi-select menu. CloudFiles can also be extended with List Actions, custom widget buttons that run a Salesforce Flow on several selected files or folders at once, which an admin can use to build a bulk delete, the example CloudFiles' own feature page gives; as a customer-built extension it does not change the rung.
Files and folders can both be deleted, which is Complete; without bulk delete it stays a rung below the top.
Deletes run from Flow and Apex, including whole SharePoint drives and many items in a single Apex call.
Move / Copy Kano · Delighter
How CloudFiles moves and copies content between locations.
Files and folders move singly or in bulk, with a destination picker and options for handling name conflicts. Copy is available only as a Flow action, and no move between two different storages is documented. CloudFiles can also be extended with List Actions, custom widget buttons that run a Salesforce Flow on several selected files or folders at once, which an admin can use to build a bulk copy; as a customer-built extension it does not change the rung.
Single and bulk moves with a choice of destination and conflict handling meet Complete; copy only through Flow, and no moves between storages, hold it there.
Move and copy run in Flow and Apex on files and folders, and Apex can also move items between drives, which goes beyond a plain move.
Where this leaves Basic Ops: CloudFiles reaches Extended on both Dealbreakers, Ingestion and Download, and on Preview. The other four stop at Complete, each for a documented reason: no choice of editor when opening the original, no bulk rename or delete, and copy only through Flow. Automation reaches Extended on Ingestion, Move / Copy and Delete, and Complete on Rename.
| Feature | Kano | Rung |
|---|---|---|
| Ingestion | Dealbreaker | L5 · Extended |
| Preview | Delighter | L5 · Extended |
| Original Access | Dial | L4 · Complete |
| Download | Dealbreaker | L5 · Extended |
| Rename | Delighter | L4 · Complete |
| Delete | Delighter | L4 · Complete |
| Move / Copy | Delighter | L4 · Complete |
Advanced Ops
What CloudFiles offers beyond the basics: editing documents, surfacing version history, enforcing and managing storage permissions, reading and writing file metadata, and two-way sync with storage.
File Edit Kano · Delighter
Where a CloudFiles user ends up when they edit a file.
The Edit button opens the file in the cloud drive's own editor. No dialog or inline editor inside Salesforce is documented, and Replace uploads a new file rather than editing the existing one.
One click gets the user to an editor, but editing happens in the storage's editor rather than inside Salesforce, which is what Complete requires.
Changing a document's contents happens in an editor, by a person.
Versioning Kano · Distractor
Whether CloudFiles exposes a file's earlier versions.
The file widget has no version button or history view. Version history is reached by opening the file in its external storage.
The history exists but lives only in the storage; even an explicit version button that redirected there would be needed for the next rung.
The feature is viewing history on screen, so automation doesn't come into it.
Permissions Kano · Dealbreaker
How CloudFiles respects and manages storage permissions for each user.
More than ten Salesforce custom permissions can be assigned, on top of enforcing each user's own storage permissions. Permissions are updated through a manual Flow action rather than kept in sync automatically.
Granular, manually controllable permissions from the Salesforce side meet Complete; automatic sync between Salesforce and storage permissions, which Extended asks for, isn't there.
Owner, read or write access can be granted or revoked in Flow and Apex across nine storages, at site, drive, folder or file level, for users or groups.
Metadata Kano · Delighter
How CloudFiles handles the properties stored alongside a file.
A View Metadata dialog shows a file's properties, and Get and Set Resource Property actions read and write them. For column types the storage API can't set, the documentation gives a manual workaround.
Reading and writing metadata is the Complete bar; a documented route around the storage API's limits is what lifts it to Extended.
Metadata can be read and searched from Flow and Apex, but Flow writes to SharePoint are limited to text and yes/no columns, so writing is only partly covered.
2-way sync Kano · Delighter
Whether a change on either side shows up on the other through CloudFiles.
Three of CloudFiles' own pages describe instant two-way sync for files and folders. Sync controls and logs aren't documented.
Sync in both directions for files and folders is Complete; happening instantly is what makes it Extended.
Sync runs on its own already, leaving no separate automation to rate.
Where this leaves Advanced Ops: CloudFiles reaches Extended on Metadata and 2-way sync, and Complete on Permissions, the category's Dealbreaker. Editing and versioning both lean on the storage's own tools, which keeps them at Limited and Workaround. Automation reaches Extended on Permissions but only Limited on Metadata, where Flow writes accept just two SharePoint column types.
| Feature | Kano | Rung |
|---|---|---|
| File Edit | Delighter | L3 · Limited |
| Versioning | Distractor | L2 · Workaround |
| Permissions | Dealbreaker | L4 · Complete |
| Metadata | Delighter | L5 · Extended |
| 2-way sync | Delighter | L5 · Extended |
Salesforce Support
Where CloudFiles runs beyond the standard Lightning desktop: in Experience Cloud portals for customers and partners, in orgs still on Salesforce Classic, and inside the Salesforce mobile app.
Experience Cloud Support Kano · Delighter
What CloudFiles offers customers and partners inside an Experience Cloud portal.
Portal users can upload, preview, download, edit and replace files, and create and rename folders, through an included Experience Cloud widget; access runs through an integration user, so no storage licence is needed per external user. Admins can switch seven actions on or off for each user, and views and downloads of shared files are tracked.
Upload, download and preview would be Complete; editing by portal users, per-user action controls and view tracking each go beyond it. Branded sharing isn't evidenced, but the rung doesn't need it.
Share, unshare and list actions for portal users exist in both Flow and Apex, which covers the task without going further.
Classic Support Kano · Distractor
CloudFiles' support for orgs that haven't moved to Lightning.
A help article updated in July 2026 documents a Visualforce page that renders the widget in Classic with the same look and behaviour as in Lightning. No source says parity is kept across releases, or covers custom Visualforce pages and Classic buttons.
The documentation says Classic gets the same widget as Lightning, which is full parity with documented setup; embedding in custom Visualforce pages and buttons would be the next step.
A question of which interface renders, not of automation.
Mobile Compatibility Kano · Distractor
What CloudFiles does inside the Salesforce mobile app.
The AppExchange listing declares iOS and Android support, and the help centre says CloudFiles is optimised for the Salesforce mobile app and Field Service Mobile, with steps to add it as a mobile action. No source lists which operations (browse, preview, upload, share) work on a mobile layout.
Without a documented list of what works on a phone, the core mobile operations can't be credited, which keeps it below Complete.
About rendering in the mobile app rather than running anything automatically.
Where this leaves Salesforce Support: CloudFiles reaches Extended on Experience Cloud and Complete on Classic. Mobile sits at Limited because no source lists what works on a phone. Automation reaches Complete on Experience Cloud, with dedicated share, unshare and list actions.
| Feature | Kano | Rung |
|---|---|---|
| Experience Cloud Support | Delighter | L4 · Complete |
| Classic Support | Distractor | L4 · Complete |
| Mobile Compatibility | Distractor | L3 · Limited |
Industry Cloud Support is left out of this scoring.
Data Reliability
How much of CloudFiles' record is public, independently published and precise, across the 32 items above. CloudFiles' record comes out Well documented, at 83%.
| Component | CloudFiles |
|---|---|
| Coverage: is it public at all? | 97% |
| Independence: who publishes it? | 64% |
| Precision: is it a checkable fact? | 89% |
Coverage and Precision are high: nearly everything scored is public and stated as a specific fact. Independence is the lowest of the three. Fifteen of the nineteen features now have an independent source, from customer reviews on AppExchange or consultancy write-ups, but Classic Support, Delete, Download and Original Access still rest on CloudFiles' own documentation.