Home / Product / FTP and FTPS

Meet existing file tools

Let established file clients manage published content without escaping its site boundary.

Expose permitted site roots through FTP or encrypted FTPS, so existing publishing and transfer tools can work with Daptin-hosted content.

See what it changes Technical guide ↗

FTP and FTPS in a product

A client connectsUse an existing FTP-capable tool

Enter an allowed site rootSee only the content that connection may reach

Manage published filesUpload, rename, move, or remove within scope

Familiar tools meet a bounded content root

01Reuse existing workflowsConnect tools people already use for file transfer and publishing.

02Keep content scoped to a siteReject path escape and cross-site movement.

03Add transport encryptionUse FTPS with the configured certificate material.

Why it matters

A familiar protocol can be the shortest path from an existing workflow to a new backend.

A content team, build system, or legacy publishing process may already deliver files through FTP. Replacing every tool can make adoption harder than the product problem itself.

Daptin can expose configured site roots over FTP and FTPS. The file client works with a familiar directory view while the backend guards the permitted site boundary and rejects path escape or cross-site rename.

Because the root belongs to a Daptin site, updates remain connected to the hosted content surface, storage, and certificate plan.

Keep useful tools working

Allow compatible FTP clients to participate in the publishing workflow.

Protect the site boundary

Constrain paths and operations to the site the connection may manage.

Use the same content foundation

Let transferred files appear in the storage and site paths already serving the product.

How it fits

Part of one connected backend.

FTP and FTPS does more when it can reuse the records, people, access rules, and workflows already in your application.

Step 1Configure

Choose the site and storage root the service will expose.

Step 2Authenticate

Establish the permitted connection.

Step 3Transfer

Use familiar directory and file operations within the root.

Step 4Publish

Serve the updated content through the associated site.

What it enables

Use it in products people recognize.

Start from the experience you want to create; the backend capability supports the work behind it.

Legacy publishing

Keep an existing content-delivery process while modernizing the backend.

Build artifact upload

Move a generated static site into its serving root.

Managed client access

Give an approved operator a bounded file-management surface.

Connected by design

Build the next part without starting over.

These capabilities share the same application context, so each one makes ftp and ftps more useful.

Know the boundary

What Daptin leaves in your hands.

FTP sends credentials and content without transport protection unless FTPS is correctly configured. Restrict network exposure, use least privilege, monitor operations, protect certificate keys, and test the exact client behavior.

Understand the operating responsibility →

Build from one foundation

Make ftp and ftps part of the product—not another disconnected service.

Run Daptin locally, explore the live administration surface, and follow one complete application path.

Get Daptin Explore all capabilities