Daptin
Get started →
Use cases
Use Daptin as the server for a new application. It can also run beside an existing application as a data API, file server, integration gateway, OAuth provider, metering service, or realtime service.
Follow the product catalog walkthrough →Use groups for accounts or teams. Ownership, relationships, and row permissions restrict each account’s records. Plans and quotas can limit API or LLM usage.
Define the tables and use the generated APIs and dashboard to manage records. Add imports, exports, actions, relationships, and access rules as needed.
Assign plans, set rate and quota limits, record each API call, and run an action after metering to debit credits or update billing records.
Publish create, update, and delete events to subscribed clients. Daptin can also publish feeds and enable YJS on selected document columns.
Attach files to content records, store them locally or in a configured cloud store, render Go templates, publish feeds, and serve sites by host name or path.
Import operations from OpenAPI, store OAuth or encrypted credentials, and call those operations through Daptin. Its /v1 routes can stream model responses and record token usage.
Run Daptin as a file service, admin data API, integration gateway, OAuth provider, metering service, mail server, feed server, or realtime channel.
These repositories cover schemas, LLM routing, metering, integration credentials, OAuth provider flows, and a larger application.
Browse all clients and examples →