File and feed protocols

Meet existing tools on familiar ground.

Expose managed content through protocols that file clients, feed readers, scripts, and publishing tools already understand.

  • FTP + FTPS
  • WebDAV-style
  • RSS + Atom + JSON

Beyond a custom API

Use the client that already fits the job.

Daptin can serve files over FTP and FTPS, provide core WebDAV-style file routes, and turn record collections into standard feeds. Each protocol stays connected to the storage and access model already configured in the server.

Move managed files with FTP

Connect compatible file-transfer clients to storage controlled by the application server.

Add transport protection with FTPS

Use TLS for compatible FTP clients where the deployment requires encrypted transport.

Work through WebDAV-style routes

Use basic file operations from tools that speak the WebDAV family of HTTP methods.

Publish records as feeds

Offer RSS, Atom, and JSON Feed for readers, syndication, and lightweight integrations.

Practical fits

Reuse the tools people already know.

Managed site uploads

Let an authorized operator publish or retrieve site files with an established FTP client.

Protected file transfer

Offer FTPS when legacy-compatible transfer is required but plaintext transport is not acceptable.

Subscriptions and syndication

Expose selected record collections to feed readers and downstream publishing tools without a custom client.

HTTP file tooling

Use the supported WebDAV-style operations for straightforward file access from compatible software.

Honest compatibility

Enable the protocol the workflow actually needs.

FTP access is tied to configured sites and application authorization. Prefer FTPS across untrusted networks, expose only the required services, and test client behavior against the latest release before production use.

Daptin implements core WebDAV-style file routes; it does not claim the full CalDAV or CardDAV standards. Feeds are read-oriented publication formats, not a replacement for the authenticated data API.

Use standard clients where they make sense.