Home / Product / TLS certificates

Protect public services

Give your sites and communication services a trusted front door.

Manage certificate records inside the same runtime as the hostnames and services that use them, so encrypted connections are part of the deployment plan.

See what it changes Technical guide ↗

TLS certificates in a product

Name the public serviceA website, mail endpoint, or file service

Provide trusted TLS materialUse ACME or an operator-managed certificate

Serve the right hostnameThe listener selects the matching certificate

TLS material connects to the service it protects

01Encrypt public connectionsPresent certificate-backed TLS where the configured service supports it.

02Manage several hostnamesAssociate certificate records with the sites and listeners that need them.

03Keep certificate work visibleGenerate, inspect, download, and replace material through explicit actions.

Why it matters

A certificate is valuable only when the right service presents it at the right time.

A hosted site, mail endpoint, or secure file service needs more than a certificate file on disk. The deployment must connect hostnames, certificate material, listeners, renewal, and failure handling.

Daptin represents certificates as managed records and can generate self-signed material or complete an ACME HTTP challenge. Applicable HTTPS, site, mail, and file-service paths can draw on the configured certificate manager.

That brings TLS into the same operating picture as the services it protects, instead of leaving it as an invisible manual step on one server.

Connect trust to the hostname

Make the relationship between a public service and its certificate explicit.

Support different deployment paths

Use operator-provided, ACME-issued, or self-signed material where appropriate.

Inspect and replace deliberately

Keep certificate and public-key operations visible to authorized administrators.

How it fits

Part of one connected backend.

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

Step 1Request

Create or provide certificate material for a hostname.

Step 2Store

Keep the certificate as a managed protected record.

Step 3Match

Associate it with the site or protocol service.

Step 4Serve

Present the material when the compatible listener accepts a connection.

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.

Customer-facing site

Serve a Daptin-hosted frontend over HTTPS.

Private mail service

Protect compatible SMTP and IMAP connections with configured TLS.

Managed content endpoint

Add secure transfer to a hosted file surface.

Connected by design

Build the next part without starting over.

These capabilities share the same application context, so each one makes tls certificates more useful.

Know the boundary

What Daptin leaves in your hands.

Certificate generation is not automatic lifecycle management. You still own DNS, public reachability, trust-chain choice, secure private keys, renewal timing, monitoring, and safe replacement before expiry.

Understand the operating responsibility →

Build from one foundation

Make tls certificates 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