DocEvent vs SFTPCloud

Both products put a managed SFTP endpoint in front of cloud storage without a server to run. The differences are the pricing model — per-instance tiers against per-user — where the free tier sits, and how far each goes beyond the endpoint itself.

Side by side

DocEventSFTPCloud
Entry priceFree forever — up to 5 users€39/month (Lite: 5 SFTP users, 1 instance, 10GB storage)
Pricing model$2 per user / month (from $10/month); no per-instance chargeSix instance tiers, €39 to €799/month, stepped by users, instances and storage
Free tierYes — free forever, 200MB transfer and 5,000 operations a month includedNo free tier
Where files liveAlways your own bucket — S3, Azure, GCS, R2, B2, Wasabi, MinIO and any S3-compatible endpoint. Nothing is stored on DocEvent's serversTheir hosted S3-based storage, or bring your own (S3, GCS, Azure, Wasabi, R2, B2 and others)
ProtocolsSFTP, FTPS, FTP and SCPSFTP, FTPS and FTP
Web file managerSFS Drive, included on every plan (per-user switch)Included
Self-hosted optionYes — self-hosted server binary and an AWS Marketplace AMI, same configCloud service only
IP allow / deny rulesPer-service firewall on every plan, including freeInbound rules included
Beyond the endpointChannels: route incoming files onward to FTP, SFTP, HTTP or email, with per-partner sources and destinationsWebhooks and email notifications
SFTPCloud figures from its published pricing page, retrieved 16 August 2026. DocEvent figures from our pricing. Tell us if either has moved and we will correct it.

Where DocEvent differs

Per-user beats per-instance at small scale

Five partners cost €39 a month on SFTPCloud's entry tier and nothing on DocEvent. Fifteen cost €49 there and $30 here. There is no instance count to plan around either — every DocEvent user is just a user, whichever backend it lands on.

The endpoint is not the ceiling

DocEvent's channels take a file that arrives over SFTP and deliver it onward — to a partner's FTP server, an HTTP endpoint, or email — with each party maintaining its own credentials. SFTPCloud's automation surface is webhooks and notifications; the delivery leg stays yours to build.

Leave the cloud when you need to

The same product runs as a self-hosted binary in your own VPC or from an AWS Marketplace AMI, with the same configuration model. SFTPCloud is a cloud service only — if a workload later needs to live inside your network, there is no equivalent to move to.

Where SFTPCloud may fit better

SFTPCloud bundles hosted storage into every tier, so if you have no bucket of your own and want storage and endpoint from one vendor, its Lite tier is a genuinely simple package. Its bring-your-own list also reaches further into consumer stores — Dropbox among them — which DocEvent does not connect to.

Switching takes three steps

1
Point DocEvent at your bucket
Connect the S3, Azure, GCS or S3-compatible bucket your files should live in — the same one you already use, or a fresh one. Files stream straight through; nothing is stored on our servers.
2
Recreate your users
Add an SFTP/FTPS/FTP user per partner or system, with a password or an SSH key and its own home directory. Per-service IP allow and deny rules are there if a partner should be pinned to known addresses.
3
Hand over the new hostname
Give partners the DocEvent hostname and credentials — or point a CNAME like sftp.yourcompany.com at the endpoint so nothing on their side ever changes again.

Common questions

You focus on integration,
we'll focus on delivery.

Get started for free