Databases
Use SQLite for local development. Daptin documents MySQL and PostgreSQL for production deployments, with connection strings supplied through flags or environment variables.
Database setup →Current release · v0.12.36
Run Daptin as a native executable or container.
Start with one executable and SQLite. Use PostgreSQL or MySQL, persistent file storage, health checks, TLS, and backups when the application moves to production.
Choose a download →Published August 13, 2026
Download v0.12.36.
The matrix below reflects the published GitHub assets for v0.12.36. A macOS ARM64 release asset is absent. Checksums are also absent, so this page does not claim they are available.
| Operating system | Architecture | Status | Artifact |
|---|---|---|---|
| Windows | x86-64 | Published | daptin-windows-amd64.exe ↓ |
| Linux | x86-64 | Published | daptin-linux-amd64 ↓ |
| Linux / Raspberry Pi | ARM64 | Published | daptin-linux-arm64 ↓ |
| macOS | Intel x86-64 | Published | daptin-darwin-amd64 ↓ |
| macOS | Apple Silicon ARM64 | Not in v0.12.36 | No release asset |
Raspberry Pi: use a 64-bit Linux distribution on an ARM64-capable Pi, download the Linux ARM64 artifact, make it executable, and keep the database and file directory on persistent storage.
Docker
Docker image: daptin/daptin:v0.12.36
The current Docker Hub manifest for v0.12.36 reports Linux x86-64. Mount storage and choose an external database before using a container for persistent work.
docker run --rm \
-p 127.0.0.1:6336:8080 \
daptin/daptin:v0.12.36Docker Compose
Docker Compose with PostgreSQL.
The repository Compose file pins Daptin v0.12.36, waits for
PostgreSQL to become healthy, and stores database and file data in
named volumes. Its current /ready probe targets newer
source; the published v0.12.36 binary exposes /ping,
so do not copy that probe unchanged.
git clone https://github.com/daptin/daptin.git
cd daptin
cp .env.example .env
docker compose up -d
curl --fail http://127.0.0.1:6336/pingKubernetes status
Kubernetes manifests and current limitations.
The current repository contains a single-replica base, an evaluation PostgreSQL overlay, and an nginx ingress example for Kubernetes 1.25 or newer. The base expects an external PostgreSQL secret and persistent asset storage.
Do not add replicas to the default base. Multi-instance operation requires shared cloud or RWX asset storage, validated concurrent schema startup, exposed Olric ports, and configured seed discovery.
Read the manifest status and commands →Persistence and operations
Back up the database and the files together.
A Daptin backup is incomplete if it contains only SQL rows. Keep the database, local asset directory or cloud-store data, deployment configuration, and encryption material in the recovery plan. Restore the complete set in a separate environment before an upgrade.
File storage
Persist the local asset path or configure an rclone-backed store. The storage guide includes local files, MinIO, and AWS S3 examples.
Storage setup →Health checks
Release v0.12.36 exposes /ping for process
liveness. Use an external database-aware readiness check
before routing traffic. The /health path is the
admin application, not a probe.
TLS and logs
Configure certificates and HTTPS in Daptin or terminate TLS at a trusted proxy. Retain process logs and enable audit records for changes that require a history.
Production guide →Upgrades
Back up and restore-test the database and file store before changing the Daptin image or executable. Pin the target version, watch its health checks, and keep a tested rollback artifact.
Multiple instances
Share the database and assets, configure Olric discovery, and test startup and shutdown behavior before sending traffic to several instances.
Clustering →