Daptin turns the things your application knows—customers, projects, content, orders—into one connected backend. Data, people, access, files, workflows, and integrations begin with the same shared context.
SQLite, MySQL, and PostgreSQL · LGPL-3.0
Most applications need the same foundations. The expensive part is not finding each piece—it is making identity, data, permissions, files, background work, and outside services behave like one product.
Each area has its own product story, concrete examples, connected capabilities, and honest boundaries. Explore without learning Daptin's internal vocabulary first.
Describe customers, projects, orders, content, or any other records your application needs. Relationships, APIs, administration, reports, history, and localization grow from that model.
Create complete account journeys, model teams and ownership, protect important accounts, connect outside identities, and carry access into records, files, and actions.
Turn approve, invite, publish, synchronize, or send into reusable backend actions. Run them from screens, schedules, or connected services without inventing several versions.
Attach files and images to real records, choose where bytes live, synchronize content, organize documents, and publish complete application surfaces at your own hostnames.
Let customers connect accounts, turn provider calls into product actions, receive and send mail, publish feeds, and meet established file and collection clients.
Deliver live record changes, collaborate in shared documents, run on supported databases, set traffic boundaries, coordinate nodes, and observe the paths customers depend on.
A single account and team relationship can shape the records a person sees, the files they download, the actions they run, and the live updates they receive.
The administration surface is not a concept mockup. It works with the resources and operations of the live Daptin backend.
Daptin fits small teams and product builders who want a broad, connected backend they can understand and operate without assembling every recurring foundation again.
Accounts, organizations, private records, documents, actions, and status updates.
Structured data, administration, approvals, schedules, reports, and integrations.
Models, files, collections, localization, sites, feeds, and collaboration.
Accounts, incoming messages, attachments, outbox work, retries, and familiar clients.
Run Daptin in infrastructure you choose. Use SQLite, MySQL, or PostgreSQL. Keep files locally or in compatible cloud storage. Export your schema and records. Inspect the LGPL-3.0 source.
What ownership meansYour team chooses and operates the database, storage, secrets, TLS, DNS, capacity, monitoring, backups, and upgrades. Daptin makes that boundary visible instead of hiding it behind a hosted control plane.
Plan a deployment you can own →Run the current release locally, create the first account, and explore the application foundation before committing to an architecture.
Daptin