# daptin/daptin

Daptin - Backend As A Service - GraphQL/JSON-API Headless CMS

Repository: https://github.com/daptin/daptin
Canonical: https://ross.abutalabs.com/products/daptin
Homepage: https://daptin.github.io/daptin/
Language: Go
License: LGPL-3.0
License Family: copyleft
Topics: content-management, headless-cms, static-site, graphql, graphql-server, graphql-api, json-api, crud-apis, cloud-storage
Last push: 2026-08-25T06:14:04+00:00

## Health v2 (maintenance only)
Score: 98/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 99, release rhythm 97, longevity 100
- inputs: {"age_days": 3382, "days_push": 8, "days_rel": 20, "gap_med": 2.0, "n_releases_24m": 19}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1891, forks 121 (observed 2026-08-28T04:05:49.611876+00:00)

## What it is
Daptin is a self-hosted Go application server that turns declarative schema definitions into permission-aware JSON:API and GraphQL CRUD backends. It bundles identity, row-level authorization, file storage, site hosting, mail, workflows, and integrations around a single data model.

## Use cases
- spin up a CRUD REST API from a schema file without writing backend code
- self-host a headless CMS with JSON:API or GraphQL endpoints
- add user signup, login, OAuth, and row-level permissions to an app backend
- host static sites and expose cloud storage like S3 or Google Drive over HTTP
- build workflow APIs that call third-party services from an OpenAPI spec
- run a self-hosted mail server with SMTP and IMAP accounts
- prototype a full backend with database, auth, and file uploads in minutes

## When to choose
- you need a complete backend (APIs, auth, storage, mail) without building one from scratch
- you want declarative, schema-driven CRUD APIs with fine-grained permissions
- you prefer a single self-hosted Go binary or Docker container
- you need to expose files, static sites, and integrations alongside your data APIs

## When to avoid
- you need a highly custom backend with bespoke business logic that declarative schemas cannot express
- you only need a lightweight API layer in front of an existing service
- your stack requires a managed BaaS with vendor support
- LGPL-3.0 licensing is incompatible with your project

## Facets
- artifact type: application
- maturity: active
- function: api-framework, http-server, graphql, auth, authorization, web-framework, file-upload, workflow-automation, email, self-hosted
- domain: web-development, backend, apis, cms, self-hosted, developer-tools
- platform: windows, self-hosted, go
- tags: headless-cms, backend-as-a-service, -api, baas, low-code-backend, oauth, letsencrypt, cloud-storage-sync, static-site-hosting, crud-apis, linux, macos, docker, web-server

## Member repositories
- daptin/daptin (main) score 98

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:05:49.611876+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T03:12:59.726703+00:00, confidence not recorded.
  - readme: https://github.com/daptin/daptin (fetched 2026-08-28T04:05:49.611876+00:00, sha 734e60fa647f)
  - homepage: https://daptin.github.io/daptin/ (fetched 2026-08-29T10:52:05.190592+00:00, sha f0377328de4c)
- Data as of 2026-08-30T08:39:29.467469+00:00.