Daptin

Home / Learn

Start with the product

Turn one product idea into a working backend.

Begin with the people, information, and outcome your product needs. Daptin can connect the accounts, access, files, actions, outside services, and live updates around that idea—without making you understand every mechanism first.

Choose what you want to build Run Daptin locally
Choose a starting point

What should someone be able to do?

Each path explains the customer benefit, shows the connected backend pieces, and points to exact reference material only when you need it.

A customer joins

Create accounts, teams, and private workspaces.

Give every person a clear identity, place them in the right group, and make their access follow the records and files they own.

Sign-in Teams Access
Work moves forward

Turn a repeatable decision into a product action.

Let someone approve, invite, publish, submit, or synchronize through one named operation your product can reuse.

Actions Progress Schedules
Content belongs somewhere

Keep documents and images attached to the work.

Store customer files with their records, choose local or cloud storage, transform images, and publish selected content as a site.

Files & images Cloud storage Sites
Another service helps

Let customers connect the tools they already use.

Ask for approval, remember the right account, and bring useful provider operations into a familiar product workflow.

Customer connections Integrations Credentials
Everyone stays current

Make changes appear while people work.

Update live screens, notify connected systems, or let several people collaborate without inventing a separate identity model.

Live updates Events Collaboration
Email is part of the product

Receive and send messages around customer records.

Build an inbox, route incoming mail, send product messages, and keep communication connected to the same application data.

Inbound mail Outbound mail Templates
One concrete example

A client portal can grow without becoming six unrelated backends.

The same shared model can carry a customer from invitation to completed work.

01 Invite the customer
02 Place them in an account
03 Show only their records
04 Collect files and approval
05 Send updates and stay live

That journey combines accounts, groups, permissions, records, files, actions, templates, mail, and realtime updates. Because they share customer and ownership context, the team spends less time translating the same rule between services.

See the full portal story
How Daptin grows with the idea

Add capability around a shared foundation.

You do not need to design every surface on day one. Start from the product vocabulary, then add the next useful customer experience.

01 · Describe Name the real things.

Customers, projects, bookings, articles, invoices, or any other records and relationships the product understands.

02 · Protect Attach people and access.

Decide who owns, sees, changes, or performs work on each kind of information.

03 · Behave Add meaningful actions.

Turn the product's verbs into reusable operations, schedules, templates, and integrations.

04 · Deliver Choose how people interact.

Use APIs, the admin surface, live updates, mail, sites, feeds, or established protocols as needed.

Ready to try it?

Run the current release locally.

This starts Daptin v0.12.36 with persistent local data and makes its administration surface available on port 6336.

Docker

docker volume create daptin-data
docker run --name daptin \
  -p 6336:6336 \
  -v daptin-data:/opt/daptin \
  daptin/daptin:v0.12.36

What happens next

Open http://localhost:6336. A new instance guides you through establishing its first administrator. Keep that setup private until you have reviewed access, storage, secrets, TLS, and recovery.

Release files and notes ↗

Taking it beyond a local trial? Use the plain-language production path before exposing it to customers.
When you need exact details

Move from product story to technical contract.

The feature pages explain value and fit. The project reference provides version-specific fields, routes, configuration, and examples.

Understand the whole system

See how the shared model connects people, records, permissions, behavior, delivery surfaces, and operator-owned infrastructure.

How Daptin works →

Look up a contract

Use the maintained wiki when you need an endpoint, schema field, configuration key, default, or code-level example.

Browse the technical reference ↗