Daptin Get started →

How Daptin works

From a table definition
to API requests.

Daptin loads table definitions and uses them to create routes, validate fields, check permissions, run actions, store files, and publish events.

Read the technical feature map →
SCHEMA LOADING

Daptin reads YAML
or JSON at startup.

For each table, it connects to the database, creates API routes, validates fields and relationships, checks permissions, lists the table for clients, and connects actions and record events.

SETTINGS STORED IN TABLES

Configure Daptin
through its API.

Daptin stores actions, scheduled tasks, file storage, integrations, LLM providers, usage plans, credentials, and mail servers in system tables. Administrators manage those rows through the API or dashboard.

world

Table and field definitions

action

Input fields and ordered action steps

task

Cron schedules for actions

site

Host names, paths, and site storage

cloud_store

Local and rclone file storage

integration

Imported external API calls

llm_provider

Model names, providers, and credentials

api_plan

Prices, rate limits, and quotas

credential

Encrypted OAuth and API credentials

mail_server

Mail domains and delivery settings

REQUEST FLOW

How Daptin handles
a resource request.

Daptin identifies the user, checks permissions, validates fields, reads or changes the record, records usage when enabled, and publishes successful changes.

  1. 01Authenticate

    Resolve the session, user, and groups.

  2. 02Authorize

    Check entity, object, relation, or action access.

  3. 03Validate

    Check field types, required values, validation rules, and input transformations.

  4. 04Execute

    Read or change records, calculate aggregates, or run action steps.

  5. 05Meter

    Enforce plan limits and record usage when configured.

  6. 06Publish

    Emit successful data changes to realtime consumers.

DEPLOYMENT

One process locally.
Multiple instances when needed.

LOCAL

One process

Run one binary with SQLite and local files for evaluation, prototyping, demos, or edge installations.

./daptin -port=6336
PRODUCTION

Production services

Use PostgreSQL or MySQL, persistent file storage, stable secrets, HTTPS, backups, monitoring, and only the protocols you need.

app + database + storage
SCALE

Multiple instances

Instances share the database and use Olric for cache entries, PubSub messages, usage counters, and rate limits.

instances + olric + database
IMPLEMENTATION DETAILS

How the server is built.

Standard databases

Use SQLite, MySQL, MariaDB, or PostgreSQL.

Shared permission checks

Records, relationships, actions, topics, and integrations use the same user and group permissions.

API descriptions

Table metadata and OpenAPI list the available tables, fields, routes, and actions.

Optional services

GraphQL, YJS, mail, FTP, and WebDAV-style routes start when enabled.

Server-side actions

Actions and schedules run in Daptin, where they can access stored credentials and metering records.

Ordered shutdown

Daptin stops accepting requests, waits for active work, then closes its services and database.

FEATURE REFERENCE

Browse the APIs,
services, and tools.

Browse all features →Production deployment guide ↗