Use case
Mobile backend
Auth, sync, and push notifications for native apps — without re-building what you already shipped.
Outcome
An open BaaS pattern that reuses your DeesseJS auth, contracts, and observability, even when the client is iOS or Android.
Stack
What shipping looks like
Native mobile apps don't need a new backend — they need the same backend, with a transport that fits their client. DeesseJS's API surface is the BaaS layer; the same auth, the same contracts, the same logs. The mobile client consumes what the web app consumes, with different shapes on the wire.
Get started
Pick a template that matches this use case and start: