Datab does not yet ship official client SDKs. Partner workloads interact with the Datab Node through plain HTTP + JSON against the endpoints documented in API Docs.

What we plan to publish

• Java / Kotlin — for partner workloads packaged as snap parts or container images on the same node.
• Dart / Flutter — extracted from datab_mobile and datab-os-mobile's service layer.
• TypeScript — for partner-app web frontends that need to reach the backend from the LAN.

What we will NOT ship

• An SDK that bypasses the Atlas identity gate.
• An SDK that bundles credentials. Auth is always per-deployment.
• An SDK that calls Orula or Gu without honoring the approval-queue contract.

Until the SDKs publish, the HTTP+JSON surface is the contract. Treat the URL paths and response shapes as the public API.