Home / Product / FTP and FTPS

Meet existing file tools

Let established FTP or FTPS clients manage published content inside an enforced site root.

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 siteConfine every FTP operation to its configured site root and permitted path.

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. Give file clients a familiar directory view while Daptin enforces site-root paths and same-site rename rules.

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

Map each file session to one site boundary and enforce path and rename rules there.

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.

Configure FTPS with valid certificates and protected credentials for encrypted file transfers. 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

Expose a site root to FTP or FTPS clients while Daptin confines every path to that site.

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

Get Daptin Explore all capabilities