-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathindex.html
More file actions
47 lines (37 loc) · 17.5 KB
/
Copy pathindex.html
File metadata and controls
47 lines (37 loc) · 17.5 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1">
<title>Daptin — Build the product, not its backend plumbing</title>
<meta name="description" content="Daptin turns your application model into a connected, self-hosted backend for data, people, permissions, files, workflows, integrations, realtime experiences, mail, and more.">
<link rel="canonical" href="https://daptin.github.io/">
<meta property="og:type" content="website"><meta property="og:title" content="Data, identity, permissions, files, jobs, integrations, and APIs—ready for your product."><meta property="og:description" content="One self-hosted backend where your product's data, people, access, files, workflows, and connected experiences already understand one another."><meta property="og:url" content="https://daptin.github.io/"><meta property="og:image" content="https://daptin.github.io/images/og-card-2026.png">
<meta name="twitter:card" content="summary_large_image"><meta name="twitter:title" content="Data, identity, permissions, files, jobs, integrations, and APIs—ready for your product."><meta name="twitter:description" content="One connected, self-hosted application backend."><meta name="twitter:image" content="https://daptin.github.io/images/og-card-2026.png">
<link rel="icon" href="/images/theme-favicon.png"><link rel="stylesheet" href="/styles.css"><script src="/site.js" defer></script>
</head>
<body>
<a class="skip-link" href="#main">Skip to content</a>
<header class="site-header"><div class="shell nav-wrap"><a class="brand" href="/"><img src="/images/theme-logo.png" alt="" width="35" height="35">Daptin</a><button class="nav-toggle" data-nav-toggle aria-expanded="false" aria-controls="site-nav">Menu</button><nav class="nav-links" id="site-nav" data-nav-links aria-label="Primary navigation"><div class="nav-primary"><a href="/product/">Why Daptin</a><details class="nav-menu"><summary>Product</summary><div class="mega-panel"><div class="mega-grid"><a class="mega-link" href="/product/features/data-modeling/"><strong>Shape your data</strong><span>Turn the things your product knows into a connected model.</span></a><a class="mega-link" href="/product/features/authentication/"><strong>Bring people in</strong><span>Accounts, sign-in, teams, and customer identity.</span></a><a class="mega-link" href="/product/features/permissions/"><strong>Decide who can do what</strong><span>Keep access attached to records, files, and actions.</span></a><a class="mega-link" href="/product/features/actions/"><strong>Automate the work</strong><span>Make repeatable product behavior part of the backend.</span></a><a class="mega-link" href="/product/features/files-images/"><strong>Store and publish content</strong><span>Files, images, cloud storage, and websites.</span></a><a class="mega-link" href="/product/features/integrations/"><strong>Connect outside services</strong><span>Bring provider operations into your product workflows.</span></a><a class="mega-link" href="/product/features/realtime-events/"><strong>Make experiences live</strong><span>Keep screens and collaborators current as data changes.</span></a><a class="mega-link" href="/product/features/mail/"><strong>Build around email</strong><span>Receive, store, read, and send mail as product data.</span></a><a class="mega-link" href="/operate/"><strong>Run it your way</strong><span>Choose infrastructure and keep operations visible.</span></a></div><a class="mega-all" href="/product/capabilities/"><strong>Explore every capability</strong><span>View the complete product map →</span></a></div></details><a href="/use-cases/">Solutions</a><a href="/developers/">Learn</a><a href="/operate/">Operate</a></div><div class="nav-actions"><a href="https://github.com/daptin/daptin">GitHub</a><a class="button small" href="/developers/#quickstart">Get Daptin</a></div></nav></div></header>
<main id="main">
<section class="home-hero"><div class="shell">
<div class="home-hero-copy"><div><span class="eyebrow">Open source · Self-hosted</span><h1>Data, identity, permissions, files, jobs, integrations, and APIs—ready for your product.</h1></div><div><p class="lede">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.</p><div class="hero-actions"><a class="button" href="/developers/#quickstart">Get Daptin</a><a class="button secondary" href="/product/capabilities/">Explore the product</a></div><p class="hero-note">SQLite, MySQL, and PostgreSQL · LGPL-3.0</p></div></div>
<div class="hero-product"><figure class="product-frame"><img src="/images/product/dashboard3-overview.jpg" alt="Daptin administration showing the resources of a running application" width="1230" height="768"><figcaption class="frame-caption">A live Daptin backend: the application model becomes a usable administration and product surface.</figcaption></figure><aside class="hero-side-note"><span>One model</span><strong>Every capability starts with the same understanding of your product.</strong><span>One owned runtime</span></aside></div>
</div></section>
<div class="signal-strip"><div class="shell signal-grid"><div class="signal"><strong>Model the product</strong><span>Records and relationships</span></div><div class="signal"><strong>Bring people in</strong><span>Accounts, teams, and ownership</span></div><div class="signal"><strong>Make work happen</strong><span>Actions, schedules, and providers</span></div><div class="signal"><strong>Keep control</strong><span>Your database and storage</span></div></div></div>
<section class="section"><div class="shell"><div class="section-head"><div><span class="eyebrow">Why Daptin</span><h2>Create a resource once; Daptin connects its accounts, permissions, files, workflows, and integrations.</h2></div><p class="lede">Most applications need the same foundations. A customer, their records, their files, and their permitted actions share one model from the start.</p></div><div class="comparison"><article class="comparison-card before"><span class="status">The usual pile</span><h3>Every new capability adds another seam.</h3><ul><li>Users live apart from the records they own.</li><li>Files need a second permission system.</li><li>Background jobs quietly gain different rules.</li><li>Provider tokens leak into client-specific code.</li><li>Mail, realtime, and sites become separate operating worlds.</li></ul></article><article class="comparison-card after"><span class="status">The Daptin approach</span><h3>Start from one product model and let capabilities share it.</h3><ul><li>People, teams, ownership, and records connect directly.</li><li>Files stay attached to the data that grants access.</li><li>Scheduled work reuses named product actions.</li><li>Outside services use protected backend connections.</li><li>Communication and live experiences build on the same application.</li></ul></article></div></div></section>
<section class="section"><div class="shell"><div class="section-head"><div><span class="eyebrow">The product</span><h2>Everything your backend needs—explained by what it lets you create.</h2></div><p class="lede">Each area has its own product story, concrete examples, connected capabilities, and honest boundaries. Start with a customer workflow and trace its records, people, files, actions, and integrations through Daptin.</p></div><div class="chapter-grid">
<article class="chapter-card"><span class="chapter-number">01 · Shape the product</span><h3>Turn your product's language into a working data foundation.</h3><p>Describe customers, projects, orders, content, or any other records your application needs. Relationships, APIs, administration, reports, history, and localization grow from that model.</p><div class="feature-links"><a href="/product/features/data-modeling/">Data models</a><a href="/product/features/resource-apis/">Resource APIs</a><a href="/product/features/graphql/">GraphQL</a><a href="/product/features/aggregations/">Reports</a><a href="/product/features/admin/">Administration</a><a href="/product/features/import-export/">Import & export</a></div></article>
<article class="chapter-card"><span class="chapter-number">02 · Bring people in</span><h3>Know who is here, where they belong, and what they can do.</h3><p>Create complete account journeys, model teams and ownership, protect important accounts, connect outside identities, and carry access into records, files, and actions.</p><div class="feature-links"><a href="/product/features/authentication/">Authentication</a><a href="/product/features/users-groups/">Users & groups</a><a href="/product/features/permissions/">Permissions</a><a href="/product/features/two-factor-auth/">Two-factor auth</a><a href="/product/features/oauth-connections/">OAuth connections</a><a href="/product/features/oauth-provider/">Identity provider</a></div></article>
<article class="chapter-card"><span class="chapter-number">03 · Make work happen</span><h3>Give every important operation one clear product meaning.</h3><p>Turn approve, invite, publish, synchronize, or send into reusable backend actions. Run them from screens, schedules, or connected services.</p><div class="feature-links"><a href="/product/features/actions/">Actions</a><a href="/product/features/transaction-control/">Transactions</a><a href="/product/features/scheduled-work/">Scheduled work</a><a href="/product/features/state-tracking/">State tracking</a><a href="/product/features/templates/">Templates</a><a href="/product/features/data-exchange/">Data exchange</a></div></article>
<article class="chapter-card"><span class="chapter-number">04 · Store and publish</span><h3>Keep content close to the customer and experience it serves.</h3><p>Attach files and images to real records, choose where bytes live, synchronize content, organize documents, and publish complete application surfaces at your own hostnames.</p><div class="feature-links"><a href="/product/features/files-images/">Files & images</a><a href="/product/features/large-files/">Large files</a><a href="/product/features/cloud-storage/">Cloud storage</a><a href="/product/features/storage-sync/">Storage sync</a><a href="/product/features/documents-collections/">Documents</a><a href="/product/features/sites/">Sites</a></div></article>
<article class="chapter-card"><span class="chapter-number">05 · Connect and communicate</span><h3>Bring outside services and familiar client tools into the product.</h3><p>Let customers connect accounts, turn provider calls into product actions, receive and send mail, publish feeds, and meet established file and collection clients.</p><div class="feature-links"><a href="/product/features/integrations/">Integrations</a><a href="/product/features/credentials/">Credentials</a><a href="/product/features/mail/">Mail server</a><a href="/product/features/outbound-mail/">Outbound mail</a><a href="/product/features/feeds/">Feeds</a><a href="/product/features/protocols/">Protocols</a></div></article>
<article class="chapter-card"><span class="chapter-number">06 · Keep it live and owned</span><h3>Show people the current product while your team keeps operational control.</h3><p>Deliver live record changes, collaborate in shared documents, run on supported databases, set traffic boundaries, coordinate nodes, and observe the paths customers depend on.</p><div class="feature-links"><a href="/product/features/realtime-events/">Realtime</a><a href="/product/features/collaboration/">Collaboration</a><a href="/product/features/databases/">Databases</a><a href="/product/features/traffic-controls/">Traffic controls</a><a href="/product/features/monitoring/">Monitoring</a><a href="/product/features/deployment/">Deployment</a></div></article>
</div><p style="margin-top:2rem"><a class="button secondary" href="/product/capabilities/">See all 44 capability journeys</a></p></div></section>
<section class="section"><div class="shell workflow-story"><span class="eyebrow">See the connection</span><h2>A customer joins. The whole backend already knows what that means.</h2><p class="lede">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.</p><div class="workflow-path"><div><small>01</small><strong>Create the customer account</strong></div><div><small>02</small><strong>Place them in a team</strong></div><div><small>03</small><strong>Share the right records and files</strong></div><div><small>04</small><strong>Let them run permitted actions</strong></div><div><small>05</small><strong>Keep their screen current</strong></div></div><div class="hero-actions"><a class="button" href="/use-cases/#multi-tenant">Explore the complete product story</a><a class="button secondary" style="color:white;border-color:white" href="/product/features/permissions/">See how access works</a></div></div></section>
<section class="section"><div class="shell"><div class="section-head"><div><span class="eyebrow">Real product proof</span><h2>See the model, access, and actions in the running product.</h2></div><p class="lede">Use the administration surface to inspect and update live application records. It works with the resources and operations of the live Daptin backend.</p></div><div class="proof-grid"><figure class="product-frame"><img src="/images/product/dashboard3-permissions.jpg" alt="Daptin administration showing access controls for a resource" width="1230" height="768" loading="lazy"><figcaption class="frame-caption">Access lives beside the resource it protects.</figcaption></figure><figure class="product-frame"><img src="/images/product/dashboard3-actions.jpg" alt="Daptin administration showing named actions available for a resource" width="1230" height="768" loading="lazy"><figcaption class="frame-caption">Product actions remain visible beside the data they work with.</figcaption></figure></div></div></section>
<section class="section"><div class="shell"><div class="section-head"><div><span class="eyebrow">Who it is for</span><h2>Use Daptin when the product needs more than a database and endpoints.</h2></div><p class="lede">Daptin fits small teams and product builders who want a broad, connected backend they can understand and operate.</p></div><div class="home-audience"><article><h3>Customer portals</h3><p>Accounts, organizations, private records, documents, actions, and status updates.</p></article><article><h3>Internal operations</h3><p>Structured data, administration, approvals, schedules, reports, and integrations.</p></article><article><h3>Content products</h3><p>Models, files, collections, localization, sites, feeds, and collaboration.</p></article><article><h3>Mail-enabled systems</h3><p>Accounts, incoming messages, attachments, outbox work, retries, and familiar clients.</p></article></div></div></section>
<section class="section"><div class="shell ownership"><div><span class="eyebrow">Open source · Self-hosted</span><h2>Keep the backend, the data, and the operating choices.</h2><p class="lede">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.</p><a class="button secondary" href="/open-source/">What ownership means</a></div><div><h3>Control includes responsibility.</h3><p>Your team chooses and operates the database, storage, secrets, TLS, DNS, capacity, monitoring, backups, and upgrades. Daptin exposes deployment, storage, limits, health, certificates, and recovery settings for your team to operate.</p><a class="card-link" href="/operate/">Plan a deployment you can own →</a></div></div></section>
<section class="feature-cta"><div class="shell"><span class="eyebrow">Start with the product you want</span><h2>Describe one model. Watch the backend come together around it.</h2><p class="lede">Run the current release locally, create the first account, and explore the application foundation before committing to an architecture.</p><div class="hero-actions" style="justify-content:center"><a class="button" href="/developers/#quickstart">Get Daptin</a><a class="button secondary" href="/product/capabilities/">Explore every capability</a></div></div></section>
</main>
<footer class="site-footer"><div class="shell"><div class="footer-grid"><div class="footer-brand"><a class="brand" href="/"><img src="/images/theme-logo.png" alt="" width="35" height="35">Daptin</a><p>Build and run a complete application backend around one connected model.</p><a class="button small" href="/developers/#quickstart">Get Daptin</a></div><div><h3>Product</h3><a href="/product/features/data-modeling/">Data models</a><a href="/product/features/permissions/">Permissions</a><a href="/product/features/actions/">Actions</a><a href="/product/features/files-images/">Files & images</a><a href="/product/features/integrations/">Integrations</a><a href="/product/capabilities/">All capabilities</a></div><div><h3>Build</h3><a href="/use-cases/#multi-tenant">Multi-tenant products</a><a href="/use-cases/#provider">Connected workflows</a><a href="/use-cases/#hosted">Sites & content</a><a href="/use-cases/#mail">Mail-enabled products</a><a href="/developers/">Learning center</a><a href="/product/architecture/">How it works</a></div><div><h3>Run & own</h3><a href="/operate/">Operations</a><a href="/operate/#security">Security model</a><a href="/open-source/">Open source</a><a href="https://github.com/daptin/daptin/releases">Releases ↗</a><a href="https://github.com/daptin/daptin/wiki">Technical reference ↗</a><a href="https://github.com/daptin/daptin/security">Report a vulnerability ↗</a></div></div><div class="footer-bottom"><span>© 2026 Daptin contributors · LGPL-3.0</span></div></div></footer>
</body></html>