Daptin Get started →

LGPL-3.0 application server

Run Daptin
on your infrastructure.

Inspect the source, download a release, and run it on a server that can reach your database and file storage. Application tables are defined in YAML or JSON.

Explore the repository ↗Download a release
01

Choose the database

Daptin stores records in SQLite, MySQL, MariaDB, or PostgreSQL. Files can stay on local storage or use a configured rclone provider.

02

Choose how to run it

Download the binary, build it from source, use the Docker image, or schedule the container on your infrastructure. Optional protocols start only when enabled.

03

Use documented HTTP APIs

Define the schema in YAML or JSON. Clients can use JSON:API, GraphQL, OpenAPI, WebSockets, OAuth/OIDC, and OpenAI-compatible routes.

LOCAL INSTALLATION

Run the current release locally.

$ docker run --rm -p 127.0.0.1:6336:8080 daptin/daptin:v0.12.36

Open localhost:6336 and create the first administrator. This command stores records and files inside the temporary container; use persistent storage and an external database for production.

Installation options →
OPERATING RESPONSIBILITY

Your team operates production.

Daptin supplies the application server and health endpoints. Your deployment still needs backups, TLS, monitoring, capacity planning, upgrades, and incident response.

Included in Daptin

  • APIs, users, permissions, files, actions, events, and integrations
  • SQLite, MySQL, MariaDB, and PostgreSQL support
  • Public source code and release history
  • YAML and JSON schema files
  • GraphQL, mail, FTP, and other optional services that can be disabled
  • Health, statistics, audit, cache, TLS, and graceful shutdown controls

What production still requires

  • Database backups and tested restores
  • Stable JWT and encryption secrets
  • HTTPS, DNS, and certificate operations
  • Durable storage and capacity planning
  • Monitoring, alerting, and log retention
  • Upgrade, security, and incident processes
DEPLOYMENT OPTIONS

Local, production,
and multiple instances.

  1. STEP 1

    Local

    One binary, SQLite, and local file storage on a developer machine.

  2. STEP 2

    Production

    PostgreSQL or MySQL, persistent file storage, HTTPS, backups, and monitoring.

  3. STEP 3

    Multiple instances

    Shared database and Olric-backed cache, PubSub, counters, and rate limits.

CLIENTS AND EXAMPLES

Code, clients, schemas,
and demos.

The Daptin organization contains the server, CLI, JavaScript and Go clients, schema samples, and runnable examples.

Core serverGo application server →Daptin CLIManage tables, records, and actions →JavaScript clientBrowser and Node client →Go clientTyped Go client →Schema samplesStarter YAML and JSON files →All repositoriesTools, demos, apps, and packages →
LICENSE

LGPL-3.0

Daptin is distributed under the GNU Lesser General Public License v3. Review the license text for the terms that apply to your distribution and modifications.

Read the license ↗
LATEST RELEASE

Download and run
the current version.

Get the latest release →Read the production guide ↗