# DocEvent

> DocEvent is a fully managed, cloud-hosted file transfer platform. It gives you
> SFTP / FTPS / FTP access on top of your own cloud storage (Amazon S3, Azure Blob
> Storage, Google Cloud Storage and S3-compatible buckets such as Cloudflare R2,
> IBM COS, Backblaze, Wasabi and MinIO), browser access to the same files via
> SFS Drive, plus a file-routing service ("Channels") that automatically moves
> files from any source to any destination — including between different
> companies sharing one channel. There is no infrastructure to run — sign up and
> connect a backend in minutes.

DocEvent is one platform with two products - the Simple FTP Service (SFS, which
includes SFS Drive browser access and a self-hosted option) and Channels. All
sign-up and login happens in the central customer console
(https://console.docevent.io). This marketing site serves no API itself, but the
platform has a public Developer API for programmatic control of SFS - see
"Developer API" below.

## When to use DocEvent

DocEvent is two products on one platform. Reach for it when a task matches one
of these jobs:

**1. Simple FTP Service (SFS) - a managed SFTP / FTPS / FTP / SCP server over a
bucket you already own.** Best fit when you need to:

- Give people or systems SFTP, FTPS, FTP or SCP access to files in your own
  cloud storage - Amazon S3, Azure (Blob, Data Lake Gen2 or Files), Google
  Cloud Storage, or any S3-compatible store (Cloudflare R2, Backblaze B2,
  Wasabi, MinIO, IBM COS and others) - without running a file server.
- Receive scheduled exports from any third-party platform that pushes over
  SFTP/FTPS/FTP (contact-centre call recordings, EDI drops, report feeds,
  backups) straight into your own bucket, with per-user accounts, an IP
  firewall, SSH-key auth and a full audit log.
- Add browser upload/download for the same users via SFS Drive - same
  permissions and audit trail, no client software.
- Run the same server yourself when data cannot leave your account: Self-Hosted
  in your own AWS VPC, or the SFS Server AMI on the AWS Marketplace.

**2. Channels - automatic any-to-any file routing, including between different
companies.** Best fit when files must move from one place to another on their
own:

- 14 source types: Amazon S3 events, HTTP upload, inbound email, a
  DocEvent-hosted SFTP/SCP/FTPS server that senders upload to (push), AS2
  from a trading partner, a SharePoint document library, scheduled pulls from
  your FTP or SFTP server (DocEvent polls a server you run), scheduled pulls from cloud storage (any S3-compatible
  bucket, Google Cloud Storage, Azure Blob, Azure Data Lake Gen2, Azure
  Files), and on-premise folders via the Filerouter or the DocEvent Agent.
- 11 destination types: an Amazon S3 or S3-compatible bucket (Cloudflare R2,
  MinIO, Backblaze B2, Wasabi and friends), a Google Cloud Storage bucket, an
  Azure Blob Storage container (standard and Data Lake Gen2 accounts alike),
  FTP, SFTP, HTTP webhook, email
  (SES), AS2 to a trading partner, a SharePoint document library, and
  on-premise folders via the Filerouter or the DocEvent Agent.
- Channels are multi-party: invite another company to a shared channel and
  each side attaches and manages its own endpoint and credentials - the
  standard pattern for B2B/EDI exchange, AS2 trading partners, and
  production-to-staging replication.
- Every file gets automatic retries and an end-to-end audit trail. No code
  required.

Not a fit: DocEvent is not hosted storage (you bring your own bucket), not a
consumer file-sharing tool, and not a two-way sync client - a channel moves
files one way per route.

How to start: sign up free at https://console.docevent.io/login/new (no credit
card; the Basic plan is free forever for up to 5 users, and Channels are free
while in preview), create an SFS service or a channel in the console, and automate
SFS with the Developer API below.

## Products

- [Simple FTP Service (SFS)](https://docevent.io/sfs/): Managed SFTP, FTPS, FTP and
  SCP front-end for your cloud storage bucket. Per-user accounts, IP
  whitelist/blacklist firewall, SSH-key auth, full audit logging, file
  restore/reprocessing, and a dashboard. Backends: AWS S3, Azure Blob, Google
  Cloud Storage, and S3-compatible stores (R2, IBM COS, Backblaze, Wasabi, MinIO).
- [FTP as a Service](https://docevent.io/ftp-as-a-service/): Landing page for the
  same managed SFS product, framed for the "FTP as a service" / "cloud FTP" /
  "hosted FTP" search intent — fully managed SFTP/FTPS/FTP on your own S3, Azure
  Blob, GCS or S3-compatible bucket, with no FTP server to run. Free forever to
  start. (Not a separate product; it is the SFS offering.)
- [SFS Drive](https://docevent.io/sfs-drive/): Browser access to the Simple FTP
  Service. The same service users that connect over SFTP/FTPS/FTP can sign in at
  https://sfs-drive.docevent.io from any web browser to upload, download, rename,
  delete and organise files — same permissions (including read-only), IP
  firewall and audit logging, no client software. Web access is a per-user
  switch; included with every plan.
- [Channels](https://docevent.io/channel/): Event-driven file routing. Connect a
  source (Amazon S3, HTTP upload, inbound email, an SFTP / FTPS server that
  DocEvent hosts for the channel - SFTP and SCP on port 22, explicit and
  implicit FTPS, per-user passwords or SSH keys, an IP firewall, upload-only,
  every completed upload enters the channel - AS2 from a trading partner, a
  Microsoft 365 SharePoint document library, a scheduled FTP/FTPS or SFTP
  pull where DocEvent polls your own server and collects new files, a scheduled
  pull from cloud storage — any S3-compatible bucket such as Cloudflare R2,
  MinIO, Backblaze B2, Wasabi, Supabase Storage, Hetzner Object Storage or Amazon S3 itself, plus
  Google Cloud Storage (GCS Blob), Azure Blob (standard/flat), Azure Data Lake Gen2 (hierarchical namespace) and Azure Files (SMB
  shares), no bucket notifications or event plumbing needed —
  or an on-premise folder via the Filerouter or DocEvent Agent) to a destination
  (an Amazon S3 or S3-compatible bucket — Cloudflare R2, MinIO, Backblaze B2,
  Wasabi, Hetzner Object Storage and friends, with access-key or assume-role authentication — a Google
  Cloud Storage bucket authenticated with a service-account key, an Azure Blob
  Storage container authenticated with the storage account key — one endpoint
  type covers both standard and Data Lake Gen2 accounts — FTP,
  SFTP, HTTP webhook, email via Amazon
  SES, AS2 to a trading partner, a SharePoint document library, or an
  on-premise folder). The Filerouter is a small self-contained agent
  for Windows/macOS/Linux that watches a local directory and moves files to and
  from a channel over outbound HTTPS — no inbound ports, no lost or duplicated
  files. The DocEvent Agent is its console-managed sibling: enroll it once on
  your machine and configure watched/delivery folders remotely from the web
  console. Channels are multi-party: the sender
  and receiver can be different accounts — invite a customer or trading partner
  (by email or username) and they attach their own endpoint with their own
  credentials, with per-member send/receive permissions. Files are delivered
  automatically with automatic retries and an end-to-end audit trail. No code
  required. Currently in preview and free for all users.
- [AS2 for EDI](https://docevent.io/channel/as2/): Hosted AS2 (RFC 4130) send
  and receive endpoints inside Channels — no AS2 server to run. A receive
  endpoint gets its own AS2 URL to hand a trading partner and is pinned to one
  partner identity; a send endpoint transmits to the partner's URL. Outbound
  messages are signed (SHA-256/384/512) and encrypted (AES-256/192/128-CBC, or
  3DES for legacy partners) with the partner's certificate, optionally
  compressed; inbound messages are decrypted and their signatures verified
  before the file enters the channel, and an endpoint can require signed and/or
  encrypted messages. MDN receipts are fully managed in ALL THREE modes in both
  directions — synchronous (in the HTTP reply), asynchronous (posted back later
  to a return URL) and none — with signed receipts verified; a message whose
  asynchronous receipt never arrives is parked for reprocessing rather than
  assumed delivered. Duplicate messages are detected per RFC 4130. Identities
  (stations), trading partners and certificates live in the web console with
  expiry warnings (30 days / 7 days). Because AS2
  is a normal channel source and destination, an AS2 message can be delivered
  to an S3, GCS or Azure Blob bucket, FTP, SFTP, a webhook, email, SharePoint
  or an on-premise folder, and any source can be transmitted as AS2. (Not a separate product; part of Channels.)
- [SharePoint file transfer](https://docevent.io/channel/sharepoint/): Microsoft
  365 SharePoint document libraries as a channel source and destination. As a
  source, DocEvent checks a library on a schedule and collects new files —
  filename pattern filtering, an optional minimum age and size-stability check
  so half-uploaded files are skipped, a per-check file cap, then each collected
  file is deleted (into the site recycle bin) or moved to an archive folder. As
  a destination, files are delivered into the site, library and folder you pick,
  with a choice of what happens when the name already exists (keep both, replace
  — SharePoint keeps version history — or fail), and large files upload in
  chunks. Both directions use a reusable Microsoft connection created once in
  the console (sign in with a Microsoft 365 account, or supply your own Entra
  application), so no client secret is stored on the endpoint and rotation
  happens in one place. Not a sync client: one-way, audited transfers.
  Cross-tenant library-to-library copying works because each end uses its own
  connection. (Not a separate product; part of Channels.)
- [Shared Channels](https://docevent.io/channel/shared/): Explainer for the
  multi-member side of Channels: create a channel, invite one or many members
  (by email or username), and every file sent in is delivered to every member
  permitted to receive — each on an endpoint they choose and manage themselves,
  governed by per-member send/receive permissions. Fan-out to multiple
  receivers also covers server migrations (run old + new receivers side by
  side during a v1→v2 upgrade) and replicating production data to staging or
  test environments. (Not a separate product; part of Channels.)
- [Managed File Transfer](https://docevent.io/managed-file-transfer/): Landing
  page framing the whole platform for the "managed file transfer" / "MFT"
  search intent — DocEvent as a managed file transfer operator: managed
  SFTP/FTPS/FTP + browser endpoints on top of storage you own, plus shared
  channels where every customer or partner attaches and maintains their own
  endpoint (you only send the invite). Covers the full endpoint range: SFTP,
  FTPS, FTP, web browser (SFS Drive), cloud buckets, HTTPS/webhooks, email, and
  on-premise folders via the DocEvent filerouter agent. (Not a separate
  product; it is the SFS + Channels platform.)
- [Call Recording Storage](https://docevent.io/call-recordings/): Landing page
  for the "call recording storage / archive call recordings" intent — point any
  contact-centre platform or dialer with an SFTP/FTPS/FTP export (Five9, NICE
  inContact/CXone, Convoso, Nextiva, Genesys, 8x8, ViciDial, Ameyo, 3CX,
  Asterisk/FreePBX, ...) at a DocEvent endpoint and every recording lands in the
  customer's own S3 / Azure Blob / GCS / S3-compatible bucket for compliance
  retention (object lock, lifecycle to cold storage, audit log). (Not a separate
  product; it is the SFS offering.)
- [AWS Transfer Family Alternative](https://docevent.io/sfs/aws-transfer-family/):
  Comparison page for people evaluating AWS Transfer Family. Same managed SFS
  product, framed against AWS's own managed SFTP: DocEvent bills per user and
  starts free, where Transfer Family bills per enabled protocol per
  server-hour (~US$219/month for one protocol before any traffic). Also
  covers the case AWS wins — at terabyte volumes the self-hosted SFS Server
  from the AWS Marketplace is the right answer, not the managed plans — and
  the backend difference (DocEvent also supports Azure, Google Cloud and
  S3-compatible stores; Transfer Family is S3/EFS only).
- [Azure Blob SFTP Alternative](https://docevent.io/sfs/azure-sftp/): Comparison
  page for people evaluating Azure Blob Storage's built-in SFTP support.
  Sourced figures: Azure bills US$0.30/hour while SFTP is enabled (~US$216/mo
  per storage account, used or not), requires a hierarchical-namespace (Data
  Lake Gen2) account, speaks SFTP only, and generates local-user passwords
  for you. DocEvent connects to any Azure container as it stands (Blob, Data
  Lake Gen2, Azure Files), adds FTPS/FTP/SCP, bills per user and starts free
  for up to 5 users. Heavy volumes route to custom pricing or self-hosted.
- [DocEvent vs SFTPCloud](https://docevent.io/sfs/vs/sftpcloud/): Comparison page
  for people evaluating SFTPCloud. Side-by-side table (retrieved from public
  pricing, dated on-page): SFTPCloud starts at EUR 39/month for 5 users on one
  instance with no free tier; DocEvent is free for up to 5 users on the
  customer's own bucket, then $2/user/month, and adds SCP, a self-hosted
  option and Channels file routing. Notes honestly where SFTPCloud fits
  better (bundled hosted storage, wider consumer-store integrations).
- [DocEvent vs Couchdrop](https://docevent.io/sfs/vs/couchdrop/): Comparison page
  for people evaluating Couchdrop. Couchdrop's entry plan is US$50/month for
  one external user with 10GB monthly transfer, higher tiers are
  contact-sales; DocEvent is free for up to 5 users, self-service throughout.
  Notes honestly where Couchdrop fits better (terabyte transfer tiers,
  DLP/malware scanning, SSO/SCIM).
- [DocEvent vs SFTP To Go](https://docevent.io/sfs/vs/sftp-to-go/): Comparison
  page for people evaluating SFTP To Go. SFTP To Go bundles managed storage
  (from US$150/month, 20 credentials); bring-your-own bucket is
  Enterprise-only beta. DocEvent only ever fronts the customer's own bucket,
  free up to 5 users. Notes honestly where SFTP To Go fits better (no bucket
  needed, S3 API access, SOC 2 / HIPAA tiers).
- [SFTP for Amazon S3](https://docevent.io/sfs/s3/): Landing page for the "sftp to s3" / "aws sftp" intent — managed
  SFTP, FTPS, FTP and SCP in front of the customer's own S3 bucket, connected
  with an IAM access key. Also covers S3-compatible stores (Cloudflare R2,
  Backblaze B2, Wasabi, Hetzner, MinIO, IBM COS, StorageGRID, Ceph, Cloudian) through the
  same connector. Not a separate product; it is the SFS offering.
- [SFTP for Azure Blob Storage](https://docevent.io/sfs/azure/): Landing page for the "azure sftp" / "azure blob storage sftp" intent.
  Same managed SFS product in front of an Azure storage account — Blob, Data
  Lake Storage Gen2 or Files — connected with an account key. Notable
  difference from Azure's own SFTP: no Data Lake Gen2 hierarchical namespace is
  required, so it works against a plain Blob container.
- [SFTP for Google Cloud Storage](https://docevent.io/sfs/gcs/): Landing page for the "google cloud storage sftp" intent. Same managed
  SFS product in front of a GCS bucket, authenticated with a service-account
  key. Google Cloud has no first-party managed SFTP, so this replaces running a
  Compute Engine VM with sshd.
- [SFTP for Cloudflare R2](https://docevent.io/sfs/cloudflare-r2/): Landing page for the
  "cloudflare r2 sftp" intent. R2 has no SFTP of its own; this is the managed
  endpoint in front of an R2 bucket, connected with an R2 API token and the
  account's <account-id>.r2.cloudflarestorage.com endpoint. The distinguishing
  point is cost: R2 charges no egress, so the Cloudflare leg of a partner
  download costs nothing per gigabyte; DocEvent bills per user plus data packs
  (US$10 per 10GB a month) beyond the transfer included in the plan.
- [SFTP for S3-Compatible Storage](https://docevent.io/sfs/s3-compatible/): Landing page for
  the "wasabi sftp" / "minio sftp" / "s3 compatible sftp" intent. The same
  managed SFS product in front of any bucket that speaks the S3 API — Wasabi,
  Backblaze B2, Hetzner Object Storage, MinIO, Ceph, NetApp StorageGRID, Cloudian and IBM COS. Only the
  endpoint URL differs from the Amazon S3 setup. Cloudflare R2 has its own page.
- [Self-Hosted / Enterprise](https://docevent.io/self-hosted/): Run the Simple
  FTP Service inside your own AWS VPC for full control over data and network.
- [AWS Marketplace](https://docevent.io/aws-marketplace/): The SFS Server as a
  paid AMI + CloudFormation product on the AWS Marketplace
  (https://aws.amazon.com/marketplace/pp/prodview-v6eirqlaodmxk). Deploys a
  self-hosted SFTP/FTPS/FTP/SCP server fleet into the buyer's own AWS account
  over their own S3/GCS/Azure/S3-compatible buckets, billed hourly through AWS
  with no separate license; includes a built-in browser admin UI for users,
  certificates, health and scaling. The page includes a factual feature and
  pricing comparison versus AWS Transfer Family (flat hourly price vs
  per-protocol hourly + per-GB rates).
- [News](https://docevent.io/news/): Product news, feature announcements and
  release notes. Each article has its own page at /news/<slug>.
- [Articles](https://docevent.io/articles/): Long-form technical articles on file transfer —
  how SFTP and FTP actually behave, integration patterns, and production failure
  modes. Each article has its own page at /articles/<slug>.
- [Does HIPAA require on-premises file transfer?](https://docevent.io/articles/hipaa-on-prem-file-transfer/):
  Why the HIPAA Security Rule never mandates on-premises hosting - it is
  technology-neutral and asks for safeguards, a business associate agreement
  and documentation; encryption is currently "addressable" (the January 2025
  proposed rule would make it required, still not final); six-year retention
  applies to compliance documentation only; the custody reframe and three
  vendor questions (who holds data at rest, is there a BAA, can you prove what
  happened); and DocEvent's posture - files land in the customer's own bucket,
  DocEvent signs a BAA, seven-year audit log, self-hosted for bytes that must
  never transit a vendor.
- [Truncated files on SFTP and FTP](https://docevent.io/articles/partial-file-pickup-truncation/):
  Why a poller can collect a file that is still being uploaded, why every log
  reports success, and the fixes that close it — atomic rename to the collected
  name, staging directories, marker files, minimum-age and size-stability gates,
  and manifest/checksum verification.
- [File transfer audit trails](https://docevent.io/articles/file-transfer-audit-trail/):
  Why most MFT purchases are really about the audit trail, not the transfer -
  what a per-file record has to contain (arrival, routing decision, outcome per
  destination, verbatim errors, retries, parked files), how to size retention,
  the proof-of-delivery evidence ladder from exit codes to signed AS2 MDN
  receipts, and the questions to ask any MFT vendor.
- [NetSuite BAI2 and NACHA over SFTP](https://docevent.io/articles/netsuite-bai2-nacha-sftp/):
  Connecting NetSuite to bank SFTP without an integration platform - what the
  Auto Bank Statement Import, SFTP Connector and N/sftp tools already handle
  natively, where direct bank connections fail (push-only banks, IP
  allowlisting, no archive), and the SFTP-mailbox pattern on your own bucket.
- [Support guides](https://docevent.io/support/): Step-by-step setup
  walkthroughs with console screenshots, organised by product
  (Simple FTP Service, Channels, Self-Hosted, Account, API) and
  category. Each guide has its own page at /support/<slug>.
- [Simple FTP Service overview](https://docevent.io/support/simple-ftp-service-overview/):
  What a Simple FTP Service is - FTP, FTPS, SFTP and SCP access to your own
  cloud storage, running in three regions with no servers to manage.
- [Your first FTP/SFTP to Amazon S3 service](https://docevent.io/support/first-ftp-to-s3-service/):
  Create an SFS service that gives you FTP, FTPS and SFTP access to your own
  Amazon S3 bucket, with DocEvent creating the bucket and keys for you if you
  want.
- [Your first FTP to Azure service](https://docevent.io/support/first-ftp-to-azure-service/):
  Create an SFS service that gives you FTP, FTPS and SFTP access to your own
  Azure Blob Storage container.
- [Your first FTP/SFTP to Google Cloud Storage service](https://docevent.io/support/first-ftp-to-gcs-service/):
  Create an SFS service that gives you FTP, FTPS and SFTP access to your own
  Google Cloud Storage bucket.
- [File versioning and restore](https://docevent.io/support/file-versioning-and-restore/):
  Restore earlier versions of uploaded files from the service logs by enabling
  versioning on your storage bucket.
- [Restrictive S3 bucket permissions](https://docevent.io/support/s3-bucket-permissions/):
  Limit DocEvent's access to specific paths in an existing S3 bucket with a
  scoped IAM policy and the service's test path.
- [SSH authorized keys for passwordless SFTP](https://docevent.io/support/sftp-authorized-keys/):
  Give a user public-key login for SFTP - generate a key pair, add up to 10
  authorized keys to the user, connect without a password.
- [Backend storage IP addresses](https://docevent.io/support/backend-storage-ip-addresses/):
  The IP addresses DocEvent's servers connect to your backend storage bucket
  from, per region - for bucket firewalls and ACLs.
- [Cloud storage limitations over FTP and SFTP](https://docevent.io/support/cloud-storage-limitations/):
  What object storage backends can and cannot do through an FTP/SFTP interface
  - renames, symlinks, appends, and why some operations show up as two log
  entries.
- [FTPS TLS certificates](https://docevent.io/support/ftps-tls-certificates/):
  The certificates DocEvent presents for explicit and implicit FTPS
  connections, who issues them, and how to configure your client's trust.
- [IP allow and deny lists](https://docevent.io/support/ip-allow-and-deny-lists/):
  Restrict who can connect to your service with per-service ALLOW and DENY
  lists - single addresses, CIDR ranges and comments.
- [Passive vs active FTP](https://docevent.io/support/passive-vs-active-ftp/):
  The difference between passive and active FTP data connections, which mode
  to use, and why active mode fails through firewalls.
- [SSH host keys for SFTP and SCP](https://docevent.io/support/ssh-host-keys/):
  The host key fingerprints DocEvent's SFTP/SCP servers present, how to verify
  them on first connection, and what to do about IP-change warnings.
- [Scaling and connection handling](https://docevent.io/support/scaling-and-connection-handling/):
  How DocEvent scales its clusters without cutting off your in-flight FTP and
  SFTP transfers.
- [SFS Static IP addresses and ports](https://docevent.io/support/static-ip-addresses/):
  The connection and data IP addresses for each Simple FTP Service region,
  what to allowlist in your firewall or storage ACL, and which ports to open.
- [Using a custom DNS name](https://docevent.io/support/custom-dns-name/):
  Point your own hostname at your Simple FTP Service with a CNAME - what works
  for SFTP and plain FTP, and why FTPS needs a different approach.
- [550 Not found when logging in](https://docevent.io/support/550-not-found-on-login/):
  Why a brand-new service or user sees "550 Not found" on their first FTP
  login, and the one-step fix.
- [Forward slash in the username](https://docevent.io/support/username-forward-slash/):
  What to do when your FTP software refuses the serviceid/username login
  format - escaping, backslash, and username aliases.
- [Google Cloud Storage permissions](https://docevent.io/support/gcs-permissions/):
  The roles your GCS service account needs, and the errors you see when they
  are missing.
- [Verifying a service with an Azure firewall enabled](https://docevent.io/support/verifying-service-with-azure-firewall-enabled/):
  What to do when Verify Access fails because your Azure storage account sits
  behind a firewall.
- [Azure Event Grid events for completed uploads](https://docevent.io/support/azure-event-grid-completed-uploads/):
  Which BlobCreated events fire for azure/blob vs azure/datalake services,
  and how to trigger downstream systems only on completed files.
- [ssh-rsa client compatibility for SFTP](https://docevent.io/support/sftp-ssh-rsa-client-compatibility/):
  Fixing "no matching host key type found" and passwordless logins that still
  prompt for a password - the ssh-rsa deprecation, and when you need client
  config.
- [Receive channel files from an S3 bucket](https://docevent.io/support/channels-receive-from-s3/):
  Set up the Amazon S3 source plugin - let DocEvent pick up every new file
  landing in your bucket, automatically via CloudFormation or by hand.
- [Channel static IP addresses](https://docevent.io/support/channels-static-ip-addresses/):
  The static IP addresses Channels connect from in each region - what to
  allowlist when DocEvent delivers to or polls your FTP, SFTP, HTTP or AS2
  server.
- [Self-Hosted overview](https://docevent.io/support/self-hosted-overview/):
  Run the Simple FTP Server in your own datacenter or VPC - hybrid mode,
  cloud-managed configuration, and what stays on your servers.
- [Start your first self-hosted instance](https://docevent.io/support/self-hosted-first-instance/):
  Activate a trial license, download the server binary, and run a Simple FTP
  Server on your own machine connected to your DocEvent services.
- [Load balancing self-hosted servers](https://docevent.io/support/self-hosted-load-balancing/):
  Four ways to put a stable address in front of multiple self-hosted instances
  - DNS round robin, weighted DNS, and load balancers with or without
  per-instance public IPs.
- [Clustering recommendations](https://docevent.io/support/self-hosted-clustering/):
  How to choose a clustering implementation for self-hosted instances - by
  protocol, with the trade-offs of DNS round robin and the network load
  balancer variants.
- [Running self-hosted in Docker](https://docevent.io/support/self-hosted-docker/):
  Start the Simple FTP Server from the official Docker image, publish the
  right ports, and pass configuration as environment variables.
- [Self-hosted firewall configuration](https://docevent.io/support/self-hosted-firewall/):
  The inbound and outbound rules a self-hosted instance needs - control ports,
  passive ranges, and the cloud configuration link.
- [Self-hosted server logging](https://docevent.io/support/self-hosted-logging/):
  Where the self-hosted server logs go, the JSON production format, and how to
  recognise transaction entries for logins and transfers.
- [Self-hosted server parameters](https://docevent.io/support/self-hosted-server-parameters/):
  Every flag and environment variable the self-hosted Simple FTP Server
  accepts, with defaults and the options that matter most.
- [Usage-based billing](https://docevent.io/support/usage-based-billing/):
  How data transfer, operations and storage are measured against your plan's
  included amounts, and what happens when you go over.
- [Getting started with the Developer API](https://docevent.io/support/api-getting-started/):
  Create an API key, make your first request, and explore the OpenAPI
  reference for automating your DocEvent services.
- [Create a Simple FTP Service via the API](https://docevent.io/support/api-create-sfs-service/):
  A worked example of PUT /service/sfs - create an S3-backed service with its
  first user in one call.
- [Cancelling or closing your account](https://docevent.io/support/closing-your-account/):
  Cancel your subscription or close your account entirely - the difference
  between the two, and what has to be cleared first.
- [Payment failed and my account is disabled](https://docevent.io/support/payment-failed-account-disabled/):
  What happens when a card payment fails, when the account is disabled, and
  how it comes back on once the invoice is paid.
- [Invoice details and who receives them](https://docevent.io/support/invoice-details-and-recipients/):
  Set the billing name, address and email that appear on your invoices, choose
  the invoice language, and find your past invoices and receipts.
- [Home directories and keeping each user isolated](https://docevent.io/support/home-directories-and-user-isolation/):
  Give every user their own folder in one bucket, and what stops them reaching
  anyone else's files.
- [Security and compliance questions](https://docevent.io/support/security-and-compliance/):
  Straight answers for vendor security questionnaires - what we hold, what we
  are aligned with, and what DocEvent must not be used for.

## Pricing

- [Pricing](https://docevent.io/pricing/): Three SFS plans — Basic (free forever,
  up to 5 users), Standard ($2/user/month, from $10/month), Premium
  ($5/user/month, from $25/month). Paid plans are billed in blocks of 5 users.
  Data and operations packs scale usage ($10 for 10GB transfer, $10 for 100,000
  operations). Premium adds organisations (invite team members to manage the
  account, each with their own login), file restore / reprocessing, root
  username aliasing and 90-day log retention. SFS Drive (web browser access) is
  included with every plan at no
  extra cost; browser transfers count towards the same data/operations quotas.
  The Channels service is free while in preview.

## Developer API

The Simple FTP Service has a public Developer API for programmatic management
of SFS services, users, firewall rules, health checks and audit logs - an agent
or script can provision and operate a complete SFS setup with it. (Channels are
managed in the web console only at this stage.)

- [OpenAPI 3.1 spec (YAML)](https://console.docevent.io/documentation/developer-api/openapi.yaml)
- [OpenAPI 3.1 spec (JSON)](https://console.docevent.io/documentation/developer-api/openapi.json)
- [Interactive API reference (Swagger UI)](https://console.docevent.io/documentation/developer-api/index.html)

Authentication: create an API key in the console (Account → API,
https://console.docevent.io/account/api) and send it in the `x-api-key` header
on every request. Keys are scoped to their owning account and to the region
they were created in. Regional base URLs:
https://developer-us-east-1.docevent.io,
https://developer-eu-west-1.docevent.io and
https://developer-ap-southeast-2.docevent.io - use the region your service was
created in. Verify a key with `GET /hello`.

## Channel integrations (source → destination)

- [Amazon S3 → Amazon S3 (or any S3-compatible bucket)](https://docevent.io/channel/s3-to-s3/)
- [Amazon S3 → Google Cloud Storage](https://docevent.io/channel/s3-to-gcs/)
- [Amazon S3 → Azure Blob Storage](https://docevent.io/channel/s3-to-azure-blob/)
- [Amazon S3 → FTP](https://docevent.io/channel/s3-to-ftp/)
- [Amazon S3 → SFTP](https://docevent.io/channel/s3-to-sftp/)
- [Amazon S3 → HTTP webhook](https://docevent.io/channel/s3-to-http/)
- [Amazon S3 → Email (SES)](https://docevent.io/channel/s3-to-ses-email/)
- [Amazon S3 → AS2 (to a trading partner)](https://docevent.io/channel/s3-to-as2/)
- [Amazon S3 → SharePoint (Microsoft 365 document library)](https://docevent.io/channel/s3-to-sharepoint/)
- [Amazon S3 → Filerouter (on-premise folder)](https://docevent.io/channel/s3-to-filerouter/)
- [Amazon S3 → DocEvent Agent (on-premise folder)](https://docevent.io/channel/s3-to-agent/)
- [HTTP upload → Amazon S3 (or any S3-compatible bucket)](https://docevent.io/channel/http-to-s3/)
- [HTTP upload → Google Cloud Storage](https://docevent.io/channel/http-to-gcs/)
- [HTTP upload → Azure Blob Storage](https://docevent.io/channel/http-to-azure-blob/)
- [HTTP upload → FTP](https://docevent.io/channel/http-to-ftp/)
- [HTTP upload → SFTP](https://docevent.io/channel/http-to-sftp/)
- [HTTP upload → HTTP webhook](https://docevent.io/channel/http-to-http/)
- [HTTP upload → Email (SES)](https://docevent.io/channel/http-to-ses-email/)
- [HTTP upload → AS2 (to a trading partner)](https://docevent.io/channel/http-to-as2/)
- [HTTP upload → SharePoint (Microsoft 365 document library)](https://docevent.io/channel/http-to-sharepoint/)
- [HTTP upload → Filerouter (on-premise folder)](https://docevent.io/channel/http-to-filerouter/)
- [HTTP upload → DocEvent Agent (on-premise folder)](https://docevent.io/channel/http-to-agent/)
- [Email → Amazon S3 (or any S3-compatible bucket)](https://docevent.io/channel/email-to-s3/)
- [Email → Google Cloud Storage](https://docevent.io/channel/email-to-gcs/)
- [Email → Azure Blob Storage](https://docevent.io/channel/email-to-azure-blob/)
- [Email → FTP](https://docevent.io/channel/email-to-ftp/)
- [Email → SFTP](https://docevent.io/channel/email-to-sftp/)
- [Email → HTTP webhook](https://docevent.io/channel/email-to-http/)
- [Email → Email (SES)](https://docevent.io/channel/email-to-ses-email/)
- [Email → AS2 (to a trading partner)](https://docevent.io/channel/email-to-as2/)
- [Email → SharePoint (Microsoft 365 document library)](https://docevent.io/channel/email-to-sharepoint/)
- [Email → Filerouter (on-premise folder)](https://docevent.io/channel/email-to-filerouter/)
- [Email → DocEvent Agent (on-premise folder)](https://docevent.io/channel/email-to-agent/)
- [AS2 (from a trading partner) → Amazon S3 (or any S3-compatible bucket)](https://docevent.io/channel/as2-to-s3/)
- [AS2 (from a trading partner) → Google Cloud Storage](https://docevent.io/channel/as2-to-gcs/)
- [AS2 (from a trading partner) → Azure Blob Storage](https://docevent.io/channel/as2-to-azure-blob/)
- [AS2 (from a trading partner) → FTP](https://docevent.io/channel/as2-to-ftp/)
- [AS2 (from a trading partner) → SFTP](https://docevent.io/channel/as2-to-sftp/)
- [AS2 (from a trading partner) → HTTP webhook](https://docevent.io/channel/as2-to-http/)
- [AS2 (from a trading partner) → Email (SES)](https://docevent.io/channel/as2-to-ses-email/)
- [AS2 (from a trading partner) → AS2 (to a trading partner)](https://docevent.io/channel/as2-to-as2/)
- [AS2 (from a trading partner) → SharePoint (Microsoft 365 document library)](https://docevent.io/channel/as2-to-sharepoint/)
- [AS2 (from a trading partner) → Filerouter (on-premise folder)](https://docevent.io/channel/as2-to-filerouter/)
- [AS2 (from a trading partner) → DocEvent Agent (on-premise folder)](https://docevent.io/channel/as2-to-agent/)
- [Filerouter (on-premise folder) → Amazon S3 (or any S3-compatible bucket)](https://docevent.io/channel/filerouter-to-s3/)
- [Filerouter (on-premise folder) → Google Cloud Storage](https://docevent.io/channel/filerouter-to-gcs/)
- [Filerouter (on-premise folder) → Azure Blob Storage](https://docevent.io/channel/filerouter-to-azure-blob/)
- [Filerouter (on-premise folder) → FTP](https://docevent.io/channel/filerouter-to-ftp/)
- [Filerouter (on-premise folder) → SFTP](https://docevent.io/channel/filerouter-to-sftp/)
- [Filerouter (on-premise folder) → HTTP webhook](https://docevent.io/channel/filerouter-to-http/)
- [Filerouter (on-premise folder) → Email (SES)](https://docevent.io/channel/filerouter-to-ses-email/)
- [Filerouter (on-premise folder) → AS2 (to a trading partner)](https://docevent.io/channel/filerouter-to-as2/)
- [Filerouter (on-premise folder) → SharePoint (Microsoft 365 document library)](https://docevent.io/channel/filerouter-to-sharepoint/)
- [Filerouter (on-premise folder) → Filerouter (on-premise folder)](https://docevent.io/channel/filerouter-to-filerouter/)
- [Filerouter (on-premise folder) → DocEvent Agent (on-premise folder)](https://docevent.io/channel/filerouter-to-agent/)
- [FTP Pull (scheduled, from your FTP server) → Amazon S3 (or any S3-compatible bucket)](https://docevent.io/channel/ftp-pull-to-s3/)
- [FTP Pull (scheduled, from your FTP server) → Google Cloud Storage](https://docevent.io/channel/ftp-pull-to-gcs/)
- [FTP Pull (scheduled, from your FTP server) → Azure Blob Storage](https://docevent.io/channel/ftp-pull-to-azure-blob/)
- [FTP Pull (scheduled, from your FTP server) → FTP](https://docevent.io/channel/ftp-pull-to-ftp/)
- [FTP Pull (scheduled, from your FTP server) → SFTP](https://docevent.io/channel/ftp-pull-to-sftp/)
- [FTP Pull (scheduled, from your FTP server) → HTTP webhook](https://docevent.io/channel/ftp-pull-to-http/)
- [FTP Pull (scheduled, from your FTP server) → Email (SES)](https://docevent.io/channel/ftp-pull-to-ses-email/)
- [FTP Pull (scheduled, from your FTP server) → AS2 (to a trading partner)](https://docevent.io/channel/ftp-pull-to-as2/)
- [FTP Pull (scheduled, from your FTP server) → SharePoint (Microsoft 365 document library)](https://docevent.io/channel/ftp-pull-to-sharepoint/)
- [FTP Pull (scheduled, from your FTP server) → Filerouter (on-premise folder)](https://docevent.io/channel/ftp-pull-to-filerouter/)
- [FTP Pull (scheduled, from your FTP server) → DocEvent Agent (on-premise folder)](https://docevent.io/channel/ftp-pull-to-agent/)
- [SFTP Pull (scheduled, from your SFTP server) → Amazon S3 (or any S3-compatible bucket)](https://docevent.io/channel/sftp-pull-to-s3/)
- [SFTP Pull (scheduled, from your SFTP server) → Google Cloud Storage](https://docevent.io/channel/sftp-pull-to-gcs/)
- [SFTP Pull (scheduled, from your SFTP server) → Azure Blob Storage](https://docevent.io/channel/sftp-pull-to-azure-blob/)
- [SFTP Pull (scheduled, from your SFTP server) → FTP](https://docevent.io/channel/sftp-pull-to-ftp/)
- [SFTP Pull (scheduled, from your SFTP server) → SFTP](https://docevent.io/channel/sftp-pull-to-sftp/)
- [SFTP Pull (scheduled, from your SFTP server) → HTTP webhook](https://docevent.io/channel/sftp-pull-to-http/)
- [SFTP Pull (scheduled, from your SFTP server) → Email (SES)](https://docevent.io/channel/sftp-pull-to-ses-email/)
- [SFTP Pull (scheduled, from your SFTP server) → AS2 (to a trading partner)](https://docevent.io/channel/sftp-pull-to-as2/)
- [SFTP Pull (scheduled, from your SFTP server) → SharePoint (Microsoft 365 document library)](https://docevent.io/channel/sftp-pull-to-sharepoint/)
- [SFTP Pull (scheduled, from your SFTP server) → Filerouter (on-premise folder)](https://docevent.io/channel/sftp-pull-to-filerouter/)
- [SFTP Pull (scheduled, from your SFTP server) → DocEvent Agent (on-premise folder)](https://docevent.io/channel/sftp-pull-to-agent/)
- [SFTP / FTPS Server (hosted by DocEvent, senders upload to it) → Amazon S3 (or any S3-compatible bucket)](https://docevent.io/channel/sftp-server-to-s3/)
- [SFTP / FTPS Server (hosted by DocEvent, senders upload to it) → Google Cloud Storage](https://docevent.io/channel/sftp-server-to-gcs/)
- [SFTP / FTPS Server (hosted by DocEvent, senders upload to it) → Azure Blob Storage](https://docevent.io/channel/sftp-server-to-azure-blob/)
- [SFTP / FTPS Server (hosted by DocEvent, senders upload to it) → FTP](https://docevent.io/channel/sftp-server-to-ftp/)
- [SFTP / FTPS Server (hosted by DocEvent, senders upload to it) → SFTP](https://docevent.io/channel/sftp-server-to-sftp/)
- [SFTP / FTPS Server (hosted by DocEvent, senders upload to it) → HTTP webhook](https://docevent.io/channel/sftp-server-to-http/)
- [SFTP / FTPS Server (hosted by DocEvent, senders upload to it) → Email (SES)](https://docevent.io/channel/sftp-server-to-ses-email/)
- [SFTP / FTPS Server (hosted by DocEvent, senders upload to it) → AS2 (to a trading partner)](https://docevent.io/channel/sftp-server-to-as2/)
- [SFTP / FTPS Server (hosted by DocEvent, senders upload to it) → SharePoint (Microsoft 365 document library)](https://docevent.io/channel/sftp-server-to-sharepoint/)
- [SFTP / FTPS Server (hosted by DocEvent, senders upload to it) → Filerouter (on-premise folder)](https://docevent.io/channel/sftp-server-to-filerouter/)
- [SFTP / FTPS Server (hosted by DocEvent, senders upload to it) → DocEvent Agent (on-premise folder)](https://docevent.io/channel/sftp-server-to-agent/)
- [S3 Compatible pull (scheduled, from any S3-compatible bucket — R2, MinIO, B2, Wasabi) → Amazon S3 (or any S3-compatible bucket)](https://docevent.io/channel/s3-pull-to-s3/)
- [S3 Compatible pull (scheduled, from any S3-compatible bucket — R2, MinIO, B2, Wasabi) → Google Cloud Storage](https://docevent.io/channel/s3-pull-to-gcs/)
- [S3 Compatible pull (scheduled, from any S3-compatible bucket — R2, MinIO, B2, Wasabi) → Azure Blob Storage](https://docevent.io/channel/s3-pull-to-azure-blob/)
- [S3 Compatible pull (scheduled, from any S3-compatible bucket — R2, MinIO, B2, Wasabi) → FTP](https://docevent.io/channel/s3-pull-to-ftp/)
- [S3 Compatible pull (scheduled, from any S3-compatible bucket — R2, MinIO, B2, Wasabi) → SFTP](https://docevent.io/channel/s3-pull-to-sftp/)
- [S3 Compatible pull (scheduled, from any S3-compatible bucket — R2, MinIO, B2, Wasabi) → HTTP webhook](https://docevent.io/channel/s3-pull-to-http/)
- [S3 Compatible pull (scheduled, from any S3-compatible bucket — R2, MinIO, B2, Wasabi) → Email (SES)](https://docevent.io/channel/s3-pull-to-ses-email/)
- [S3 Compatible pull (scheduled, from any S3-compatible bucket — R2, MinIO, B2, Wasabi) → AS2 (to a trading partner)](https://docevent.io/channel/s3-pull-to-as2/)
- [S3 Compatible pull (scheduled, from any S3-compatible bucket — R2, MinIO, B2, Wasabi) → SharePoint (Microsoft 365 document library)](https://docevent.io/channel/s3-pull-to-sharepoint/)
- [S3 Compatible pull (scheduled, from any S3-compatible bucket — R2, MinIO, B2, Wasabi) → Filerouter (on-premise folder)](https://docevent.io/channel/s3-pull-to-filerouter/)
- [S3 Compatible pull (scheduled, from any S3-compatible bucket — R2, MinIO, B2, Wasabi) → DocEvent Agent (on-premise folder)](https://docevent.io/channel/s3-pull-to-agent/)
- [GCS Blob Pull (scheduled, from your Google Cloud Storage bucket) → Amazon S3 (or any S3-compatible bucket)](https://docevent.io/channel/gcs-pull-to-s3/)
- [GCS Blob Pull (scheduled, from your Google Cloud Storage bucket) → Google Cloud Storage](https://docevent.io/channel/gcs-pull-to-gcs/)
- [GCS Blob Pull (scheduled, from your Google Cloud Storage bucket) → Azure Blob Storage](https://docevent.io/channel/gcs-pull-to-azure-blob/)
- [GCS Blob Pull (scheduled, from your Google Cloud Storage bucket) → FTP](https://docevent.io/channel/gcs-pull-to-ftp/)
- [GCS Blob Pull (scheduled, from your Google Cloud Storage bucket) → SFTP](https://docevent.io/channel/gcs-pull-to-sftp/)
- [GCS Blob Pull (scheduled, from your Google Cloud Storage bucket) → HTTP webhook](https://docevent.io/channel/gcs-pull-to-http/)
- [GCS Blob Pull (scheduled, from your Google Cloud Storage bucket) → Email (SES)](https://docevent.io/channel/gcs-pull-to-ses-email/)
- [GCS Blob Pull (scheduled, from your Google Cloud Storage bucket) → AS2 (to a trading partner)](https://docevent.io/channel/gcs-pull-to-as2/)
- [GCS Blob Pull (scheduled, from your Google Cloud Storage bucket) → SharePoint (Microsoft 365 document library)](https://docevent.io/channel/gcs-pull-to-sharepoint/)
- [GCS Blob Pull (scheduled, from your Google Cloud Storage bucket) → Filerouter (on-premise folder)](https://docevent.io/channel/gcs-pull-to-filerouter/)
- [GCS Blob Pull (scheduled, from your Google Cloud Storage bucket) → DocEvent Agent (on-premise folder)](https://docevent.io/channel/gcs-pull-to-agent/)
- [Azure Blob Pull (scheduled, from your standard/flat Blob container) → Amazon S3 (or any S3-compatible bucket)](https://docevent.io/channel/azure-blob-pull-to-s3/)
- [Azure Blob Pull (scheduled, from your standard/flat Blob container) → Google Cloud Storage](https://docevent.io/channel/azure-blob-pull-to-gcs/)
- [Azure Blob Pull (scheduled, from your standard/flat Blob container) → Azure Blob Storage](https://docevent.io/channel/azure-blob-pull-to-azure-blob/)
- [Azure Blob Pull (scheduled, from your standard/flat Blob container) → FTP](https://docevent.io/channel/azure-blob-pull-to-ftp/)
- [Azure Blob Pull (scheduled, from your standard/flat Blob container) → SFTP](https://docevent.io/channel/azure-blob-pull-to-sftp/)
- [Azure Blob Pull (scheduled, from your standard/flat Blob container) → HTTP webhook](https://docevent.io/channel/azure-blob-pull-to-http/)
- [Azure Blob Pull (scheduled, from your standard/flat Blob container) → Email (SES)](https://docevent.io/channel/azure-blob-pull-to-ses-email/)
- [Azure Blob Pull (scheduled, from your standard/flat Blob container) → AS2 (to a trading partner)](https://docevent.io/channel/azure-blob-pull-to-as2/)
- [Azure Blob Pull (scheduled, from your standard/flat Blob container) → SharePoint (Microsoft 365 document library)](https://docevent.io/channel/azure-blob-pull-to-sharepoint/)
- [Azure Blob Pull (scheduled, from your standard/flat Blob container) → Filerouter (on-premise folder)](https://docevent.io/channel/azure-blob-pull-to-filerouter/)
- [Azure Blob Pull (scheduled, from your standard/flat Blob container) → DocEvent Agent (on-premise folder)](https://docevent.io/channel/azure-blob-pull-to-agent/)
- [Azure Files Pull (scheduled, from your Azure Files share) → Amazon S3 (or any S3-compatible bucket)](https://docevent.io/channel/azure-files-pull-to-s3/)
- [Azure Files Pull (scheduled, from your Azure Files share) → Google Cloud Storage](https://docevent.io/channel/azure-files-pull-to-gcs/)
- [Azure Files Pull (scheduled, from your Azure Files share) → Azure Blob Storage](https://docevent.io/channel/azure-files-pull-to-azure-blob/)
- [Azure Files Pull (scheduled, from your Azure Files share) → FTP](https://docevent.io/channel/azure-files-pull-to-ftp/)
- [Azure Files Pull (scheduled, from your Azure Files share) → SFTP](https://docevent.io/channel/azure-files-pull-to-sftp/)
- [Azure Files Pull (scheduled, from your Azure Files share) → HTTP webhook](https://docevent.io/channel/azure-files-pull-to-http/)
- [Azure Files Pull (scheduled, from your Azure Files share) → Email (SES)](https://docevent.io/channel/azure-files-pull-to-ses-email/)
- [Azure Files Pull (scheduled, from your Azure Files share) → AS2 (to a trading partner)](https://docevent.io/channel/azure-files-pull-to-as2/)
- [Azure Files Pull (scheduled, from your Azure Files share) → SharePoint (Microsoft 365 document library)](https://docevent.io/channel/azure-files-pull-to-sharepoint/)
- [Azure Files Pull (scheduled, from your Azure Files share) → Filerouter (on-premise folder)](https://docevent.io/channel/azure-files-pull-to-filerouter/)
- [Azure Files Pull (scheduled, from your Azure Files share) → DocEvent Agent (on-premise folder)](https://docevent.io/channel/azure-files-pull-to-agent/)
- [SharePoint (scheduled, from a Microsoft 365 document library) → Amazon S3 (or any S3-compatible bucket)](https://docevent.io/channel/sharepoint-to-s3/)
- [SharePoint (scheduled, from a Microsoft 365 document library) → Google Cloud Storage](https://docevent.io/channel/sharepoint-to-gcs/)
- [SharePoint (scheduled, from a Microsoft 365 document library) → Azure Blob Storage](https://docevent.io/channel/sharepoint-to-azure-blob/)
- [SharePoint (scheduled, from a Microsoft 365 document library) → FTP](https://docevent.io/channel/sharepoint-to-ftp/)
- [SharePoint (scheduled, from a Microsoft 365 document library) → SFTP](https://docevent.io/channel/sharepoint-to-sftp/)
- [SharePoint (scheduled, from a Microsoft 365 document library) → HTTP webhook](https://docevent.io/channel/sharepoint-to-http/)
- [SharePoint (scheduled, from a Microsoft 365 document library) → Email (SES)](https://docevent.io/channel/sharepoint-to-ses-email/)
- [SharePoint (scheduled, from a Microsoft 365 document library) → AS2 (to a trading partner)](https://docevent.io/channel/sharepoint-to-as2/)
- [SharePoint (scheduled, from a Microsoft 365 document library) → SharePoint (Microsoft 365 document library)](https://docevent.io/channel/sharepoint-to-sharepoint/)
- [SharePoint (scheduled, from a Microsoft 365 document library) → Filerouter (on-premise folder)](https://docevent.io/channel/sharepoint-to-filerouter/)
- [SharePoint (scheduled, from a Microsoft 365 document library) → DocEvent Agent (on-premise folder)](https://docevent.io/channel/sharepoint-to-agent/)
- [DocEvent Agent (on-premise folder) → Amazon S3 (or any S3-compatible bucket)](https://docevent.io/channel/agent-to-s3/)
- [DocEvent Agent (on-premise folder) → Google Cloud Storage](https://docevent.io/channel/agent-to-gcs/)
- [DocEvent Agent (on-premise folder) → Azure Blob Storage](https://docevent.io/channel/agent-to-azure-blob/)
- [DocEvent Agent (on-premise folder) → FTP](https://docevent.io/channel/agent-to-ftp/)
- [DocEvent Agent (on-premise folder) → SFTP](https://docevent.io/channel/agent-to-sftp/)
- [DocEvent Agent (on-premise folder) → HTTP webhook](https://docevent.io/channel/agent-to-http/)
- [DocEvent Agent (on-premise folder) → Email (SES)](https://docevent.io/channel/agent-to-ses-email/)
- [DocEvent Agent (on-premise folder) → AS2 (to a trading partner)](https://docevent.io/channel/agent-to-as2/)
- [DocEvent Agent (on-premise folder) → SharePoint (Microsoft 365 document library)](https://docevent.io/channel/agent-to-sharepoint/)
- [DocEvent Agent (on-premise folder) → Filerouter (on-premise folder)](https://docevent.io/channel/agent-to-filerouter/)
- [DocEvent Agent (on-premise folder) → DocEvent Agent (on-premise folder)](https://docevent.io/channel/agent-to-agent/)

## Legal

- [Terms of Service](https://docevent.io/terms-of-service/)
- [Privacy Policy (GDPR & CCPA)](https://docevent.io/privacy-policy/)
- [Data Processing Agreement (DPA)](https://docevent.io/data-processing-agreement/)
- [Support Policy](https://docevent.io/support-policy/)
- [Acceptable Use Policy](https://docevent.io/acceptable-use-policy/)
- [Service Level Agreement (SLA)](https://docevent.io/service-level-agreement/)
- [Security Information](https://docevent.io/security/)

## Get started

- [Sign up (free, no credit card)](https://console.docevent.io/login/new)
- [Log in](https://console.docevent.io/login)

## Regions

DocEvent runs in three regions: us-east-1 (US East), eu-west-1 (EU West), and
ap-southeast-2 (Asia Pacific, Sydney). Pick the region closest to your users at
sign-up.