DaptinInspect the runtime
Read the request gates, data paths, action outcomes, protocol servers, and dependencies. Inspect request gates, data paths, action outcomes, protocol servers, and runtime dependencies in the source.
Browse the source ↗Home / Open source
Keep your choices openRun Daptin on infrastructure you control, inspect its source, and export your application data.
Daptin is LGPL-3.0 software that runs on infrastructure you choose. Keep control of the runtime, records, files, and release you depend on—and keep a path to inspect, change, export, or move them.
Practical ownership
Control is a set of concrete options.
Inspect Daptin’s architecture, deployment path, and portability while your team operates the production instance.
Choose the state systems
Use SQLite, MySQL, or PostgreSQL for relational state. Keep assets locally or connect rclone-compatible storage where the provider and workload fit.
Choose a database path →Keep movement paths
Export schema and data, use stable reference IDs, access resources over JSON:API or GraphQL, and connect familiar protocol clients where supported.
See how data can move →Responsibility
Self-hosting moves authority to your team.
That authority includes deciding how the system is secured, observed, recovered, and changed.
| Daptin provides | You provide |
|---|---|
| Application model, generated resources, identity and permission mechanisms | Correct schemas and policies, administrator hygiene, account lifecycle, and access review |
| Database adapters, asset abstractions, caches, queues, and service processes | Capacity, durability, backups, network policy, provider accounts, DNS, and recovery tests |
| Credential records, certificate workflows, OAuth roles, rate and request controls | Secret key material, certificate/DNS reachability, least privilege, safe limits, and rotation |
| Source, release artifacts, issue history, tests, and documented interfaces | Version selection, dependency assessment, rollout, monitoring, rollback, and local patches |
Project ecosystem
Use adjacent projects for a specific job.
The ecosystem is most useful when each project has a clear role in the application lifecycle.
Operate from a terminal
The Daptin command-line client supports scripted and terminal-oriented interaction with a running server.
Explore daptin-client ↗Generate application shapes
Schema and example projects offer starting points for common models. Treat them as editable inputs and review permissions before use.
Explore schemas ↗Build administration surfaces
Dadadash demonstrates an administration-oriented client around Daptin resources and APIs.
Explore Dadadash ↗Participate
Leave useful evidence.
Start with the project record
Search existing issues and discussions, include the exact release, database, operating context, reproduction steps, expected behavior, and relevant sanitized logs.
Keep changes reviewable
Explain the user-visible problem, preserve compatibility where possible, add focused evidence for behavior, and update documentation when a contract changes.
Report vulnerabilities privately
Report vulnerability details privately through GitHub’s security reporting channel. Use the repository security reporting path so maintainers can coordinate assessment and disclosure.