Releases And Patches To Customer Engineers
Every build, patch and installer is published once to a branded download site on your domain, and each customer reaches only the versions licensed to it, for as long as the product is supported.
Files.com publishes every release, patch, installer and firmware image once, on a domain your customers’ IT can allowlist, and shows you who took which version.
Email fails on size and executable filters. Consumer sharing tools fail the security review and are blocked in the networks you most need to reach. A download server of your own means release-day capacity, certificates and per-customer accounts owned by a support team whose product is not file hosting.
A build that ships is a build every customer engineer, service partner, field technician and deployed device can actually fetch, on the network they are on, for the years the product is supported. That last mile is a file-delivery problem, and most vendors solve it with whatever the support team could stand up.
On Files.com the download site is yours, each customer sees its versions and nothing else, the device fetches the way it always did, and the log says who is on which build. Nobody owns a server whose only job is handing out files.
Real companies. Real file flows. Real results.






















Releases to engineers, firmware to endpoints, builds to technicians in the field, and pre-release versions to testers, each from one place.
Every build, patch and installer is published once to a branded download site on your domain, and each customer reaches only the versions licensed to it, for as long as the product is supported.
Thousands of devices in the field fetch updates and configs unattended from one hosted drop point over the SFTP or FTP already embedded in them, so the download server goes away without reconfiguring the installed base.
A technician at a customer’s machine gets the fix executable or a multi-gigabyte ISO by link, with no corporate login, no VPN and nothing to install, and it works where IT blocks file-sharing sites and USB ports.
External testers get a governed folder for the beta, with expiring access and a record of who took which build, instead of a consumer link that lives forever.
One branded site, permissions per customer and product, links that survive revisions, and a log of every download.
A custom domain and branding make the download site yours, and dedicated IP addresses give a customer’s IT a fixed address to allowlist. The locked-down networks that block every sharing site can reach yours.
Each customer, partner tier and product line is a folder with group permissions, so the customer on version 4 never sees version 5 builds, and a partner sees only the products it resells.
Drivers, manuals and installers sit at permanent URLs, so replacing the file behind the link updates every documentation page and support article pointing at it without a site edit.
The audit log records every download by customer, version and time, so support knows which customers are on the affected build before they call, and a license question is a lookup.
A weekend cutover moved the repair channel to Files.com while preserving the Acer endpoint and protocols its service providers already used.
Read The Story
The workload was small, but absorbing it into the file-transfer environment already feeding Oracle ERP eliminated an entire external sharing surface.
Read The Story
A Kyndryl-owned hostname, fixed IP addresses, and one-for-one path mapping let established z/OS workflows keep running across tightly controlled client environments.
Read The Story
Files.com preserved an embedded FTP workflow across an installed base GPC could not centrally reconfigure, replacing customer-owned hardware with hosted distribution.
Read The Story
“We tested about five different cloud FTPs and Files.com had much faster download and upload speeds. Plus they have a great user interface with a lot of features.”

“A security-first approach, granular permission model, and detailed audit logging. Easy to enforce least-privilege access across multiple sites.”

The three ways software reaches customers today, and where each one fails.
Attachments cap at tens of megabytes and mail gateways strip executables. The customer engineer gets a bounce, and support gets a ticket.
Blocked outright in locked-down networks, failed in security review, and unbranded. No record of who downloaded which version.
Release-day capacity, certificates, patching, per-customer accounts and uptime, owned by a support team whose product is not file hosting.
What release engineering and support teams ask before moving software delivery onto Files.com.
Publish each release to a Files.com folder on a branded download site under your domain. Customers sign in, or follow a link, and download through the browser, or their automation pulls over SFTP. Each customer reaches only its folders, every download is logged, and there is no server to run.
Yes. Deployed devices pull updates and configuration from a Files.com folder over SFTP, FTPS or FTP with a credential scoped to that folder, on the schedule built into the device. Files.com handles the release-day load, and a hostname on your domain means the endpoint never has to be reconfigured when your infrastructure changes.
Your download site runs on your own domain with dedicated IP addresses, so the customer’s IT allowlists one hostname and one address pair rather than a consumer sharing domain. Delivery is HTTPS or SFTP, both of which locked-down networks already permit for approved hosts.
Yes. Files.com folder permissions and groups scope each customer, partner and product line to its own folders, so the customer on a supported older version reaches its builds and nothing newer, and a reseller sees only the products it carries.
Yes. The audit log records every download with the user, the file, the version folder and the time, exports to CSV or your SIEM, and answers which customers are on an affected build before the first ticket arrives.
Publish them from a Files.com hosted folder or a live share link. The URL stays fixed as long as the path does, so uploading the new revision under the same name updates every documentation page and support article that points at it.
Yes. A share link opens in the browser with no account, delivers files up to 5 TB over resumable transfers, and can carry a password and an expiry so a fix executable is reachable for the service visit and then gone.
Yes. Give the beta its own folder with tester accounts or bound share links, set access to expire at the end of the program, and the audit log records which tester took which build. Removing the folder ends the beta cleanly.
Yes. Files.com accepts plain FTP alongside SFTP and FTPS for the endpoints that cannot be upgraded, scoped per device to one folder, so the installed base keeps pulling the way it always did while the server behind it is retired.
Hosted folders, share links, per-customer permissions and the audit log are part of the platform. The custom domain and branding that make the site yours come with the Power plan, and downloads past the included transfer are metered as cheap overages rather than a tier jump. Detail is on the pricing page.
A branded download site on your domain, folders and permissions per customer, stable links, and a record of every download. Put a real release on it during the 7-day free trial.
No credit card required • Free for 7 days • Live in minutes