Getting started

Run Daptin, then describe your application.

Use a release binary or container, open dashboard3, and create or import the schema that defines your product.

Run the first useful request

This path uses the published container and the default SQLite database. You need Docker and two free local paths: port 6336 and a named volume for persistent data. Keep the volume when you stop the container; deleting it deletes this evaluation instance.

1. Start Daptin

docker volume create daptin-quickstart-data
docker run --name daptin-quickstart --pull=always \
  -p 127.0.0.1:6336:8080 \
  -v daptin-quickstart-data:/var/lib/daptin \
  daptin/daptin:v0.12.36

Wait for the process to report that it is listening on port 6336. Leave this terminal open. If the port is already occupied, stop the conflicting service or map a different host port such as -p 127.0.0.1:7336:8080 and use that port below.

2. Test that the server is reachable

Open another terminal and request the liveness endpoint:

curl --fail http://localhost:6336/ping

A successful HTTP response proves that the process is accepting requests. It does not prove that your model, permissions, storage, or external services are configured correctly.

3. Open the dashboard and inspect the model

Open localhost:6336. Use the dashboard to inspect the generated tables and create an administrator account if the first-run flow asks for one. The dashboard is an inspection and administration surface; your product frontend can use the same generated APIs directly.

4. Add an application model

Continue with Define a data model to create a small record type, then use the API guide to create and read a record. That pair is the first complete Daptin loop: model, running API, stored record, and observable response.

Verify more than process startup

  • /ping responds on the address clients will use.
  • The dashboard loads without using a private container-only address.
  • A created record is still present after restarting the container.
  • An operation that should be denied is denied for a non-administrator user.
Do not use this evaluation command as a production plan. Before real traffic, choose a database, protect secrets and TLS, persist files, configure health checks, and rehearse backup and restore.

Stop, restart, or remove the evaluation

docker stop daptin-quickstart
docker start daptin-quickstart
# Remove the container only; the named volume remains:
docker rm -f daptin-quickstart
# Delete evaluation data only when you no longer need it:
docker volume rm daptin-quickstart-data

Continue to Server configuration before changing runtime settings, or to Production deployment when the application model is ready to operate.

The shortest useful path

Download the release for your platform, start the server, and open http://localhost:6336. Configure the first administrator when prompted. Define tables and relationships in dashboard3, or start Daptin with a YAML or JSON schema you can keep in version control.

1. Start the server

Use the native artifact for a direct local run or the published container for a container workflow.

2. Define the model

Add fields, validation, indexes, relationships, permissions, and asset columns.

3. Use the result

Open dashboard3 and the generated API, then inspect OpenAPI and metadata discovery routes.

4. Add product behavior

Configure actions, authentication, files, integrations, or live subscriptions as the product needs them.

Choose the deployment that fits your machine.